• Adrian Sutton's avatar
    Introduce fast dispute game type (#10715) · 58f74b1d
    Adrian Sutton authored
    * Introduce fast dispute game type
    
    Avoids the need to change configuration to support fast withdrawals via fault proofs.
    
    * e2e: Wait for game to become resolvable.
    
    * Update kontrol snapshots.
    
    * e2e: Set correct game type for proposer.
    
    * challenger: Fast games are alphabet vm, not cannon.
    
    * Set fast game clock duration to 0.
    
    * Update snapshots again
    
    * Use game type consistently.
    58f74b1d
Name
Last commit
Last update
..
autogen Loading commit data...
checks Loading commit data...
fpac Loading commit data...
getting-started Loading commit data...
go-ffi Loading commit data...
interfaces Loading commit data...
libraries Loading commit data...
Artifacts.s.sol Loading commit data...
ChainAssertions.sol Loading commit data...
Chains.sol Loading commit data...
Config.sol Loading commit data...
Deploy.s.sol Loading commit data...
DeployConfig.s.sol Loading commit data...
DeployOwnership.s.sol Loading commit data...
DeployPeriphery.s.sol Loading commit data...
Deployer.sol Loading commit data...
Executables.sol Loading commit data...
FaultDisputeGameViz.s.sol Loading commit data...
FeeVaultWithdrawal.s.sol Loading commit data...
ForgeArtifacts.sol Loading commit data...
L2Genesis.s.sol Loading commit data...
PeripheryDeployConfig.s.sol Loading commit data...
SemverLock.s.sol Loading commit data...
Types.sol Loading commit data...
dag-viz.py Loading commit data...
deploy.sh Loading commit data...
print-addresses.sh Loading commit data...
restructure_tests.py Loading commit data...
statediff.sh Loading commit data...
visualize.sh Loading commit data...