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​

With up to 90% lower fees, higher throughput, and faster finality, it is suitable for high-volume, low-value applications like gaming or social dApps.

Cons​

Introduces a trust assumption in the DAC, which could be a vector for censorship or failure if too many members collude (though mitigated by requiring only a small honest minority).

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.