All your team's crypto in one place. · 150+ tokens on 35+ chains · Confidential payroll and transfers · Batch payments and swaps · Start free, gas on us 👇

Joined January 2026
Trezu | Multisig treasury for Web3 teams retweeted
So happy to see @meta_pool getting the NEAR Connector! Now DAOs can stake their $NEAR through @TrezuApp and receive $stNEAR in return. Their stake keeps earning rewards while $stNEAR remains liquid: usable across the ecosystem and swappable back to $NEAR at any time!
3
3
1
14
657
Trezu | Multisig treasury for Web3 teams retweeted
We gave ChatGPT, Claude, Gemini and Grok one public treasury address. No context. Same 90-day window. The results were wildly different ↓
1
3
2
17
1,319
Trezu | Multisig treasury for Web3 teams retweeted
Public or confidential?
2
1
15
635
Trezu | Multisig treasury for Web3 teams retweeted
You’re more vulnerable than ever. Recent incidents involving Coldcard, Trezor, SafePal, and even exchanges showed 4 very different ways things can go wrong. > Keys can be compromised > Personal data can leak > Withdrawals can be frozen > Your treasury can expose you At this rate, making it to 2027 with your funds, access, and privacy intact feels like an achievement. That’s uncomfortable enough when it’s your own money. It gets more serious when you’re managing more than your own 0.3 BTC. Hardware alone won’t save you from all of this. Neither will leaving funds on an exchange. And putting your entire financial operation onchain for everyone to see creates a different kind of risk. The more capital you manage, the more "security" has to actually cover: > Control > Access > Privacy Most solutions solve one. Trezu is built for all three.
1
2
2
13
1,045
Trezu | Multisig treasury for Web3 teams retweeted
Self-custody comes in many forms
Dear community, While your SafePal wallet, seed phrase, and private keys are secure; we identified a flaw in the order-tracking plug-in that led to unauthorized access to information of a subset of customers. The issue has been fixed with additional security measures introduced. The incident impacts approximately 39,798 customers who placed orders between March 2, 2025 and April 11, 2026. Exposed information includes name, email address, shipping address, phone number, and purchase details. All affected customers have been notified individually by email. We have also published this webpage safepal.com/scam-protection for customers to verify if they are affected using order ID number and shipping country. For a complete disclosure of the incident and the actions we’ve taken, along with FAQs and guidance, please refer to our blog: safepal.com/blog/security-up… This incident did not involve your seed phrase, private keys, wallet password, or other wallet credentials, bank account information, payment card numbers, or government-issued identification numbers. Never share your seed phrase, private key, or password with anyone, and stay vigilant against phishing or impersonation attempts. We are extremely sorry to the community and those who are affected. Updates will be posted on our blog as we continue to work through things.
2
1
12
755
Trezu | Multisig treasury for Web3 teams retweeted
Your company’s bank statement probably isn’t public. > Why is your treasury? Payroll, counterparties, balances, and spending patterns don’t need to become public intelligence. Stay onchain. Keep the business private.
4
5
3
24
2,266
Trezu | Multisig treasury for Web3 teams retweeted
Your treasury address is free competitive intelligence for anyone who wants it. Today’s Trezor leak through a shipping provider is a reminder that your core security can work exactly as intended while sensitive data around it still gets exposed. The same applies to an onchain treasury. Your keys can be secure. Your multisig can work perfectly. Your funds can remain fully self-custodial. And your financial activity can still be public. Give someone enough transaction history and over time they can figure out: > how much runway you have left > whether your team is growing or shrinking > which counterparties you keep paying > when spending suddenly starts slowing down Nobody needs to hack your company. A competitor only needs your treasury address. We already know what CT does with a single public metric. A revenue chart drops, and within hours people are ranking winners, losers, growth, and decline. That’s one number. Your treasury address can expose months of financial signals. For a blockchain, public financial metrics are part of the market. For a company, publishing its financial operations is a choice and usually a bad one. That choice used to have an excuse -- keeping a self-custodial onchain treasury private was hard. The excuse no longer holds. Today you can manage assets onchain, keep full self-custody, use multisig, and make bulk payments without turning your financial operations into a public data feed for competitors. This is exactly what Confidential Treasuries in Trezu make possible. Want to see what a private workflow looks like? Book a 15-minute demo: trezu.org/book
2
1
16
1,487
Trezu | Multisig treasury for Web3 teams retweeted
More than $50M is managed through Trezu. Trezu cannot move a dollar of it. But keeping control of the funds is only the starting point. Here is how a company can run payroll without giving up that control or publishing every salary onchain 🧵
2
2
3
12
1,229
Trezu | Multisig treasury for Web3 teams retweeted
Quantum-resistant multisig is not a new type of multisig. The approval rules stay exactly the same. What changes is the cryptography each signer uses to prove that an approval is theirs. NEAR’s latest mainnet upgrade made this possible for Trezu. Here is how it works 🧵
MAINNET UPGRADE Quantum-safe signing is now live on NEAR mainnet. This makes NEAR one of the first blockchains with a NIST-approved post-quantum signature scheme in production. The upgrade also launches dynamic resharding, so NEAR Protocol can scale itself automatically 🧵
2
8
2
45
11,975
Trezu | Multisig treasury for Web3 teams retweeted
Running payroll? Paying invoices? Receiving payments? Historically doing this on-chain meant all the key company information was visible to everyone in the world. With @TrezuApp using confidential intents you can now keep this information private as it's suppose to be.
Running payroll on a public multisig means every salary is public. Every vendor payment. Every trade size. Not every team signed up for that level of transparency. Trezu lets you choose. Public treasury for open governance. Confidential treasury for everything else.
13
35
2
236
22,280
Trezu | Multisig treasury for Web3 teams retweeted
Are you still using multisig and telling everyone how much your business spends/receives? Time to go confidential with Trezu across 35+ chains - a multi chain confidential multisig.
I want to quote the legend here: "This is my last public swap." @AlexAuroraDev, but this time it is "this is our last public swap" since Trezu brought confidential to the teams and businesses Kudos to @near_intents and @NEARProtocol teams for the great permissionless tech that is really a pleasure to build on!
6
11
3
167
11,458
Trezu | Multisig treasury for Web3 teams retweeted
#TrezuLeaks Trezu CLI was just dropped. Let your AI agents unleash the power of confidential multichain multisig!
1
4
2
20
1,188
Trezu | Multisig treasury for Web3 teams retweeted
Building a Decentralized Future for NEAR Partners, Teams, and Communities 🧱 The Meteor team has supported @TrezuApp to build a meta-transaction relayer, ensuring the smoothest UX for Trezu users. Trezu is now live and accessible directly via the Meteor App explore page! Manage team payments, bounties, and multi-sig approvals on the go. High-level security, mobile-first.
12
8
65
8,116