-
Notifications
You must be signed in to change notification settings - Fork 419
docs: tw-565-orbit-config-pt4 #2784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
pete-vielhaber
commented
Oct 16, 2025
- Adding Arbitrum configs for:
- BoLD
- Timeboost
- Force inclusion
- Permissioned validators
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
docs/launch-arbitrum-chain/partials/config-l1-challenge-period.mdx
Outdated
Show resolved
Hide resolved
Jason-W123
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
fix markdown table
docs/launch-arbitrum-chain/partials/config-l1-challenge-period.mdx
Outdated
Show resolved
Hide resolved
docs/launch-arbitrum-chain/partials/config-l1-challenge-period.mdx
Outdated
Show resolved
Hide resolved
docs/launch-arbitrum-chain/partials/config-l1-challenge-period.mdx
Outdated
Show resolved
Hide resolved
| @@ -0,0 +1,8 @@ | |||
| Timeboost is an optional transaction ordering policy that is configurable on any Arbitrum chain, including Arbitrum (Orbit) chains. It replaces the First-come, First-served (FCFS) ordering by introducing a sealed-bid, second-price auction for an "express lane." This express lane gives the auction winner a temporary time advantage (default: 200ms) for submitting transactions ahead of others, allowing the chain owner to capture Maximal Extractable Value (MEV) from activities like arbitrage or liquidations. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Timeboost is an optional transaction ordering policy that is configurable on any Arbitrum chain, including Arbitrum (Orbit) chains. It replaces the First-come, First-served (FCFS) ordering by introducing a sealed-bid, second-price auction for an "express lane." This express lane gives the auction winner a temporary time advantage (default: 200ms) for submitting transactions ahead of others, allowing the chain owner to capture Maximal Extractable Value (MEV) from activities like arbitrage or liquidations. | |
| Timeboost is an optional transaction ordering policy that can be configured on any Arbitrum chain, including Arbitrum (Orbit) chains. It replaces the First-come, First-served (FCFS) ordering by introducing a sealed-bid, second-price auction for an "express lane." This express lane gives the auction winner a temporary time advantage (default: 200ms) for submitting transactions ahead of others, allowing the chain owner to capture some of the Maximal Extractable Value (MEV) from activities like arbitrage or liquidations. |
|
|
||
| | Feature | Pros | Cons | | ||
| | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Revenue and MEV Capture | Captures MEV (e.g., from arbitrage or backrunning) as auction revenue for the chain owner, potentially generating significant income. Revenue can be redistributed to users, apps, or burned, creating new value accrual paths. Flexible bid tokens (e.g., any `ERC-20`) allow customization. | Revenue isn't guaranteed; it depends on MEV volume—if your Arbitrum chain has low activity, auctions may yield little or nothing. Setup/maintenance costs (e.g., auctioneer infrastructure) could exceed benefits. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | Revenue and MEV Capture | Captures MEV (e.g., from arbitrage or backrunning) as auction revenue for the chain owner, potentially generating significant income. Revenue can be redistributed to users, apps, or burned, creating new value accrual paths. Flexible bid tokens (e.g., any `ERC-20`) allow customization. | Revenue isn't guaranteed; it depends on MEV volume—if your Arbitrum chain has low activity, auctions may yield little or nothing. Setup/maintenance costs (e.g., auctioneer infrastructure) could exceed benefits. | | |
| | Revenue and MEV Capture | Captures MEV (e.g., from arbitrage or backrunning) as auction revenue for the chain owner, potentially generating significant income. Revenue can be redistributed to users and apps, or burned, creating new value-accrual paths. Flexible bid tokens (e.g., any `ERC-20`) allow customization. | Revenue isn't guaranteed; it depends on MEV volume. If your Arbitrum chain has low activity, auctions may yield little or no value. Setup/maintenance costs (e.g., auctioneer infrastructure) could exceed benefits. | |
| | Feature | Description | | ||
| | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --- | | ||
| | Dedicated throughput | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-dedicated-throughput.mdx">More info</FloatingHoverModal> | | ||
| | EVM+ compatibility | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-evm-compatibility.mdx">EVM compatability</FloatingHoverModal> + <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-other-language-support.mdx">more languages like Rust programs supported</FloatingHoverModal> | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | EVM+ compatibility | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-evm-compatibility.mdx">EVM compatability</FloatingHoverModal> + <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-other-language-support.mdx">more languages like Rust programs supported</FloatingHoverModal> | | |
| | EVM+ compatibility | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-evm-compatibility.mdx">EVM compatibility</FloatingHoverModal> + <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-other-language-support.mdx">more languages like Rust programs supported</FloatingHoverModal> | |
Co-authored-by: Gaël Blanchemain <anegg0@users.noreply.github.com>
Co-authored-by: Gaël Blanchemain <anegg0@users.noreply.github.com>
Co-authored-by: Gaël Blanchemain <anegg0@users.noreply.github.com>
….mdx Co-authored-by: Gaël Blanchemain <anegg0@users.noreply.github.com>
….mdx Co-authored-by: Gaël Blanchemain <anegg0@users.noreply.github.com>
….mdx Co-authored-by: Gaël Blanchemain <anegg0@users.noreply.github.com>