docs: broken-links-and-timeboost-faq #2100
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
pete-vielhaber
commented
Feb 21, 2025
pete-vielhaber
commented
- fixing broken links that push to Notion
- Due to this needed a Timeboost FAQ
- Timeboost FAQ is a temp solution instead of using Notion, until we have a finalized solution
- fixing broken links that push to Notion - Due to this needed a Timeboost FAQ - Timeboost FAQ is a temp solution instead of using Notion, until we have a finalized solution
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
anegg0
reviewed
Feb 21, 2025
anegg0
reviewed
Feb 21, 2025
anegg0
reviewed
Feb 21, 2025
|
|
||
| The Timeboost auction is open to everyone; however, since auctions require a non-zero bid to win, we believe that only parties who can return from capturing arbitrage opportunities, backrunning opportunities, or reselling the express lane rights will benefit from participating. | ||
|
|
||
| The Timeboost protocol works behind the scenes with minimal impact on regular users while generating revenue for the Arbitrum DAO and opening up an additional revenue stream for sophisticated searchers. |
There was a problem hiding this comment.
"The Timeboost protocol works behind the scenes". I read this sentence as, "We're doing some things behind your back, but don't worry; your tokens are safe with us".
anegg0
reviewed
Feb 21, 2025
|
|
||
| ### How much estimated revenue will this drive to the DAO? | ||
|
|
||
| Estimating how much revenue Timeboost will generate is complex and is based on many factors. There are no ways to confidently estimate the amount of arbitrage or backrunning opportunities that currently exist or will exist on Arbitrum chains in the future. The expectation is that the revenue will be significant on Arbitrum One due to the high amount of DeFi activity. |
There was a problem hiding this comment.
It might be a good idea to point readers to an explorer link where they can see the token flow.
anegg0
reviewed
Feb 21, 2025
anegg0
reviewed
Feb 21, 2025
anegg0
reviewed
Feb 21, 2025
anegg0
reviewed
Feb 21, 2025
anegg0
reviewed
Feb 21, 2025
anegg0
reviewed
Feb 21, 2025
anegg0
reviewed
Feb 21, 2025
anegg0
reviewed
Feb 21, 2025
anegg0
reviewed
Feb 21, 2025
anegg0
reviewed
Feb 21, 2025
|
|
||
| On having a clearer user interface: | ||
|
|
||
| - Users can subscribe to the sequencer feed to view, in real-time, the final order of transactions. This sequencer feed is usable today and in a world where the DAO adopts Timeboost (should the vote pass). Arbitrum chains currently operate with a single sequencer with no public mempool. Today, the logic used to sort transactions is "first-come-first-serve" or FCFS. |
There was a problem hiding this comment.
"Should the vote pass". Hasn't the vote passed already?
- added quicklooks
anegg0
reviewed
Feb 21, 2025
Comment on lines
+100
to
+102
| ### Will there be a testnet for Timeboost? | ||
|
|
||
| Timeboost will be rolled out on private testing-focused devnets and public testnets like Arbitrum Sepolia before Arbitrum One and Nova. |
There was a problem hiding this comment.
Isn't Timeboost in production now?
anegg0
requested changes
Feb 21, 2025
|
|
||
| ### Will there be plans for a clean user interface that allows users to understand the logic of how their transactions are sorted, as well as an optional setting to adjust the sensitivity to the time factor? | ||
|
|
||
| The first point about a clearer user interface is that users can subscribe to the sequencer feed to view, in real time, the final order of transactions. This sequencer feed is usable both today and in a future world where the DAO adopts Timeboost (should the vote pass) to understand the logic of how transactions get sorted. |
Co-authored-by: Gaël Blanchemain <[email protected]>
Co-authored-by: Gaël Blanchemain <[email protected]>
Co-authored-by: Gaël Blanchemain <[email protected]>
Co-authored-by: Gaël Blanchemain <[email protected]>
Co-authored-by: Gaël Blanchemain <[email protected]>
Co-authored-by: Gaël Blanchemain <[email protected]>
pete-vielhaber
commented
Feb 21, 2025
Co-authored-by: Gaël Blanchemain <[email protected]>
Co-authored-by: Gaël Blanchemain <[email protected]>
pete-vielhaber
commented
Feb 21, 2025
Co-authored-by: Gaël Blanchemain <[email protected]>
Co-authored-by: Gaël Blanchemain <[email protected]>
Co-authored-by: Gaël Blanchemain <[email protected]>
Co-authored-by: Gaël Blanchemain <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.