Skip to content

docs: refresh WIP-1006 - #1010

Open
Kemperino wants to merge 3 commits into
mainfrom
kempy/refresh-wip-1006
Open

docs: refresh WIP-1006#1010
Kemperino wants to merge 3 commits into
mainfrom
kempy/refresh-wip-1006

Conversation

@Kemperino

@Kemperino Kemperino commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Note

Low Risk
Documentation-only changes to a draft WIP; no runtime or contract code is modified in this PR.

Overview
Refreshes WIP-1006 so the written spec matches the current World Chain multi-proof dispute design instead of older staking/CHALLENGE_FEE assumptions.

Challenges and bonds: Participation no longer depends on a staking registry—anyone challenges by posting CHALLENGER_BOND. CHALLENGE_FEE is removed; challenged timeouts pay the challenger CHALLENGER_REWARD_BPS (50%) of the forfeited proposer bond, with the rest to the protocol. Successful defense splits CHALLENGER_BOND between the proposer and each accepted proof-lane recipient (named per submission). Parent invalidation refunds full bonds.

Domain and proofs: BLOCK_INTERVAL (450 L2 blocks) is an activation parameter and part of domainHash; proposals must advance the parent by exactly that interval. Proof binding is lane-specific: validity and TEE lanes attest game-reconstructed transition public values (SP1 aggregation / TEE signatures); the Security Council binds rootId. Lane proofs carry a reward recipient; duplicate lane submissions revert.

Interfaces: Contract references shift from Base Azul stubs to repo types (IWorldChainProofVerifier, NitroEnclaveKeyRegistry, SecurityCouncilVerifier). Test cases and security notes are updated for bonded challenges, lane-specific binding, and revised self-challenge economics.

Reviewed by Cursor Bugbot for commit 9200468. Configure here.

@Kemperino
Kemperino enabled auto-merge (squash) August 7, 2026 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant