Trezu | Multisig treasury for Web3 teams

"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.

Nobody stole Binance’s private keys. That’s the uncomfortable part of the $6.3B hack. What’s known so far: it started, Binance says, with one engineer’s laptop. From there the attacker reached a service that submits withdrawals. Wallets on 10 chains, with different key types, produced valid signatures in about 30 minutes. The keys were safe. The system allowed to use them wasn’t. About $3B is frozen, almost all of it stablecoins that Tether and Circle could block. The ETH and BTC are still with the attacker. Same group as Bybit in 2025, according to TRM Labs. Both times the cryptography held. The process around it didn’t. So here’s the question for any team holding funds: is there anything in your setup that can sign alone? A server, a bot, one person’s laptop. We ask ourselves the same thing every day. In Trezu, every transfer waits for your team’s own approvals, and no Trezu server can approve one for you.

Google is building crypto custody for banks. Split the key, require 2-of-3 or 5-of-7, check every transfer against policy before it’s signed. Crypto teams don’t need to wait for it. Trezu already gives your treasury multi-approval today, with no custodian in the middle and every vote recorded by the smart contract.

Binance founder says no crypto wallet is 100% safe. We agree. Including the ones where someone else holds your keys.

~$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.

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.

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.

“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

$100M → $150M under management! More teams are choosing a treasury that's confidential when they need it and auditable when they don't. Thank you for building with us ❤️

Security is a spectrum. We are here for the heavy lifting.