Skip to main content

Why choose to use AnyTrust for data availability on your Arbitrum chain

Choosing AnyTrust mode refers to selecting the AnyTrust protocol as the data availability (DA) mechanism for a chain, such as when deploying custom chains via Arbitrum Orbit. AnyTrust is an alternative to the pure Rollup mode, prioritizing cost efficiency and performance over maximum decentralization.

Opting for AnyTrust means configuring your Arbitrum-based chain to use this DA approach for reduced operational costs and better scalability, while accepting a slight trade-off in trust-minimization compared to posting all data directly to L1 (as in Rollup mode).

It's ideal for use cases where ultra-low fees are a priority over Ethereum's full security guarantees, such as consumer apps or high-frequency trading platforms. Developers can set up and configure a DAC via Arbitrum's tools, including defining the committee size and keyset threshold. This flexibility allows tailoring to specific needs within the Arbitrum ecosystem, and it's compatible with other Orbit features like custom gas tokens or third-party DA integrations.

Key Concepts​

  • Data Availability (DA) in Arbitrum: DA ensures transaction data is accessible for verification, fraud proofs, and maintaining security in optimistic rollups. Without reliable DA, users couldn't independently validate the chain's state.
  • AnyTrust Mode:
    • Transaction data is initially submitted off-chain to a permissioned group of nodes called the Data Availability Committee (DAC), typically consisting of around 20 members (though configurable).
    • The DAC stores the data and signs a Data Availability Certificate (DACert), which posts to the parent chain (Ethereum L1). Full data is not posted onchain unless requested (e.g., during a challenge).
    • Security relies on a "keyset" where at least two honest members are assumed to prevent data withholding—far milder than centralized assumptions but not fully trustless like Rollup mode.

Pros​

  • 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.
  • Higher throughput and speed: Supports a much larger volume of transactions per second compared to traditional rollups, ideal for high-frequency applications.
  • Faster withdrawals: Withdrawals to Ethereum can occur immediately if vouched for by the DAC, avoiding the typical seven-day challenge period.
  • 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.
  • Customization: Enables flexible configurations like custom gas tokens, governance, and execution logic while inheriting low-cost benefits.
  • 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.

Cons​

  • 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.
  • 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.
  • 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.
  • Liquidity and adoption changes: May face lower liquidity or ecosystem integration compared to Rollup-based chains like Arbitrum One, potentially limiting interoperability with certain apps.
  • 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.

This option reflects the growing trend toward modular blockchain architectures, where DA handling is separate to scale ecosystems like Arbitrum without compromising core security. For implementation, refer to the docs or your RaaS; a list of RaaSes is on the Third-party providers page.