@EFDevcon 8 Mumbai was a memorable experience for @EIPsInsight. 💙
Our Impact Booth brought us closer to the Ethereum community, giving us the opportunity to showcase our work and hear valuable feedback.
Thanks to @ether_world, our exclusive media partner, for capturing the journey.
Watch the recap 👇
Can AI help Ethereum EIP editors manage 550+ open PRs?
That was one of the interesting discussions at today’s EIPIP meeting.
A few highlights:
- @JochemBrouwer96 shared AGENTS.md:
AI-assisted reviews will be piloted. Comments only, no auto-merging. Human oversight stays.
https://t.co/lxQP4R2HTn
- @EIPsInsight demoed EIP Builder showcasing support to authors & editors to draft, validate & review proposals.
https://t.co/jXacRil6cv
Editors discussed potential integration with https://t.co/FOwGnx8qyw.
- Exceptional PR merging (Glamsterdam EIPs):
Editors reaffirmed that PRs require author approval, even for factual corrections.
- EIP Coordinator: CfI will be closed in favor.
PR to update EIP-1 with the Coordinator role/name looks good and can be merged.
https://t.co/bX96HtFUxI
- Keeper of Consensus: Election remains open for 30 days. CfI will be updated to reflect the voting window.
https://t.co/IZLV1eMiDa
- PR backlog: EIP Editors encouraged to join Office Hours to help move reviews forward.
AI can help us scale EIP reviews, but human oversight, author ownership and process neutrality must remain at the center.
Next EIPIP: Dec 16.
🔴 FOCIL Breakout #046 recap is live on @EIPsInsight.
A few key updates from today’s discussion:
→ PR #5769 green-lit, with merge targeted for the next breakout
→ IL timing, retention and proposer deadlines discussed across consensus PRs
→ Open questions around IL equivocation proofs and gossip propagation
→ PQ FOCIL gets its own dedicated breakout next week
Full recap, decisions, transcript, recording and call artifacts:
https://t.co/l8fBvbzYmV
#Ethereum #FOCIL #Glamsterdam
Ever wondered how to keep up with Ethereum’s EIPs, network upgrades and core developer discussions?
We put together a quick walkthrough of EIPsInsight, showing how you can follow the work shaping Ethereum, all in one place.
🎥 Watch the explainer:
https://t.co/ZZ1VuPpj2c
#Ethereum #EIPs #EIPsInsight
🔴 RPC Standards #038 recap is live on @EIPsInsight.
A quick one this time, with a focus on moving execution-apis forward.
→ Batch of docs, fixes and eth_simulate PRs set for merge
→ Outstanding Reth and Besu test failures discussed, with fixes awaiting merge
→ No objections raised to the agenda PRs. Chase plans to merge by end of day
→ More controversial PRs deferred to the next call
Full recap, transcript, recording and call artifacts:
https://t.co/5gsirx92HQ
#Ethereum #RPC #ExecutionAPIs
🔴 AllCoreDevs Testing #103 recap is live on @EIPsInsight.
→ ~200 compatibility findings across EIP-8037/8038
→ Auditors and EF shared their findings on affected contracts
→ App teams raised concerns around gas assumptions and contract immutability
→ No final decision yet. Discussion continues Thursday at ACDE.
Full recap, transcript, recording and all call artifacts:
https://t.co/XVyuTZT9oc
#Ethereum #Glamsterdam #EIP8037 #EIP8038
⏰ AllCoreDevs Testing #103 is coming up today at 14:00 UTC.
Today’s agenda:
→ Glamsterdam: EIP-8037/8038 compatibility investigations, audit findings and potential impact on deployed contracts.
→ Independent findings from ChainSecurity and Dedaub, alongside EF’s internal investigations and application-team feedback.
→ Payload binding: choosing between two proposed solutions to unblock the consensus-spec release.
→ Open Q&A on affected contracts, audit findings and outstanding concerns.
Featuring contributions from @vdWijden , @dedaub , @trooocher , @nero_eth , and @omw_to_the_moon .
Join the call and follow along:
https://t.co/yBNdpDDqY7
#Ethereum #ACDT #Glamsterdam #EIP8037 #EIP8038
⏰ RPC Standards #38 is happening today at 15:00 UTC.
Today’s agenda covers a packed set of Execution API updates:
→ Transaction validation across fork boundaries and handling transaction fields for inactive forks.
→ Updates to eth_createAccessList, eth_getProof and eth_simulateV1.
→ Opcode tracer specification clarifications.
→ New test fixtures for gas behaviour at fork boundaries and state overrides.
→ Engine API updates, including the proposed payload witness endpoint.
Join the discussion with @naps_thelma and the RPC Standards contributors:
https://t.co/5jUAmh8dXY
#Ethereum #RPC #ExecutionAPI #EIPsInsight
⏰ AllCoreDevs Testing #103 is coming up today at 14:00 UTC.
Today’s agenda:
→ Glamsterdam: EIP-8037/8038 compatibility investigations, audit findings and potential impact on deployed contracts.
→ Independent findings from ChainSecurity and Dedaub, alongside EF’s internal investigations and application-team feedback.
→ Payload binding: choosing between two proposed solutions to unblock the consensus-spec release.
→ Open Q&A on affected contracts, audit findings and outstanding concerns.
Featuring contributions from @vdWijden , @dedaub , @trooocher , @nero_eth , and @omw_to_the_moon .
Join the call and follow along:
https://t.co/yBNdpDDqY7
#Ethereum #ACDT #Glamsterdam #EIP8037 #EIP8038
@VitalikButerin What stands out: it’s not just a defense of 8037, but an honest map of what it breaks (OP-stack bridges, 4337, some 8038 cases) and how to mitigate.
That transparency is what the affected app devs actually needed.
In Last Call now 👇
https://t.co/xatr7gmQrl
Six ERCs, six different challenges in real-world asset infrastructure.
From asset anchoring (ERC-8325) to compliance records (ERC-8328) and NAV snapshots (ERC-8330), @kula_dao's proposals explore new interfaces for Ethereum.
Watch Taran's presentation from Devcon 8.
From ERC-8325 to ERC-8330, @kula_dao's proposals explore the infrastructure needed for interoperable, auditable real-world assets.
Watch Taran's full presentation from Devcon 8 Mumbai on EtherWorld.
#Ethereum#RWA#Devcon8
https://t.co/dKPFtcXxht
@iamdhanushlnaik Good catch. The Hoodi postponement is easy to miss when the old activation date is still listed in the Meta EIP.
We’re tracking the updated testnet status on EIPsInsight, so the rollout details are easier to cross-check against the spec:
https://t.co/5KmUrYp4qw
a big thank you to everyone who stopped by the @EIPsInsight booth at Devcon! 🫶
loved getting to chat with so many of you, hear your thoughts, answer questions, and exchange ideas about ethereum and its ecosystem.
every conversation made the experience more special. really glad we got to connect. until next time! ❤️
@EIPsInsight at @EFDevcon 8 Mumbai 🇮🇳
From showcasing the platform at its Impact Booth to connecting with Ethereum developers, researchers, & contributors, it was an exciting four days.
As EIPsInsight's exclusive media partner, we're bringing you a look back at the experience 👇
https://t.co/cMr5hSvOk2
ACDC #191: post-quantum security is taking priority in Ethereum’s Hegota planning. 🔐
A few key takeaways from the call:
→ BLS-decoupled consensus is off the table. DC work moves forward as PQ-DC.
→ EIP-8483 received PFI for Hegota, enabling pre-fork registration of post-quantum keys for validators and builders.
→ EIP-8198 (Quick Slots) was deprioritized as its champion shifts focus to PQ work.
→ LeanVM is targeting production readiness in January 2027, with formal audits beginning February 1.
FOCIL and other Hegota discussions remain open, with more research needed before decisions are made.
Read the full call summary, decisions and action items 👇
https://t.co/srMR8gbbbM
Every EIP has a journey, from the first draft to reviews, revisions, and eventually becoming a standard.
Understanding that process is essential to understanding how Ethereum evolves.
A great opening keynote by @poojaranjan19 at EIP Hub @ Devcon 8.
Watch the session 👇
New post on Eth Research!
Seam: verifying Zcash headers on Base with EIP-152, and proving shielded payments without linking the chains
By:
- Himess
🔗 https://t.co/vQRjgtBsGM
Highlights:
- A permissionless on-chain relay on Base verifies Zcash block headers against Zcash consensus rules (Equihash via the EIP-152 BLAKE2b precompile, difficulty adjustment including NU7’s 25-second blocks, timestamp rules, PoW target, and most-work fork choice), so contracts can read Zcash’s best chain without trusting a committee or bridge.
- Per-header cost is ~626k gas on average (with Equihash ~361k gas); following Zcash at 25-second blocks is ~3,456 headers/day (~2.2×10^9 gas/day), estimated around ~0.01 ETH/day at ~0.005 gwei on Base.
- The relay design handles reorganizations safely: it avoids gas-cost blowups by not clearing orphaned height indices, ensuring attackers can’t freeze the relay by forcing expensive state rewrites; feeders can delay updates but cannot make invalid headers be accepted.
- On top of the relay, a RISC Zero zkVM proof (Groth16-wrapped) can prove a shielded Zcash payment meets an app-defined condition (minimum value, receiver commitment, memo includes a payment reference) and is included under ZIP-221/ZIP-244 commitments anchored to a header the relay has—without revealing txid, note, block, or address on the EVM chain.
- It’s experimental: testnets only and unaudited; security depends on trusted deployment inputs (checkpoint/parameters), liveness depends on header feeders, proofs currently require GPU for practical performance, and the main security bound is economic (apps must require sufficient cumulative work, not a simple confirmation count).
ELI5:
Seam is like putting a mini “Zcash verifier” inside Base (an EVM chain). Instead of trusting a bridge operator to tell Base what happened on Zcash, a smart contract checks Zcash block headers itself (the hard math puzzle, timestamps, and difficulty rules). Then, if someone wants to prove they paid you on Zcash without revealing which transaction or address it was, they can generate a zero-knowledge proof that says “a real shielded payment of at least X went to the receiver this app expects,” and Base can verify that proof cheaply—without learning the private details or linking the two chains by publishing a txid.
Encrypt The Mempool #012: a few key updates from the latest call.
→ The optionality problem is being split from EIP-8184 (LUCID) into a separate proposal.
→ EIP-8491 introduces a key publisher priority list to address probabilistic front-running.
→ Encrypted mempool is unlikely to make I-Star. J-Star is the earliest realistic target.
The prototype continues in the background, without pressure to meet a fork deadline.
cc : @robocopsgonemad@AnotherJannik@jtraglia
Full recap: https://t.co/DGDjle21OZ