Replies: 2 comments
-
Some updates on our multi-section fault dispute game (FDG) progress:
Future actionable plans:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Major updates on Multi-Section Fault Dispute Game (FDG) from EthStorage team: Completed Enhancements:
Completed Testing for 4-Section DFG |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Goal
The objective of the proposal is to develop a multi-section fault-proof game on top of the existing bisect
FaultDisputeGame.sol
with minimal changes. The idea is to use EIP-4844 BLOB to carry 4096 claim/state hashes in eachmove()
. As a result, countering a claim by calling amove()
can create 4096 sub-claims with the following features:move()
calls to complete a game is expected to reduce from 73 (MAX_DEPTH
of Sepolia testnet) to 7 (3*12=36
forSPLIT_DEPTH
, and4*12=48
forEXECUTION_DEPTH
). The potential main benefit will be a significant gas reduction for the challenger over the whole game and a reduction in fault proof window.move()
will be minimal: the additional fee will be mainly BLOB fee for eachmove()
. This is done by reusing existing data structures, e.g., in eachmove()
, the claim hash is replaced by the hash of sub-claims - resulting in no additional storage cost.FaultDisputeGame.sol
will be minimized, and the existing definitions such asPosition
,Depth
,MIPS.sol
, etc will be retained. Further, the N-section fault-proof game would subsume bisectFaultDisputeGame.sol
when N=2. Therefore, all existing tests (unit tests, e2e tests) forFaultDisputeGame.sol
can be also used to test the new multi-section fault-proof game.Materials
Beta Was this translation helpful? Give feedback.
All reactions