Timeboost primary sources
Collected: 2026-05-10 UTC
Primary sources reviewed
- https://docs.arbitrum.io/how-arbitrum-works/timeboost/gentle-introduction
- Official Arbitrum overview of the mechanism.
- Used to confirm the modified-FCFS framing, private-mempool / anti-sandwich positioning, 200ms non-express delay, 60-second round structure, and the express-lane / auction / auction-contract decomposition.
- https://docs.arbitrum.io/how-arbitrum-works/timeboost/timeboost-faq
- Official FAQ.
- Used to confirm optional deployment by chain owners, claimed anti-front-running boundary, monetization goals, fallback to FCFS, and the stated behavioral expectation that searchers may buy auction access instead of engaging in latency-race spam.
- https://docs.arbitrum.io/how-arbitrum-works/timeboost/how-to-use-timeboost
- Official operator / user guide.
- Used to confirm auction contract addresses and endpoints, bidder pre-deposit flow, signature requirements, error conditions, and the practical reality that an express-lane controller can submit third-party transactions through the privileged lane.
- https://github.com/OffchainLabs/timeboost-design
- Canonical specification repository.
- Used to confirm that Timeboost is implemented as part of the Nitro stack and to locate the research and implementation specs.
- https://raw.githubusercontent.com/OffchainLabs/timeboost-design/main/research_spec.md
- Core research specification.
- Used to confirm the sealed-bid second-price auction, reserve-pricer role, governance-selected bidding token and beneficiary, round timings, transfer mechanics, and RPC message structure.
- https://raw.githubusercontent.com/OffchainLabs/timeboost-design/main/implementation_design.md
- Offchain and sequencer API details.
- Used to confirm the split between auctioneer and sequencer RPC namespaces, validation logic, and the express-lane controller signature path.
- https://medium.com/offchainlabs/timeboost-for-beginners-offchain-labs-latest-transaction-ordering-policy-protocol-10310f445c81
- Offchain Labs explainer.
- Used to confirm the project’s intended positioning versus FCFS and priority-gas-auction style ordering, plus the early rollout framing around Arbitrum DAO adoption.
Notes
- Timeboost’s core mechanism is a sold timing edge inside a constrained FCFS regime, not unrestricted reorder rights.
- The main control surfaces are chain-owner parameter choice, auctioneer operation, express-lane endpoint access, and how proceeds are routed or burned.
- This entry is useful because it makes the distinction between “capture MEV,” “reduce spam,” and “preserve user protections” unusually explicit in one mechanism.