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
- Followers532
- Likes401
Attackers can now run code on your server without logging in. Bit they still need 2 of 3 signatures to touch the treasury
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.
The visibility choice matters as much as chain coverage. Trezu offers public treasuries for community accountability alongside confidential ones for internal payments, with multisig approvals in both. Teams can choose the setup each budget needs.
For team funds, the key question is whether one compromised phone can authorize a payment. A 2-of-3 setup needs independently secured keys and recovery paths. Three signer addresses on one phone still share one failure point.
15 is valid too! BIP-39 supports 12, 15, 18, 21 or 24 words. Each word encodes 11 bits: 128 bits of entropy + 4 checksum bits = 12 words; 256 + 8 = 24. That’s where the lengths come from.
For teams comparing options: NEAR Business focuses on confidential treasuries. Trezu offers both public and confidential ones, so community funds can stay transparent while payroll lives in a separate confidential treasury.
Appreciate you using Trezu 🤝 And fair question — there is real overlap. Both products offer multichain treasury management, multisig approvals and confidential payments.
A key difference today is that Trezu supports both public and confidential treasuries, while NEAR Business offers confidential ones only. Teams can use Trezu for transparent community funds and private payroll through separate treasuries.
So for confidential treasury management, the use cases overlap directly. Trezu also covers teams that need public transparency.
Trezu gives teams public treasuries for community funds, confidential ones for payroll.
Already used by 50+ teams, with $195M+ in transactions processed.
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.
