Candide

tether.wallet runs on Candide. We operate the bundler and paymaster inside Tether's self-custodial wallet. Users pay fees in USD₮, XAU₮, and USA₮. No native gas token. Built on @Safe smart accounts and ERC-4337. Tether can switch wallet infra anytime, no migration.

How it happened, and why Tether chose an open standard: candide.dev/blog/tether-op…

tether.wallet runs on Candide. We operate the bundler and paymaster inside Tether's self-custodial wallet. Users pay fees in USD₮, XAU₮, and USA₮. No native gas token. Built on @Safe smart accounts and ERC-4337. Tether can switch wallet infra anytime, no migration.

Banks don't move at the speed you do. Today we're launching El Dorado Business: The Multisig Account for Internet Businesses. One account to move money across the globe, with or without a US entity. Built on @tempo

Multisig signers should be able to verify the transaction, not just trust the interface. Safe OpenSig by @candidelabs helps Safe signers avoid blind signing with on-device transaction simulation, independent state verification, and clearer checks before hardware wallet approval. Learn more: youtube.com/watch?v=hQI88j… Support: qf.giveth.io/project/safe-o…

0/ Clear signing is now live. An open standard to end blind signing, making human-readable transactions default. This effort brings a major UX and Security upgrade to transaction signing on Ethereum.

@ztzsol Funny enough, the opposite. We built Safe OpenSig through all of 2025 the "old" way. Development was nearly complete right as agentic coding actually became useful. We use it now for fixes and new features. You can inspect its full commit history if you are curious

@candidelabs I have a suspicion that anthropic has written at least 80% of your frontend code 😆

Ethereum Foundation. $ 187M Safe multisig. 2 signers pending on a 10,000 ETH transfer. This is what verifying before signing with Ledger looks like, without blind signing.

@CAPTINDELTA Mobile only. IOS and Android. A chrome extension runs on the same machine as the interface you're verifying. If that's compromised, so is the extension. Your phone is a separate device. It acts as an independent verification layer.

@candidelabs Avaliable on chrome?

We simulated and verified this tx locally 2 hours ago, and showed the signer exactly what they'd see on their Ledger. Now it's been executed. x.com/ethereumfndn/s…

Safe OpenSig simulates safe transactions locally on your phone, verifies state against multiple nodes, and mirrors the exact Ledger screen before you sign. Free to use candide.dev/opensig

Safe OpenSig simulates safe transactions locally on your phone, verifies state against multiple nodes, and mirrors the exact Ledger screen before you sign. Free to use candide.dev/opensig

Approving a Safe multisig transaction means trusting the RPC node and infra behind the UI. $290M was stolen last week through compromised nodes. Safe OpenSig verifies onchain state across multiple independent nodes before you sign with your Ledger.

Safe OpenSig simulates safe transactions locally on your phone, verifies state against multiple nodes, and mirrors the exact Ledger screen before you sign. Free to use candide.dev/opensig

You can stop blind trusting RPCs. Before showing you what a transaction does, Safe OpenSig requests a Merkle proof from multiple independent nodes. They have to agree on the state. One compromised RPC can't pass it. Verified state. Then simulate.

@hell0men thanks! and remember: simulation shows you what's expected, but it is not a guarantee. things can change between when you sign and when the transaction lands onchain like MEV

@candidelabs Cool, but anyway, easier to sign with full details on the screen fitting all data.

Frax Finance. $35M Safe multisig. 3 out of 5 threshold. 1 signer pending on a 17k frxUSD transfer. This is what verifying that tx looks like, without blind signing.

Impressive! I am going to start incorporating this into my airgapped signing setup.

@jacobwillemsma great idea! worth exploring further

@candidelabs A cool idea would be to have a secured agent which runs this software locally as well be a signer on the wallet & only sign if everything comes back ok!

@penzjun @safe 2/2 it verifies state against multiple independent nodes using merkle proofs. all nodes must agree or the simulation is rejected. at bybit, that would have flagged it immediately: operation: delegatecall. safe singleton replaced with attacker's contract. signing stops there

@penzjun @safe 1/2 the bybit attack worked because the browser showed one transaction and the contract executed another. decoding calldata from the same compromised browser just confirms the attacker's version of events. opensig runs on your phone, isolated from the browser

@hell0men 2/2 then it validates that against multiple independent nodes using cryptographic proofs. all nodes have to agree, or the simulation gets rejected. by the time you confirm the hash on your ledger, you already know what you’re signing

@hell0men 1/2 yes, because opensig verifies the transaction before you ever touch your ledger. it runs a local simulation on your phone showing exactly what will happen: token transfers, approvals, warnings.