You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/launch-arbitrum-chain/01-a-gentle-introduction.mdx
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,9 +23,9 @@ If you'd prefer to learn by doing, see the [Orbit SDK Rollup creation example](h
23
23
- Arbitrum chains can be a <adata-quicklook-from='layer-2-l2'>Layer 2 (L2)</a> chain which settles directly to Ethereum, or a Layer 3 (L3) chain which can settle to any Ethereum L2, such as <adata-quicklook-from='arbitrum-one'>Arbitrum One</a>.
24
24
25
25
<ImageZoom
26
-
src="/img/orbit-settlement-layers.png"
26
+
src="/img/orbit-settlement-layers.svg"
27
27
alt="Arbitrum Orbit chain settlement layers"
28
-
className="img-600px"
28
+
className="img-800px"
29
29
/>
30
30
31
31
### What's an Arbitrum chain?
@@ -43,20 +43,20 @@ Arbitrum's protocols address this challenge by offloading some of the Ethereum n
| Gas & Tokens | <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-custom-gas-token.mdx">Custom gas token</FloatingHoverModal> or <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-native-eth.mdx">Native ETH</FloatingHoverModal> |
52
-
| Data availability | <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-rollup.mdx">Rollup (ETH DA)</FloatingHoverModal>, <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-anytrust.mdx">AnyTrust</FloatingHoverModal>, <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-alt-da.mdx">Alt-DA</FloatingHoverModal> |
53
-
| Fast confirmations | <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-fast-withdrawals.mdx">Fast withdrawals</FloatingHoverModal> |
54
-
| Security & validation | BoLD, Permissioned validators, <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-challenge-period-l1.mdx">Challenge period enforced on L1</FloatingHoverModal>|
55
-
| Safety Features | Force-inclusion & <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-customizable-governance.mdx">customizable governance</FloatingHoverModal>|
| Gas & Tokens | <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-custom-gas-token.mdx">Custom gas token</FloatingHoverModal> or <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-native-eth.mdx">Native ETH</FloatingHoverModal> |
52
+
| Data availability | <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-rollup.mdx">Rollup (ETH DA)</FloatingHoverModal>, <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-anytrust.mdx">AnyTrust</FloatingHoverModal>, <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-alt-da.mdx">Alt-DA</FloatingHoverModal> |
53
+
| Fast confirmations | <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-fast-withdrawals.mdx">Fast withdrawals</FloatingHoverModal> |
54
+
| Security & validation |<FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-bold.mdx">BoLD</FloatingHoverModal>, <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-permissioned-validators.mdx">Permissioned validators</FloatingHoverModal>, <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-l1-challenge-period.mdx">Challenge period enforced on L1</FloatingHoverModal> |
55
+
| Safety Features |<FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-force-inclusion.mdx">Force-inclusion</FloatingHoverModal> & <FloatingHoverModalhref="/launch-arbitrum-chain/partials/config-customizable-governance.mdx">customizable governance</FloatingHoverModal> |
Copy file name to clipboardExpand all lines: docs/launch-arbitrum-chain/partials/config-anytrust.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,8 @@
9
9
10
10
## Cons of using AnyTrust
11
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.
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 trust assumption 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 lack of data posting makes it less suitable for high-value DeFi or applications requiring Ethereum-level security.
14
+
-**Potential for fallback mode issues**: If the DAC cannot come to a quorum, 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 with certain <adata-quicklook-from="dapp">apps</a>.
16
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.
BoLD (Bounded Liquidity Delay) is a dispute resolution protocol that enables permissionless validation, allowing anyone to propose, challenge, and defend chain states by bonding `ETH`, with disputes resolved in a fixed-time window (typically around 7-14 days, depending on the chain). For Arbitrum chains, BoLD is available as an optional upgrade via the Nitro stack, enhancing decentralization and security while setting states to a parent chain like Ethereum or Arbitrum One.
| Validation & Decentraliation | - Enables permissionless validation, allowing anyone to propose and defend states, increasing resilience and inclusivity <br /> - Supports trustless bonding pools, letting groups pool `ETH` to participate without high individual capital barriers, promoting broader decentralization | - High bond requirements (e.g., potentially thousands of `ETH` for assertions) may centralize participation to well-funded entities, limiting smaller validators. <br /> - No built-in protocol-level incentives for validators could lead to free-riding, where parties rely on others to defend the chain. |
6
+
| Security & Dispute Resolution | - Mitigates delay attacks by enforcing a bounded dispute window (e.g., ~7 days plus grace periods), ensuring predictable resolution even against multiple malicious challengers. <br /> - Enhances withdrawal security to the parent chain by limiting indefinite delays, and includes features like Delay Buffer for censorship resistance. <br /> - A single honest party can win disputes against any number of dishonest ones, with audited code for reliability. | - Disputes can still delay all withdrawals (up to ~14 days total), impacting user experience and liquidity. <br /> - For lower-TVL Arbitrum chains, high bonds might need adjustment, trading off security against centralization risks or vulnerability to spam. <br /> - Potential censorship risks for L3 Arbitrum chains (e.g., parent chain is censored, delays could extend up to 50 days in extreme cases, though mitigated). |
7
+
| Economics & Incentives | - Bonds deter actors, with honest parties refunded plus a 1% defender's bounty and gas reimbursements, plus potential service fees (3-4% annualized `ETH` yield) from chain owners. <br /> - Fixed costs and resource ratios prevent dishonest parties from inflating expenses for honest validators. | - Significant capital lockup in bonds creates opportunity costs and risks (e.g., loss if proven wrong), potentially prohibitive for smaller chains. <br /> - KYC requirements for fee eligibility may exclude some participants, like those in sanctioned regions. <br /> - Operational costs for onchain proofs and disputes (gas, computation), add complexity and expenses. |
8
+
| Implementations & Maturity | - Modular upgrade for Arbitrum chains <br /> - Community testing via testnets and visualizers available for easier adoption | - Increased protocol complexity may require additional tooling and expertise to manage. <br /> - Reliance on parent chain for final proofs; issues there could affect Arbitrum chain disputes. |
0 commit comments