Skip to content

Commit dfb57b4

Browse files
Merge pull request #2723 from OffchainLabs/orbit-config-pt3
docs: arbchain-config-pt3
2 parents d047ba4 + c2d796c commit dfb57b4

File tree

5 files changed

+60
-14
lines changed

5 files changed

+60
-14
lines changed

docs/launch-arbitrum-chain/01-a-gentle-introduction.mdx

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -43,20 +43,20 @@ Arbitrum's protocols address this challenge by offloading some of the Ethereum n
4343

4444
### What key features should I consider?
4545

46-
| Feature | Description |
47-
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
48-
| Dedicated throughput | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-dedicated-throughput.mdx">More info</FloatingHoverModal> |
49-
| EVM+ compatibility | EVM compatability + more languages like Rust programs supported |
50-
| Account abstraction | Account abstraction |
51-
| Gas & Tokens | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-custom-gas-token.mdx">Custom gas token</FloatingHoverModal> or <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-native-eth.mdx">Native ETH</FloatingHoverModal> |
52-
| Data availability | Rollup (ETH DA), AnyTrust, <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-alt-da.mdx">Alt-DA</FloatingHoverModal> |
53-
| Fast confirmations | Fast withdrawals |
54-
| Security & validation | BoLD, Permissioned validators, Challenge period enforced on L1 |
55-
| Safety Features | Force-inclusion & customizable governance |
56-
| MEV | Timeboost |
57-
| Cost | Data posting costs |
58-
| Infrastructure | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-hardware.mdx">Hardware requirements</FloatingHoverModal> |
59-
| Interop | TBD |
46+
| Feature | Description |
47+
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
48+
| Dedicated throughput | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-dedicated-throughput.mdx">More info</FloatingHoverModal> |
49+
| EVM+ compatibility | EVM compatability + more languages like Rust programs supported |
50+
| Account abstraction | Account abstraction |
51+
| Gas & Tokens | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-custom-gas-token.mdx">Custom gas token</FloatingHoverModal> or <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-native-eth.mdx">Native ETH</FloatingHoverModal> |
52+
| Data availability | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-rollup.mdx">Rollup (ETH DA)</FloatingHoverModal>, <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-anytrust.mdx">AnyTrust</FloatingHoverModal>, <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-alt-da.mdx">Alt-DA</FloatingHoverModal> |
53+
| Fast confirmations | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-fast-withdrawals.mdx">Fast withdrawals</FloatingHoverModal> |
54+
| Security & validation | BoLD, Permissioned validators, Challenge period enforced on L1 |
55+
| Safety Features | Force-inclusion & customizable governance |
56+
| MEV | Timeboost |
57+
| Cost | Data posting costs |
58+
| Infrastructure | <FloatingHoverModal href="/launch-arbitrum-chain/partials/config-hardware.mdx">Hardware requirements</FloatingHoverModal> |
59+
| Interop | TBD |
6060

6161
### How do Arbitrum chains help the Ethereum ecosystem?
6262

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
## Pros of using AnyTrust
2+
3+
- **Ultra-low transaction fees**: By offloading data availability to a Data Availability Committee (DAC) instead of posting all transaction data directly to Ethereum L1, AnyTrust significantly reduces costs, making micro-transactions viable.
4+
- **Higher throughput and speed**: Supports a much larger volume of transactions per second compared to traditional rollups, ideal for high-frequency applications.
5+
- **Faster withdrawals**: Withdrawals to Ethereum can occur immediately if vouched for by the DAC, avoiding the typical seven-day challenge period.
6+
- **Minimal trust assumptions with strong feedback**: Requires only a small number of honest DAC members for normal operation, which is less trust-intensive. If the DAC fails, it automatically falls back to rollup mode, posting data to Ethereum for security.
7+
- **Customization**: Enables flexible configurations like custom gas tokens, governance, and execution logic while inheriting low-cost benefits.
8+
- **Ideal for specific use cases**: Best for high-volume, low-value applications such as Web3 gaming, decentralized social media, NFT platforms, and micro-payment systems where cost efficiency outweighs maximum decentralization.
9+
10+
## Cons of using AnyTrust
11+
12+
- **Introduced trust assumptions**: Relies on the DAC's honesty and availability, which adds a layer of trust not present in full trustless rollups. This could be a risk if committee members collude or fail.
13+
- **Reduced decentralization and security guarantees**: Lacks the full trustlessness, permissionlessness, and censorship resistance of Rollups, as not all data is posted to Ethereum by default. This makes it less suitable for high-value DeFi or applications requiring Ethereum-level security.
14+
- **Potential for fallback mode issues**: If the DAC quorum isn't met, the chain reverts to Rollup mode, which could increase costs temporarily and introduce delays similar to standard Rollups.
15+
- **Liquidity and adoption changes**: May face lower liquidity or ecosystem integration compared to rollup-based chains like Arbitrum One, potentially limiting interoperability for certain dApps.
16+
- **Not optimal for all use cases**: For applications handling significant financial value or needing maximum security, the trade-offs in decentralization could outweigh the benefits.
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
## Pros
2+
3+
- **Significantly faster withdrawals and finality**: Reduces withdrawal times from days to minutes, improving user experience and enabling quicker asset movement across chains. This is particularly beneficial for cross-chain dApps, as they can read the finalized state at the same accelerated rate.
4+
- **Enhanced capital efficiency**: Shorter wait times minimize opportunity costs for users, allowing faster re-deployment of funds and better liquidity in DeFi or other applications.
5+
- **Improved performance for AnyTrust**: When combined with AnyTrust mode, Fast Withdrawals leverage existing infrastructure without introducing entirely new trust elements, enabling near-instant withdrawals for non-fungible assets.
6+
- **Flexibility for Layer 3 setups**: For chains settling to Arbitrum One or similar, finality can be configured down to 15 seconds, supporting high-throughput applications.
7+
8+
## Cons
9+
10+
- **Introduced trust assumptions**: Shifts security from the fully decentralized optimistic Rollup model to reliance on a validator committee. For Rollup-mode chains, this means it's no longer a "true" Rollup, as users must trust the committee for fast confirmations. In AnyTrust mode, it assumes at least two honest members in the Data Availability Committee (DAC), which could be a risk if the committee is compromised.
11+
- **Potential delays under high load**: High network throughput can cause confirmation delays beyond the configured rate, with a practical minimum of 1-2 minutes in busy scenarios. Initial setup may also slow the chain temporarily due to backlog processing.
12+
- **Setup complexity and requirements**: Requires upgrading to specific versions, creating a multi-signature Safe wallet for the committee, and running at least three validators. This adds operational overhead and potential costs.
13+
- **Security trade-offs compared to standard withdrawals**: While standard withdrawals maintain full Ethereum-level security via the challenge period, fast withdrawals prioritize speed over decentralization, potentially exposing users to risks if the committee fails or is attacked.
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
## Pros of using Rollup mode
2+
3+
- **Security**: Provides maximum security and decentralization by inheriting full Ethereum-grade security without additional trust assumptions beyond the base layer.
4+
- **Strong Data Availability**: Ensures strong data availability and censorship resistance, as all transaction data is publicly posted on the parent chain, allowing anyone to validate and detect fraud.
5+
- **Trustless and permissionless**: Fully trustless and permissionless operation, requiring only one honest validator for the system to remain secure, making it ideal for high-value applications like DeFi protocols.
6+
7+
## Cons of using Rollup mode
8+
9+
- **Higher costs**: Higher transaction fees due to the cost of posting all data on-chain to the parent layer.
10+
- **Withdrawal times**: Longer withdrawal times, typically involving a seven-day challenge period for fraud proofs before funds can be moved back to the parent layer.
11+
- **Throughput**: Potentially lower throughput compared to AnyTrust mode, as the on-chain data posting can limit scalability for high-volume, low-value transactions.

src/components/FloatingHoverModal/index.js

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,9 @@ import ConfigAltDa from '@site/docs/launch-arbitrum-chain/partials/config-alt-da
2323
import ConfigDedicatedThroughput from '@site/docs/launch-arbitrum-chain/partials/config-dedicated-throughput.mdx';
2424
import ConfigNativeEth from '@site/docs/launch-arbitrum-chain/partials/config-native-eth.mdx';
2525
import ConfigHardware from '@site/docs/launch-arbitrum-chain/partials/config-hardware.mdx';
26+
import ConfigRollup from '@site/docs/launch-arbitrum-chain/partials/config-rollup.mdx';
27+
import ConfigAnytrust from '@site/docs/launch-arbitrum-chain/partials/config-anytrust.mdx';
28+
import ConfigFastwithdrawals from '@site/docs/launch-arbitrum-chain/partials/config-fast-withdrawals.mdx';
2629

2730
// Static content mapping
2831
const contentMap = {
@@ -31,6 +34,9 @@ const contentMap = {
3134
'config-dedicated-throughput': ConfigDedicatedThroughput,
3235
'config-native-eth': ConfigNativeEth,
3336
'config-hardware': ConfigHardware,
37+
'config-rollup': ConfigRollup,
38+
'config-anytrust': ConfigAnytrust,
39+
'config-fast-withdrawals': ConfigFastwithdrawals,
3440
};
3541

3642
// MDX components for proper rendering

0 commit comments

Comments
 (0)