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.

🗳️ New Proposal for Safenet Aegis is now live on the Safe{DAO} forum. Here is a breakdown ↓ It asks to fund the first production-ready protocol version built to secure @safe Multisig and the wider ecosystem in Q4. Threats to self-custody are only increasing, and most defences today are still just warnings, not enforcement. Safenet Aegis is changing that paradigm. 🔰 Safenet is a decentralized network of independent Sentinels and Validators 📜 Sentinels check every transaction against a public, DAO-owned charter using their own proprietary threat detection systems 🧾 Sentinels pass verdicts. Verdicts are attested by validators onchain making security enforceable 🛡️ Enforcement happens at the account level via Safenet Guards Proposed Independent Sentinels checking transactions: @OpenCover, @IntentGuard , @hackenclub, @hexens, @BlockSecTeam and @candidelabs Proposed Validators: @gnosisdao, Core Contributors, @greenfield_cap, @SafeLabs_, @RockawayX and @bcap Safe{DAO} through this proposal, owns every fee parameter on the Safenet protocol. Safenet Aegis will ship inside @SafeLabs_ multisigs in Q4 2026. Read More ↓

Your gold. Your control. Candide handles the gas.

Years ago we watched new users give up on sending stables because apps told them to signup on an exchange to buy a second token to pay the fee. Hold gold, send gold, the fee comes out in gold. No gas token. Gold from your pocket only works if the pocket doesn't need a manual.

One Forwarding Address, seven chains to deposit stables from, funds land in the user's main account on Arbitrum. Instant, non-custodial deposits where users need them the most. ¡Felicitaciones, El Dorado!

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: piped.video/watch?v=hQI88j44… Support: qf.giveth.io/project/safe-op…

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.

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

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

A few days ago we launched Safe OpenSig. The thing that surprised me most was how misunderstood blind signing is. Even among people who think seriously about this. So let me explain what it actually means, step by step. Step 1: You open Safe. A transaction was proposed. You review it. You see decoded details. A transfer, a contract call, an ownership change. Looks right. But three things can compromise what you see before you ever touch your hardware wallet. The interface can be compromised through: a tampered frontend, a poisoned backend, a malicious browser extension, a hijacked DNS record, or a compromised dependency deep in the frontend's supply chain. You wouldn't know which one. Step 2. You try to verify. Smart move. You copy the calldata and paste it into an external tool to decode it. But where did you get that calldata? You copied it from the same interface that may be compromised. The verification is tainted from the start. The only review that means anything is one where you constructed the calldata yourself, offline, from scratch. Without touching the UI at all. That's not a realistic workflow for a n-m multisig signing transactions every week. Step 3. You connect your Ledger. This is where people assume the hardware takes over as the trusted layer. It doesn't. For anything beyond a simple ETH transfer, your Ledger can't decode the transaction. It shows two hashes. Domain hash. Message hash. nitter.net/heymarcopolox/status/2… Step 4. You approve the hash. You always do. This is the attack surface. There is no moment in this workflow where you can verify that what the interface showed you matches what the hardware is actually committing to. The security layer you thought existed doesn't. What Safe OpenSig does Before you touch your Ledger, Safe OpenSig simulates your Safe transaction locally on your mobile phone, away from your desktop. Two devices means two independent verification layers. It verifies state against multiple independent nodes, and shows you a pixel perfect mirror of what your Ledger screen will display. The hash gets a face. You know what you're signing before you sign it. candide.dev/opensig