All Core Devs - Consensus (ACDC) #163, August 21, 2025

Protocol Calls & happenings
,
4

ACDC #163 Action Items

  • Continue work to produce trunk branches for Fusaka with target by end of next week
  • fusaka-devnet-5 will launch once those are ready (est. 1 Sep)
  • Non-headliner Glamsterdam EIPs should be proposed by the time Fusaka mainnet releases are out

ACDC #163 Summary
Fusaka

  • fusaka-devnet-3 undergoing a non-finality test, restoring back to default state
    • currently ~80% participation achieved
  • Some client updates
    • Lighthouse working through syncing issues
    • Memory leak in Reth, reported to team
  • fusaka-devnet-4 was launched, but taken down due to:
    • BPO spec ambiguity resulting in chain split
    • Syncing issues mentioned above
  • fusaka-devnet-5 launch planned for week after next
    • Same scope as devnet-4, no spec changes from devnet-3
    • Large devnet like devnet-4
    • Waiting on teams to have trunk branches ready, which pipelines things for testnets and mainnet

Team Readiness Updates

Spec & Testing Updates

  • Minimal preset parameter adjustment merged for testing
    • Enables larger validator counts on minimal preset
    • Helps with lighter devnet operations
  • Justin Traglia releasing alpha.5 spec version today
    • Includes parameter changes and additional updates

Security Analysis - BPO Fork Version

  • Theoretical attack vector analysis completed across three areas:
    • Wasteful work through minority fork block fetching
    • Potential mesh advantage for attackers serving unavailable data
    • Cross-feeding attestations between forks
  • Conclusion: Extremely theoretical with 1 in 129 million probability
    • Requires sophisticated attacker, not a realistic concern for mainnet
  • Plan to update EIP with trade-off documentation between fork digest vs fork version solutions

Glamsterdam

1 Like