I've brought this up a few times over the past couple years, most recently on a Safe call - the centralized Transaction Service is both a security risk and a missed opportunity for sustainable SAFE token utility. So I decided to flesh out the full architecture... 🧵

The problem: Every Safe transaction sits in a centralized database while collecting signatures. This gives backend access holders visibility into: • Large treasury swaps before execution • Security patches being deployed (giving attackers time to simulate exploits) • Governance upgrades before deployment • Any transaction before it hits the mempool

Meanwhile, sophisticated VCs and DAOs already know this and run private transaction infrastructure. But everyday Safe users? They're left exposed to MEV and surveillance. This creates a two-tier system where security depends on technical sophistication.

How it works: 📦 HPKE encryption protects transaction data end-to-end 🌐 @waku_org v2 handles gossip and storage 🔒 @eigenlayer AVS provides economic security via staking/slashing 💰 Tiny DA fees flow to SAFE stakers and operators

@Waku_org @eigenlayer The magic is in the signature convergence: multiple signers can discover and co-sign transactions asynchronously, even if they act simultaneously. CRDT merge operations guarantee everyone converges to the same final state. No coordination needed, no staying online required.

@Waku_org @eigenlayer For users, it's simple: toggle "Private Relay" in Safe UI, pay a tiny fee (fraction of gas costs), get the same pre-trade privacy that institutions already have. All while maintaining full on-chain accountability and transparency post-execution.

@Waku_org @eigenlayer For SAFE token holders: Finally, a revenue stream that's impossible to undercut because it's core infrastructure. As Safe adoption grows, so does demand for secure relaying. Mission-aligned monetization that reinforces decentralization instead of fighting it.

@Waku_org @eigenlayer Users can pay fees in ETH or SAFE tokens. When paid in SAFE, it creates consistent buy pressure and utility beyond governance. The more Safes that opt into private relay, the more SAFE gets used as a medium of exchange for security services.

@Waku_org @eigenlayer This isn't theoretical - it's built on proven primitives: • HPKE is IETF standard (RFC 9180) • Waku v2 is production-ready P2P messaging • EigenLayer AVS framework handles the economics • Safe's execution layer stays exactly the same

@Waku_org @eigenlayer The vision: Every Safe user gets institutional-grade security by default, SAFE token holders earn sustainable yield, and we eliminate the last centralized chokepoint in Safe's architecture. Win-win-win. @safe

@Waku_org @eigenlayer @safe Full technical details and forum discussion: Forum post: White paper: