Timeboost

• Name: Timeboost
• URL: https://docs.arbitrum.io/how-arbitrum-works/timeboost/gentle-introduction
• Category: L2 transaction-ordering policy / sequencer-side MEV-capture mechanism / express-lane auction infrastructure
• Tags: ethereum-ecosystem
• Summary: Timeboost sells bounded sequencing priority, not a whole block and not a generic MEV auction. What matters is how much ordering power the chain sells, to whom, and under which governance knobs inside an otherwise FCFS-style sequencer.
• What it does:
  • Adds an express-lane endpoint on Arbitrum-chain sequencers where the current round’s controller can submit transactions without the non-express artificial delay
  • Uses a per-round sealed-bid second-price auction to determine who controls that express lane for the next round
  • Splits the mechanism across an offchain autonomous auctioneer, an onchain auction contract, and sequencer software that enforces the timing policy
  • Requires bidders to pre-deposit an ERC-20 bidding token into the auction contract and lets chain owners choose the token, reserve parameters, beneficiary, and delay settings
  • Preserves a single ordered transaction stream and private mempool semantics rather than granting the auction winner arbitrary reorder rights or universal top-of-block control
  • Lets the express-lane controller sign privileged submissions directly and, in practice, also relay third-party transactions through that privileged lane on a per-transaction basis
• Key claims:
  • The most important primitive is not “faster tx inclusion” in isolation; it is the sale of a bounded timing advantage inside a still-FCFS-style sequencing regime. Timeboost tries to monetize latency without fully turning ordering into an open reorder market.
  • The Arbitrum docs repeatedly stress that the winner gets only a temporary head start — by default a 200ms advantage — not visibility into private pending user flow, not arbitrary transaction reordering, and not guaranteed first position in every block.
  • The research spec makes the governance surface unusually explicit. Governance or the chain owner selects the deposit token, reserve price floor, reserve-pricer role, beneficiary / burn destination, round duration, and delay parameters. Those settings determine whether Timeboost acts mainly as anti-spam infrastructure, a revenue switch, or a new dependency for professional searchers.
  • The autonomous auctioneer is a critical trust and operations surface. Although auction outcomes settle through the onchain contract, the offchain auctioneer receives bids, filters them, and submits resolution transactions, so practical neutrality still depends on software operation outside the chain itself.
  • The “express lane controller” is narrower than a block builder or proposer. The controller can sign privileged submissions, but the system still feeds both express and ordinary transactions into one ordered sequencer stream. That makes Timeboost analytically different from proposer commitment systems like Bolt or from gas-price ordering on chains with public mempools.
  • The docs and FAQ frame the hoped-for behavioral effect very clearly: searchers should spend money bidding for temporary advantage instead of wasting capital on hardware and network-path latency races. Whether that actually decentralizes opportunity or just formalizes a new auction rent is the central question worth carrying into future comparisons.
  • The ability to choose any ERC-20 bidding token and route proceeds to a beneficiary account means Timeboost is also a policy lever for chain-level value accrual, not only a market microstructure tool.
  • Timeboost belongs in the active corpus because it sharpens a recurring control-plane question in rollup design: when a chain says it is “capturing MEV while protecting users,” where does authority really sit — in sequencing software, auction operations, reserve-setting governance, endpoint access, or the exact boundaries of the privilege being sold?
• Whitepaper: No canonical standalone Timeboost whitepaper surfaced in this pass. The strongest primary materials were the Arbitrum docs pages, the timeboost-design specification repository, and the introductory Offchain Labs explainer; see ../whitepapers/timeboost-primary-sources-2026-05-10.md.
• Sources:
  • https://docs.arbitrum.io/how-arbitrum-works/timeboost/gentle-introduction
  • https://docs.arbitrum.io/how-arbitrum-works/timeboost/timeboost-faq
  • https://docs.arbitrum.io/how-arbitrum-works/timeboost/how-to-use-timeboost
  • https://github.com/OffchainLabs/timeboost-design
  • https://raw.githubusercontent.com/OffchainLabs/timeboost-design/main/README.md
  • https://raw.githubusercontent.com/OffchainLabs/timeboost-design/main/research_spec.md
  • https://raw.githubusercontent.com/OffchainLabs/timeboost-design/main/implementation_design.md
  • https://raw.githubusercontent.com/OffchainLabs/arbitrum-docs/master/docs/how-arbitrum-works/timeboost/gentle-introduction.mdx
  • https://raw.githubusercontent.com/OffchainLabs/arbitrum-docs/master/docs/how-arbitrum-works/timeboost/timeboost-faq.mdx
  • https://raw.githubusercontent.com/OffchainLabs/arbitrum-docs/master/docs/how-arbitrum-works/timeboost/how-to-use-timeboost.mdx
  • https://medium.com/offchainlabs/timeboost-for-beginners-offchain-labs-latest-transaction-ordering-policy-protocol-10310f445c81

Internal linkages

• Strongest execution-rights sale comparisons: flashbots-auction, express-relay, and jito.

• Useful cut: keep this note on sequencer-sold timing priority, not every adjacent oracle or bundle-auction branch.

• Last reviewed: 2026-06-03 UTC