Software developer working on go-ethereum.

✨ 24H in Ethereum Core Dev | April 10 ✨

 - ACD: final shaping of Fusaka hardfork
 - Reducing GossipSub overhead
 - peerDAS devnet 6 live
 + More

Feat. PG members: @vdwijden @terencechain Améziane Hamlat, Csaba Király & more!

a collective funding mechanism for +170 Ethereum L1 R&D maintainers 🌿 stewarding our commons infra


peerDAS devnet 6 live
https://peerdas-devnet-6.ethpandaops.io

🚨 We are LIVE! 🚨
https://t.co/gycFQnuHP9

Very productive AllCoreDev call today

Final shaping of the Fusaka hardfork!

MariusVanDerWijden

ACD
https://x.com/vdWijden/status/1910353322495582685

Améziane compares besu parallel tx processing performance to theoretical max

summary_large_image

Research reveals that 64.85% of Ethereum transactions can be parallelized, enabling a 2-3x improvement in potential throughput.

Report from Sei Research Initiative examines how execution models and dependencies impact Ethereum’s scalability.

Full Blog: https://t.co/vvhtAzHuDw

In @HyperledgerBesu, we've been ahead of the curve — with parallel transaction execution implemented since 2024.
With recent conflict detection improvements, we're hitting ~60% parallelism : https://t.co/EfRZEgTAYu.

Améziane Hamlat

Améziane compares besu parallel tx processing performance to theoretical max
https://x.com/A_HAMLAT/status/1910067829396635872

Terence shares context on Prysm's fork choice implementation

Wrote a short doc on Prysm's fork choice implementation using a doubly linked list. Fork choice can feel intimidating—often custom and outside the spec—but it doesn’t have to be. Hope this helps demystify it a bit
https://t.co/nDUMEcL4K3

terence

Terence shares context on Prysm's fork choice implementation
https://x.com/terencechain/status/1910334061198901610

Csaba shared an EIP on reducing the GossipSub overhead in clients

summary

New post on https://t.co/neli1nzo0Y!

PPPT: Fighting the GossipSub Overhead with Push-Pull Phase Transition

By:
- cskiraly

🔗 https://t.co/s4YWnh1nCr

Highlights:
- GossipSub has a significant bandwidth overhead due to message duplicates during peer-to-peer redistribution.
-

ethresearchbot

Csaba shared an EIP on reducing the GossipSub overhead in clients
https://x.com/ethresearchbot/status/1909978651774390663