Large institutional orders still leak the moment they hit a shared mempool.
That is when slippage and front-running begin.
Cocoon keeps the order book on operator-owned infrastructure, so it never touches a shared mempool.
ZK proofs still let regulators verify totals and
Empowering industries with trustless, decentralized software innovations.
dsc.gg/erigon
- Client diversity solves one failure mode: no single codebase running the whole network. There's a second one, one layer down: most RPC traffic flowing through a handful of providers. That's the gap we're working on with @lavanetxyz.Erigon x Lava. 🌋 Erigon is an Ethereum execution client: the software that downloads the chain, executes every transaction, and serves data to validators, wallets, and apps. By storing state in flat key-value tables with snapshot-based history, a full archive node fits in
- Erigon v3.5.4 "Tidal Tails" is out! 🚀 Key benefits: • Fixed a critical memory leak in the RPC gzip path that was eating ~9-15 GiB/day on archive nodes. • Better path handling: --datadir now properly expands ~/ and $VAR on all platforms. • Drop-in upgrade from v3.5.3—no
- Selective disclosure is the whole point. A market wants privacy. A regulator wants assurance. Usually a venue can only offer one of them. Cocoon offers both: the order book stays sealed, while a proof lets a regulator check totals and exposures directly. No raw trade log
- Erigon v3.5.3 “Tidal Tails” is live 🌊 Recommended bugfix upgrade from 3.5.2 with no re-sync required (drop-in update): - Restores `logs/newReceipts` notifications on resumed mid-blocks - Fixes trace-path panic on null tip txs - Fixes JSON-RPC batch deadlock (`handleBatch`)


