You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
opgeth-decoupling: audit op-devstack/sysgo direct ethclient calls (L1 vs L2) #20274
Runtime L1 wiring: l1_runtime.go, mixed_runtime.go, multichain_supernode_runtime.go and singlechain_build.go.
Dispute-game and upgrade setup: add_game_type.go, interop_zk_upgrade.go, pre_genesis_super_game.go and superroot.go.
These need no change under upstream go-ethereum.
DSL:dsl/bridge.go has the only L2 ethclient. It feeds withdrawals.ProveWithdrawalParametersFaultProofs, which reads headers and receipt Logs only, so it works under upstream.
No full-block or tx reads: there are no BlockByNumber/BlockByHash/TransactionByHash calls anywhere in op-devstack or op-acceptance-tests.
🤖 Claude says: Closing: the audit is done. Every op-devstack/sysgo ethclient dials L1, and the DSL bridge's L2 client reads only headers and receipt logs, which works under upstream go-ethereum. Nothing to migrate; details in the body.
Activity
sebastianst commentedon Oct 14, 2026
🤖 Claude says: Closing: the audit is done. Every op-devstack/sysgo
ethclientdials L1, and the DSL bridge's L2 client reads only headers and receipt logs, which works under upstream go-ethereum. Nothing to migrate; details in the body.