Arbitrum BoLD brings permissionless validation and fixed dispute windows

The BoLD protocol replaces the previous dispute protocol that relied on an allowlist of validators. This new system allows any party to participate in validating the Arbitrum chain state or opening challenges. Bounded Liquidity Delay, or BoLD, ensures that disputes resolve within a fixed period. A single honest validator protects the network against any number of adversaries. I see this move as a way for Arbitrum to address the State Validation wedge in the L2BEAT risk analysis pie chart. This transition moves the network toward Stage 2 recognition. Arbitrum processed 478 million transactions in the first half of 2026, bringing its lifetime total to 2.7 billion. The ecosystem generated $206 million in GDP during that same period. This growth occurs alongside a total supply of 10 billion ARB, of which 92.3% remains in the treasury or unlocked.

Validators begin by taking the most recent confirmed assertion, Block A, and asserting an end state, Block Z. If a validator disagrees with the end state represented by Block Z, they submit a challenge by bonding capital to a different end state, Block Y. This creates two asserted states. The parties engage in a bisection game to find the exact block where they disagree. First, the parties identify the specific block in a level-zero challenge. Second, they move to the big-step challenge to narrow the disagreement to a range of 2^23 WASM instructions. Finally, they conduct a one-step challenge to reach a single instruction. The smart contract on the parent chain executes this one step to validate the correctness of the submitted proof from both parties. A timer increments at each stage, and an edge automatically confirms if the timer reaches the period, T. This mechanism prevents malicious actors from extending the challenge period. The parties use Merkle trees of asserted states to manage these historical commitments. In a level-zero challenge, the disputing parties take turns bisecting their historical commitments until they identify the specific block on which they disagree.

The economic security of the protocol depends on heavy bonds to prevent spam and delay attacks. Proposers must bond 3600 ETH to post an assertion. To open challenges, validators must provide specific challenge bonds at different levels of the bisection.

The protocol sets these values to account for the opportunity cost of delayed withdrawals. The Arbitrum One bridge contains approximately $3.4B in assets. If these funds earned a 5% APY elsewhere, a one-week delay in withdrawals costs about $3.27M. The bonds ensure that any attempt to delay withdrawals through a dispute costs the attacker more than the potential gain. You should know that these bonds can accumulate via a trustless bonding pool. If a validator proposes an invalid assertion, they lose their entire bond.

Optimism Cannon uses a single-round mechanism. A challenger identifies a single, incorrect step in a state transition and proves that invalidity in one onchain transaction. This requires the entire disputed instruction to be executed and verified on Ethereum. This process can be gas-intensive for complex operations. BoLD uses a multi-round bisection game where the challenger and defender narrow the dispute to a single WASM instruction step. This results in a much smaller onchain verification cost. Cannon relies on a MIPS instruction-level trace, while BoLD uses a WASM instruction-level trace. Cannon currently uses permissioned challengers, but BoLD allows any party to act as a challenger if they meet the bond requirements. The current challenge period for Arbitrum One and Nova is defined by 45,818 blocks, which at a fixed block time of 12 seconds results in a duration of exactly 6 days and 8 hours. This period is lower than the 7-day requirement for Stage 2 designation. What happens if Ethereum changes its block times again?