erigon.eth

Empowering industries with trustless, decentralized software innovations.

[erigon.eth @ErigonEth]

See also the full release notes

https://t.co/mtMrObUlFo

Happy syncing! 🦦

[erigon.eth @ErigonEth]

📢Erigon v3.7 Velvet Vibrissae is out!

State-root computation now runs in parallel by default. Together with parallel execution from v3.5, both halves of block processing now use every core.

Plus faster RPC, receipts kept by default and Glamsterdam on Sepolia.

https://t.co/YWt0Hj8V97

[erigon.eth @ErigonEth]

#Erigon #Ethereum

[erigon.eth @ErigonEth]

📢 Erigon v3.6.1 is released! Bugfix and security release, recommended for all users.

Drop-in from 3.6.0, no re-sync.

• Valid local snapshots no longer silently replaced
• Caplin honours peer bans on inbound connections, not just outbound dials
• Syncing beacon endpoints return 503, not 500 — your alerts stop firing at startup
• grpc bumped for two HIGH-severity CVEs

Full notes: https://t.co/Ons0B9tzQX

#erigon #ethereum

[erigon.eth @ErigonEth]

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.eth @ErigonEth]

Release Notes:

https://t.co/2XDQilB8ve

[erigon.eth @ErigonEth]

⚡️ 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

[Lava Network 🌋 @lavanetxyz]

Reminder: Erigon Providers Call is tomorrow. 🌋

12:00 PM UTC · Lava's Discord
Ask anything about running @ErigonETH nodes or provider setup.

📍 https://t.co/tVXtFkzw6Z

[Lava Network 🌋 @lavanetxyz]

We're doing a live AMA; ask us anything about running @ErigonETH nodes, provider setup, or what's next.

🎙️ Erigon Providers Call
📅 Aug 21 · 12:00 PM UTC
📍 Lava's Discord server: https://t.co/tVXtFkzw6Z

Drop questions in the comments 🌋

[erigon.eth @ErigonEth]

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

[Lava Network 🌋 @lavanetxyz]

.@ErigonETH joined Lava to refine archive node stability and grow network load share. Electric Blue sandbox running with 11 teams. BHL sandbox launching next.

Full breakdown in the July 2026 Ecosystem Call: https://t.co/zmuZOy1t0S

[erigon.eth @ErigonEth]

@DamianCTO Sorry for the late reply here. You're right, archive RPC cost is more than disk. Memory leaks like this one compound under sustained trace/debug traffic.

v3.5.5 is out now with additional fixes for validators and archive operators if you haven't upgraded yet!

[erigon.eth @ErigonEth]

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 re-sync needed.

Perfect for operators of high-traffic RPC endpoints looking for stability and efficiency.

#Erigon #Ethereum

https://t.co/2uuCYYovSi

[erigon.eth @ErigonEth]

@kitsunedevs gRPC, not HTTP. The rpcdaemon connects to Erigon's internal API via --private.api.addr (default 127.0.0.1:9090).

This lets you run multiple rpcdaemon instances on separate machines, all pointing to one Erigon node.

For more detailed info see https://t.co/lZS6GXWM8m

[erigon.eth @ErigonEth]

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!

[zentar @0Mosterin83293]

@lavanetxyz @ErigonEth that makes total sense, it’s all about redundancy.

[erigon.eth @ErigonEth]

Exactly. An encrypted mempool protects the whole base layer for everyone; venue-level privacy only covers who opts in. By design, Cocoon targets institutions that also need on-chain KYC and selective disclosure to a regulator, which a base-layer mempool can't provide. A different scope which is complementary, not competing.

[erigon.eth @ErigonEth]

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

[erigon.eth @ErigonEth]

Good question! Cocoon doesn't touch Ethereum's mempool at all. It's a permissioned venue that settles to L1; the confidentiality is local to the venue, not a change to Ethereum's base layer.

So Ethereum stays exactly as permissionless as before; the trade-off is opt-in, at the venue, for participants who need it.

[erigon.eth @ErigonEth]

📢Erigon v3.5.5 released!

Security + bugfix release. Recommended for all users.

Block proposers: Fulu blinded-block panic fixed
Archive operators: logIndex regression fixed (v3.5.1–v3.5.4)
External CL users: payload timing fix
Plus 4 security bumps.

Drop-in from v3.5.4, no re-sync.

https://t.co/jWrGPbHJLJ

[erigon.eth @ErigonEth]

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

[Lava Network 🌋 @lavanetxyz]

The team behind one of Ethereum's most influential node clients is paying closer attention to Developers.

@ErigonETH architecture shaped how clients like Reth approach node design. Now the focus is expanding to better support for Developers running RPC daemons and core nodes inside the Lava ecosystem.

That's a meaningful shift. 🌋