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
- Tweets277
- Following16
- Followers533
- Likes401
Pinned Tweet
"We don't want each other checking each other's payments"
@aescobar0g from @rhea_finance on why they moved most of their treasury activity to a confidential treasury, payroll included.
Onchain payroll means every colleague can see what everyone earns. Most teams have absorbed that rather than fixed it, which is no longer the case for teams using Trezu.
~$160M in team treasuries on Trezu.
We’re just getting started 🚀
AI agents have already made 138M crypto payments. Sooner or later your team gives one access to the treasury.
The real question: can it move money without asking?
Don’t hand an agent a private key. Give it a seat in your multisig:
→ It can propose payments
→ It can’t approve them
→ Every transfer still needs your team’s signatures
An agent with a key is a hot wallet with opinions.
An agent with a role is a junior teammate.
Building with agents? DM us and we’ll show you how to set up an agent-safe treasury on Trezu.
Five hardware wallets can still hide a single point of failure.
Ledger’s account of the recent hardware-implant attack describes genuine devices being modified after they left its control to capture recovery phrases during setup.
For a company treasury, that raises four practical questions:
• Where did each signing device come from, and who handled its setup?
• Were signer keys generated independently, with recovery material stored separately?
• Do different people actually review and approve payments?
• Who can add signers or lower the approval threshold?
That last question deserves more attention.
A 3-of-5 payment policy can be undermined by a single account with permission to rewrite it.
Trezu lets teams separate payment approvals from governance, with configurable thresholds for each. Teams can require multiple approvals both to move funds and to change who controls them.
Those rules work alongside trusted device sourcing, independent keys and careful transaction review.
The goal is to limit what one compromised device, account or person can authorize.
A verified human can still paste the wrong address.
This is why the second signer actually has to read the transaction.
Are hardware wallets cooked?
Trezu co-founder and CTO @Freol is live on Crypto Quorum, discussing hardware wallets and their future.
Tune in and join the conversation.
Are hardware wallets done for after a series of hacks and exploits? Or will they have a second wind?
Join us for the next episode of the Crypto Quorum, co-hosted by @zano_project and @RUNEBondApp and sponsored by @EdgeWallet, live Thursday at 5pm UTC!
xitter.cf/i/spaces/1rGmqpaWZENGy
How to set up your team’s crypto treasury for $0.
Multisig wallets are safer than most hardware wallets.
→ Prepare your signers
Use independent wallets, separate seeds and offline backups. Share public account IDs only.
→ Create your treasury
Go to Trezu, add your team and choose public or confidential. Confidential keeps balances and payment details private; members and votes remain public.
→ Assign roles
Requestor proposes payments. Finance approves them. Governance manages members and rules.
→ Set both thresholds
Example: 2-of-3 for Finance and 2-of-3 for Governance. Protect governance wallets with hardware devices.
→ Test first
Make a small deposit and test payment. Check the recipient, asset, network and amount before approving.
→ Know the costs
$0 treasury creation. We cover gas for the first 1,000 actions/month, then standard network fees apply. Swap fee: 0.70%.
We never hold your private keys. Your team stays in control.
Bookmark this before your next payroll.
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!
us watching a founder keep the entire team’s treasury on a single Ledger instead of setting up a multisig
A good reminder for anyone managing a treasury: a single key should never be a single point of failure.
Keys get compromised, devices get tampered with, seeds get phished, people make mistakes. With multisig, one compromised key can't move funds on its own. You just rotate that signer out and keep going.
Secure setup + multisig = a treasury that survives a bad day.
Ledger is investigating reports of loss of funds from users in South East Asia who purchased products from a reseller named CryptoBillis. As a precaution, and pending the results of our investigation, we have asked CryptoBilis to pause all sales and shipments of Ledger devices. We recommend Ledger users who purchased from this reseller in the last 90 days to not initiate set up if you have not done so yet. If you have set up your Ledger device, consider moving assets to a new Ledger signer (with new seed). We will continue to inform customers of updates as the investigation progresses.
Reach out to Ledger customer support through official channels with any questions: support.ledger.com/
“Night and day.”
That’s how @rhymetaylor from @dragonisnear described voting with Trezu.
Glad to support a DAO that takes its members’ experience and treasury security seriously.
Founders: could you go offline for two days at a conference without your company's finance ops stopping?
If your phone keeps buzzing with payments, approvals and invoices, here's how to let your team handle them safely:
Before
One account on Ethereum
One account on Arbitrum or Base
One account on Solana
One hardware wallet for BTC
One accountant to account for transactions
Multiple actions for bridging and swapping
After
One account on Trezu
Payroll at most crypto teams:
> 40 addresses copy pasted into a spreadsheet
> Funds on 6 chains, tracked by one person's memory
> Chasing 3 signers across 3 time zones for one payment
Here's the same thing on Trezu:
🧵
Security is a spectrum. We are here for the heavy lifting.
When it comes to crypto, don't lock yourself on using one solution to fit all.
It is a spectrum. For simple cases, go with Passkey on near(dot)com, for more complex - go with Passkey and 2 out of 3 approvals on Trezu, and for the most secure treasury - go with Trezu with 3 out of 5 approvals with Ledgers (even if you are just 2 people, you sill can have multiple wallets)
The cat is out of the bag, fair enough.
But can we talk about the elephant in the room now?
Massive spike in sign ups for @near_ai cloud as people realize they need to encrypt their prompts.
Keeping your AI private is as critical for businesses as having op sec. Cat is out of the bag and everyone needs to position accordingly.
Confidential treasuries in Trezu, built on @NEARProtocol, keep amounts, recipients and balances private.
@rhea_finance already moved most of their treasury activity there, payroll included.
Hear more from @aescobar0g, Head of Operations at Rhea: xitter.cf/TrezuApp/status/210063…
"We don't want each other checking each other's payments"
@aescobar0g from @rhea_finance on why they moved most of their treasury activity to a confidential treasury, payroll included.
Onchain payroll means every colleague can see what everyone earns. Most teams have absorbed that rather than fixed it, which is no longer the case for teams using Trezu.
Most teams now hold assets on more than one chain, and every chain comes with its own wallet, its own set of signers and its own way of approving a payment.
Add a separate tool for payroll and another for swaps, and the treasury ends up spread across several apps, with no one on the team able to see it all at once.
Trezu works a bit differently. You get one account and one dashboard, and from there you can send, receive, swap, and bridge across 35+ chains, with every outgoing move going through the layers of approval your team sets up.
