As stated in the AIP, the goal of Timeboost is to give chain owners a way to capture available MEV on their chain and reduce spam from FCFS arbitrage all while preserving best-in-class user experience with both fast block times and protection for users from harmful MEV (e.g. frontrunning/sandwich attacks). That being said, any MEV strategy comes with trade-offs though and it is important that the DAO works collaboratively together with the ecosystem to monitor and fine-tune Timeboost over time to strike the right balance of trade-offs.
Any proposed change, technical or otherwise, to Arbitrum One and Nova should prioritize ensuring the best user experience and optimal functioning of the chain ahead of other priorities. Timeboost explicitly embodies this principle in 3 ways through deliberate design decisions outlined below:
- Arbitrum One and Nova block times will continue to be industry leading at 250ms even after Timeboost What will change with Timeboost is that some transactions, specifically those not in the express lane, will be delayed to the next block. If there is an Express Lane controller for a given round, users will wait, at most, 450ms for their transactions to be sequenced (200ms proposed delay, plus 250ms block time). Furthermore, the time for a user’s transaction to be sequenced will fall back to 250ms(up to 100ms for Orbit chains who choose to lower blocktimes) if there is no express lane controller. All of these values for Arbitrum One and Nova, both the block time and the nominal delay for non-express lane transactions, are controlled by governance and are far shorter than the blocktimes seen on other L2 and even rival alternative L1s (like Solana’s 400ms block times).
- Timeboost is purely supplemental and optional to Arbitrum chains. The chain will fall back to the current FCFS ordering policy if (1) Timeboost is turned “off” (controlled by governance) or (2) if there is no express lane controller for the given round. Timeboost may be turned off in the event that its effects are harming UX for users of the chain.
- With Timeboost, the mempool for transactions will continue to be private, which means users will continue to be protected from harmful MEV like front-running and sandwich attacks. This ensures a great user experience.
Timeboost’s design is the culmination of over a year of research and development by the team at @offchainlabs , as well as discussions with teams that would be affected by Timeboost. While the on-chain implementation will be independently audited by Trail of Bits before the Tally vote, the long term performance of Timeboost can only truly be evaluated with real-world data - data that can help hone and fine-tune Timeboost’s design for the benefit of the ArbitrumDAO and all Arbitrum builders and users.
The proposed values in this Timeboost proposal were chosen as starting parameters that we believe would strike a fair balance/approach for both arbitrageurs and regular users of Arbitrum chains. All of these parameters, including the ability to disable Timeboost, are controlled by Governance, and can be adjusted (within limits) if experience with Timeboost suggests that is beneficial.
- The 60 second period length was chosen to balance the desire to make prediction of MEV value by bidders easier (suggesting a shorter period) against the fact that there are costs and “friction” at the boundary between periods (suggesting a longer period).
- Closing the auction 15 seconds before the period starts was chosen to balance the desire to minimize how far in the future bidders need to predict (suggesting a shorter interval) against the desire to leave time for the auction winner to restructure and/or resell their rights (suggesting a longer interval).
- The 200 millisecond time advantage for the auction winner was chosen to balance the desire to minimize the delay for user transactions (suggesting a shorter interval) against the desire to give the auction winner enough time to run a service that aggregates submissions from multiple searchers and forwards them with some time advantage.
Other sectors of the chain will be impacted by the introduction of the proposed 200ms delay for non-express lane transactions. It remains to be seen what exactly that impact will entail as these sorts of behaviors are incredibly hard to predict ahead of time.
One fact that deserves emphasizing here is that even with Timeboost, Arbitrum One and Nova block times will continue to be industry leading at 250ms. What will change is that some transactions not in the express lane will be delayed to the next block. Preserving the property of fast block times contributes to the great user experience that Arbitrum chains have and continue to be known for. We believe that the property of fast block times, alongside protection against harmful MEV, will continue to attract and retain both users and the pioneering builders behind next-gen applications, including gaming and prediction markets - especially now with Stylus live on mainnet.
The decisions around what strategies to use and how to use them to generate revenue from available MEV on Arbitrum One and Nova are entirely in the hands of the DAO. Whether or not this revenue comes at the expense of DEX volume, and to what extent, remains to be seen. Without real-world data, it is difficult to accurately predict exactly what will happen.
Collection and monitoring of key metrics will be crucial to evaluating Timeboost’s performance and downstream impacts, over time. The insights gained from such analyses can also be used to inform how the DAO fine-tunes the various parameters of Timeboost, including the nominal delay for non-express lane transactions (200ms) and the auction duration (1 minute). To support this effort, the AIP states that the following data sources will be saved and made available after Timeboost goes live on Arbitrum One and Arbitrum Nova, if this proposal passes:
- Historical bid data for auction participants, outside of the two highest bids (that are otherwise posted on-chain)
- A way to label/identify which transactions were sequenced in the express lane (i.e. Timeboosted transactions)
Also mentioned in the AIP is the fact that the long term performance of Timeboost can only truly be evaluated with real-world data - data that can help hone and fine-tune Timeboost’s design for the benefit of the DAO.