One multi-sig, any crypto, total control. Manage your team's capital from a single dashboard without ever giving up your keys.
- Tweets 227
- Following 10
- Followers 527
- Likes 295
"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.
1
1
12
452
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)
7
255
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.
2
7
293
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:
"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.
3
87
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.
1
8
205
Treasury management is a long sequence of small decisions, and most teams make each one on the spot.
Who requests a payment, who releases it, how many approvals it needs, how long those approvals stay valid, and who gets to see any of it.
On Trezu you decide all of that once, at setup. The person who queues a payment doesn't release it. Approvals have a threshold and a window, and anything that doesn't clear within that time expires.
Payroll goes out in one batch, and each payment leaves a receipt that your team can read but a block explorer can't. One account holds 150+ assets across 35+ chains, so everything sits together and swaps skip the bridge. Public or confidential is your call at setup, signing works with a Ledger and secured with passkeys, and the whole thing is self-custodial.
More than 433 teams use Trezu as their multisig for stablecoins and native assets, securing $100M in AUM.
6
145
If someone stores your data, they'll always be hunted for it. The Revolut attack is a harsh reminder of the risks of centralized platforms. When you rely on third parties, you create a honeypot of sensitive data.
No information shared = no risk of it leaking.
That's why we built Trezu as non-custodial infrastructure, to eliminate this risk. There's no central database of sensitive info to hack or request.
⚠️ ALERT: Revolut falls for a FAKE government request, exposing sensitive personal information of customers in a disturbing data breach.
Revolut disclosed that it complied with a fraudulent government request using a spoofed official email and valid credentials, exposing PII belonging to a group of customers.
The leaked data reportedly includes passports/driving licences, verification selfies, names, DOBs, occupations, home addresses, emails, phone numbers, IBANs, account statements and full transaction histories, including Bitcoin activity.
No customer funds were reportedly lost and Revolut says its systems were not hacked.
The company has notified affected users and regulators and blocked the source.
Social-engineering attacks are on the rise, with attackers increasingly exploiting human trust and weak verification processes rather than technical vulnerabilities.
1
8
324
One compromised laptop shouldn't be enough to drain a company's treasury. @stacy_muur walked through how role-based permissions and multisig approvals actually work in Trezu. Worth the read if your team still runs on one shared wallet.
As a founder, I’ve been trying to move away from relying on one seed phrase to protect everything I own onchain.
So should YOU.
I came across @TrezuApp, which uses a non-custodial multisig to remove the single point of failure that comes with relying on one wallet or seed phrase.
Here’s a quick TL;DR ↓
1️⃣ Architecture
The treasury is a multisig smart contract on @NEARProtocol.
Trezu uses a multisig setup where each team member connects with their own wallet.
Nobody shares one login, and Trezu doesn’t hold the team’s private keys, so all the funds remain under the treasury’s control onchain.
More importantly, responsibilities are separated by permissions:
→ Requestors can create payment, swap, staking, or withdrawal requests, but can’t approve them.
→ Ops team can approve or reject requests, but can’t edit them or change the treasury setup.
→ Governance controls members, voting thresholds, and request settings, but can’t approve normal payments.
In a nutshell, an employee from the Marketing department can prepare a $100K payment without having the ability to actually move $100K.
Execution still depends on the approval threshold the company configured, for example, a 2-of-3 multisig.
As a founder, you can delegate operations without delegating unilateral control of the money.
2️⃣ Approval Layer
When someone creates a payment request, they have to enter the wallet address, token, amount, and network before it goes to Finance or Ops for review.
The responsible department sees exactly who's getting paid, how much, which token, and any comment the Requestor left with it.
And because the request can't be edited once it's submitted, nobody can change the details after the first person has looked at it.
If there aren't enough tokens in the treasury, the payment can't be approved until the team tops it up. Once it's completed, Trezu generates a PDF receipt as proof of payment.
I know it sounds like boring admin stuff, but crypto payments are irreversible, and having the details tied to the request means more than "trust me bro".
3️⃣ Bulk Payments
For bulk payments, a Requestor can upload a CSV with wallet addresses and amounts, or enter them manually. The whole batch goes through as one request.
One limitation worth knowing is that everyone in the batch needs to be paid in the same token.
So it’s ideal for $USDC contractor payments, but not for one batch where everyone wants a different asset.
Finance then reviews the batch before funds move and can reject it if anything looks off.
I bet you won’t find many founders who enjoy clicking through a million separate wallet prompts lol.
4️⃣ Self-Custody Layer
This is one of the first things I look for with any self-custody product:
→ The funds aren’t sitting in a Trezu-controlled account!
They remain onchain and are controlled by the treasury setup and the team’s signing wallets.
If the Trezu app becomes unavailable, the company can still interact with the treasury through alternative onchain interfaces or command-line tooling.
5️⃣ Multichain Infrastructure
Trezu supports treasury management across networks including @ethereum, @solana, @Bitcoin, @0xPolygon, @NEARProtocol, @SuiNetwork, @ton_blockchain, and @Cardano.
For a company operating across multiple ecosystems, that matters.
Instead of rebuilding completely different operational processes every time the company starts using another network, the team gets one place to manage treasury activity and approvals.
IMO, most teams don’t think seriously about treasury infrastructure until they DO.
Once a company has its one-year runway onchain, one compromised laptop, employee, or seed phrase shouldn’t be enough to drain everything.
That’s the real appeal of multisig that not many people get:
Delegate the work without giving any single person unilateral control of the treasury.
Trezu is free to create and has no asset or user caps. They’ve already processed $194M+ in transactions, manage $100M in assets, and are used by 433 teams.
If you're a founder struggling to manage company funds onchain without relying on one wallet or one person, check out: trezu.org/
7
262
Somewhere there is a founder whose treasury is secured by a sticky note under a keyboard.
It's one string, on one laptop, in one person's head. If it goes, the runway goes with it. And if that person is also the only one who can send payments, nothing moves without them either.
A multisig with real roles fixes both. Marketing can prepare a payment, Finance approves it, Governance sets who's allowed to do what. Nobody can move funds alone, and nobody is a bottleneck.
Delegate the work. Not the control
2
1
10
276
– "Bulk payments!" – Head of Finance
– "Bulk payments, definitely!" – Finance Ops Manager
*answered in 0.1s, without missing a beat*
That was the reply when we asked a Web3 team using Trezu: "What’s your favorite feature?"
– "Before Trezu, we had to approve every single transaction manually, one by one. With bulk payments, we just batch them and approve dozens at once. It saves us a ton of time."
We’re completely obsessed with making our users' lives easier.
1
11
258
A lot of Web3 finance leads, founders and CEOs, are NON-technical.
And that’s totally okay.
The strength of any great team lies in complementary skill sets: the finance team owns accounting, while the CEO drives revenue and GTM strategy.
But when it comes to gathering data for business and financial analytics, they struggle with raw explorers and rely heavily on dev teams just to pull transactions and close month-end reports.
We know this problem inside out from seeing how our users handled it before Trezu.
That’s why we built Trezu as an intuitive, user-friendly, and business-first solution rather than a developer tool, taking the technical chaos out of crypto financial management.
8
221
We invite everyone to experience Trezu first-hand - no email, credit card, or KYC required.
8
308
Say you run a startup that operates in stablecoins and the native tokens of a few chains or your own.
You have USDC on Base, ETH and SOL set aside for gas and operations, some staked for yield, and part of your reserves in native BTC.
The standard way to manage this is to use a separate multisig on each chain.
Each one is its own deployment. Each one needs gas, funded per signer, per network.
Every new chain your business touches adds another wallet to administer and another set of approvals to track.
Trezu runs it all from one account. We cover 150+ assets and 35+ chains.
The juggling ends on Trezu
9
223
We asked Anna from @Sweatcoin how Trezu fits into her team's day-to-day.
From signing as a team to catch mistakes early, to moving funds across chains in a minute, here's how it's made treasury ops simpler and faster 👇
2
13
679
