📣 Erigon v3.8 Watery Whiskers is out! Glamsterdam hits Hoodi on 26 October. Watery Whiskers is the release that schedules it, with a steadier Caplin for validators, faster execution and RPC, and better protection from crowding peers. Upgrade your Hoodi nodes before the fork: https://t.co/7lZ4Xn6eMZ

Running an Ethereum node used to mean running two of them. An execution client and a consensus client. Two processes, two datadirs, two config files, two upgrade schedules, and a JWT secret between them that fails in a way nobody enjoys debugging. Erigon ships Caplin, a consensus layer embedded in the same binary. It is on by default, so the plain command is the whole setup, and there is no separate disk store for it either. It is not a cut-down version: → --caplin.states-archive for historical beacon states → --caplin.blocks-archive for full block history → --caplin.blobs-archive for historical blobs For anyone running an op-node, --caplin.blobs-immediate-backfill populates the last 18 days of blobs up front instead of waiting for them to trickle in. The design reason is worth more than the feature. The two layers were split across two processes for historical reasons, not because the data wants to live apart. Putting them in one binary removes a category of operational failure rather than optimising it. https://t.co/Pzjp6ZBqTY #Erigon #Ethereum

⚡️ Erigon v3.6 is live! - More reliable block production - Bounded disk usage on pruned nodes - Merges up to 2-3x faster on less RAM - A leaner node overall Upgrade in place, no re-sync required. Onward! https://t.co/e0BXLtkmZR #Erigon #Ethereum #Gnosis https://t.co/WoPh5NX9I3

A contract shipped without the event you needed. The data is all in the chain history, but the log was never emitted, so nothing indexes it. The usual fix is to re-execute the range yourself and rebuild the state by hand. Erigon's overlay namespace does it as a query instead. You supply a version of the contract with the events you wish it had emitted, the node replays the historical blocks against that bytecode, and you get back the logs it would have produced. Nothing is deployed and no on-chain state is touched. overlay_getLogs runs it across a block range. overlay_callConstructor gives you the deployed bytecode to start from. Why it works this way: the state is already there, and Erigon keeps history as immutable files it can replay cheaply. Retro-fitting observability is a read, not a migration. The constraint is honest. Overlay replays historical state, so it needs a node that still has it, and the call fails on pruned blocks. Enable with --http.api=...,overlay https://t.co/6Ugkt9PYUW #Erigon #Ethereum

Erigon pulls historical data over BitTorrent, not the Ethereum p2p network. The reason is incentives: nobody is paid to serve old blocks, so peers for that data are scarce and unreliable. Snapshots are immutable files, content-addressed, perfect for a distribution protocol. Two sources feed the same download. The P2P swarm, and webseed, plain HTTPS servers we host that expose the same files. The torrent client treats a webseed as a peer holding 100% of the pieces, so a new node never waits for peers to appear, while the swarm absorbs the load as a file gets popular. Our bandwidth cost falls as adoption rises. No extra trust either way: every piece is checked against hashes shipped inside the binary, whether it came from a peer or from us. Snapshots are pulled once, at node creation. After that the node builds its own segments, then seeds them back. https://t.co/J4c5v4DfgS #Erigon #Ethereum

At institutional size, a public mempool turns intent into signal. That is where slippage, frontrunning, and copy trading start. Cocoon keeps the order book on operator infrastructure, so the trade never hits a shared mempool. ZK proofs still let regulators verify totals and exposures. Privacy to the market, provability to the regulator. https://t.co/ZEPsuieOcf #Cocoon #Ethereum

Running RPC infra? Two things worth knowing: - Erigon serves RPC from a separate daemon process, so you can scale the query layer independently of the node following the chain, or run it remotely. - Every release since 3.1 has focused on performance and stability at chain tip: 4x smaller chaindata, non-blocking startup, parallel block execution on by default, and concurrency limits that keep ‘eth_getBlockReceipts’ latency flat at high request rates. Serving traffic on @lavanetxyz? We're helping operators get set up on Erigon, reach out!

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 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`) - Tightens RLP tx decoding for safer validation - Makes `eth_getLogs` limits tunable via `--rpc.logs.querylimit` - Fixes Caplin sync ETA overflow/underflow Upgrade for more reliable RPC + subscription behavior with minimal operational risk. https://t.co/SZim0KTHRh #Erigon #Ethereum

A large order only needs to be seen once to be beaten. On a public chain it waits in the mempool in full view, and bots position ahead of it before it ever executes. The fill you get is worse than the price you saw. Cocoon keeps the order book off any shared mempool, so there is nothing to race, and zero-knowledge proofs keep the matching provably fair. https://t.co/ZEPsuieOcf #Cocoon #Ethereum