Search

Search for projects by name

SummaryRisk summaryFraxtalDADA Bridge

FraxtalDA logoFraxtalDA

  • Type
    No DAC
  • TVS
    $272.88 M
  • Economic security
    —
  • Duration of storage
    Flexible
  • Used by
  • Risks

    • Select a bridge
    No Bridge
    $272.88 M
    Risk summary
    FraxtalDA risks
    FraxtalDA

    FraxtalDA is a custom data availability solution built by the Fraxtal team.

    Risk analysis
    Economic security
    None

    There are no onchain assets at risk of being slashed in case of a data withholding attack, and the committee members are not publicly known.

    Fraud detection
    None

    There is no fraud detection mechanism in place. A data withholding attack can only be detected by nodes downloading the full data from the DA layer.

    Committee security
    N/A

    There is no committee attesting to the availability of data.

    Upgradeability
    N/A

    Without the bridge, users cannot react in time to malicious actions by the sequencer.

    Relayer failure
    N/A

    The relayer does not contribute to the DA bridge liveness since data availability attestations are not integrated in the scaling solution’s proof system.

    Technology

    Architecture

    FraxtalDA is a custom data availability solution built by the Fraxtal team. The data is posted by the OP batcher to three separate locations: AWS, IPFS, and Cloudfare R2. The IPFS hash is then submitted to the onchain inbox contract on Ethereum. FraxtalDA relies on a single DA endpoint to manage data posting between the three different locations. FraxtalDA The sequencer attests to data availability by posting an IPFS hash to an onchain inbox contract on Ethereum. L2 nodes derive the L2 chain from the L1 by reading transactions commitments from this sequencer inbox. When reading from the inbox, the op-node verifies that the commitment hash is a valid IPFS CID. If the data corresponding to the hash is missing from IPFS, the op-node will halt, preventing further derivation of the L2 chain.

    • Funds can be lost if the sequencer posts an invalid data availability commitment.

    1. FraxtalDA Documentation
    2. Fraxtal DA Follower - Source Code
    No Bridge

    The SequencerInbox only stores IPFS hash commitments posted by the sequencer. It is not possible to verify blob inclusion against the data commitments onchain. Projects not integrating with a functional DA bridge rely only on the data availability attestation of the sequencer.

    Risk analysis

    There is no committee attesting to the availability of data.

    Without the bridge, users cannot react in time to malicious actions by the sequencer.

    The relayer does not contribute to the DA bridge liveness since data availability attestations are not integrated in the scaling solution’s proof system.

    Technology

    There is no committee attesting to the availability of the data. For L2 chain derivation, the system relies on sequencer commitments to an L1 onchain inbox. See DA layer technology section for more details.

    Permissions

    The system consists of the following permissions on Ethereum:

    Sequencer (relayer) 0x6017…d1f2

    Central actor allowed to relay DA commitments to the SequencerInbox.

    SystemConfig owner 0xe0d7…0508

    Account privileged to change System Config parameters such as Sequencer Address and gas limit.

    Contracts

    The system consists of the following smart contracts on Ethereum:

    SequencerInbox 0xfF00…20fC

    This address is used to store transaction batch hashes as data availability commitments.

    ProxyAdmin 0x13Fe…ABcA

    The ProxyAdmin contract is the owner of SystemConfig and can change the address of the SequencerInbox for the system.