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: 🧵

If you have been following along, I’ve been discussing a privacy-first health app I’ve been building on top of @near_ai. I’m looking for beta testers who have iPhones running iOS 16 or later. DM me if you are interested.

. @near_ai and @ilblackdragon are shy to say that they are building good AI that will protect us all from the evil AI. NEAR AI says "your own AI", "own your AI", but what they mean is that the AI that you control will be on your side in the future where corps will be using AI against you.

Just a week later, it is already old news. It is already $160M assets trusted to Trezu multichain multisig. Users love Passkeys a lot!

Confidential Intents TVL crossed $110M. This means that if NEAR is listed on @DefiLlama's Privacy Category it would be #2 after TornadoCash. However, it's not only the TVL that matters here. Short thread below.

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)

@ilblackdragon as the frontman of the @AIconference ig ads, love to see it 👀 another proud wife moment

near officially took the snapshot on sep 13 📸 you can check your rank now. allocations & claim are coming soon once near:native hits $3.33 over 3 consecutive days, allocation converts 1:1 into near:native let's see what rank 258 gets me. what's your rank fren? > near.com/login?ref=56c2p8lf

Your activity is confidential. But the tax man is calling. Export your near​.com history and share it with your accountant—along with a link that verifies its authenticity. Everyday Confidentiality. We think of everything, so you don’t have to.

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.

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/

this is very likely your last chance to join the NEAR@3.33 airdrop campaign • currently at $63M TVL • $66M reached yesterday • spike from $50M in less than a week (Sep 2) i believe we see $70M by the weekend (or earlier) then, the snapshot eligible: • $100 deposited in confidential intents • 1 confidential swap on near-com that's a minimum larger deposits and more swaps compound then near:native needs to hold above a $3.33 average for 3 days then the next campaign (NEAR@6.66) begins more below ↓

I’m excited about reaching this major milestone!

Our users motivate us to ship faster and more every day!

Test out private inference for free!

The story is @NEARProtocol. The ticker is $NEAR. My investment thesis, in 78 seconds. NFA. DYOR.