Mantle DA
Mantle DA is a data availability solution built on EigenDA contracts, which have been forked and significantly modified.
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.
There is no delay in the upgradeability of the bridge. Users have no time to exit the system before the bridge implementation update is completed.
The relayer role is permissioned, and the DA bridge does not have a Security Council or a governance mechanism to propose new relayers. In case of relayer failure, the DA bridge will halt and be unable to recover without the intervention of a centralized entity.
Architecture
Mantle DA is an independent DA module that is built on top of an early version of EigenDA smart contracts.
The system is made up of two main component: onchain smart contracts for storing and verifying data commitments, and an offchain network of permissioned nodes storing the data.
The permissioned set of nodes is tasked with providing data availability to the Mantle network.
They receive Mantle network transaction data, sign it using a BLS signature scheme, and send back signatures to the sequencer to post commitments to the DataLayrServiceManager (DA Bridge) contract on Ethereum.
The DA DataLayrServiceManager acts as a verifier smart contract, verifying that the signatures provided by the sequencer are indeed from node operators who have agreed to be in the quorum.
To become members of the DA network, node operators are required to stake 100,000 MNT tokens, and can only be registered by an authorized entity. There is no slashing mechanism in place for misbehaving nodes.
There is a Mantle DA bridge on Ethereum storing data availability commitments.
There is no delay in the upgradeability of the bridge. Users have no time to exit the system before the bridge implementation update is completed.
The relayer role is permissioned, and the DA bridge does not have a Security Council or a governance mechanism to propose new relayers. In case of relayer failure, the DA bridge will halt and be unable to recover without the intervention of a centralized entity.
The DA bridge contract is used for storing transaction data headers and confirming the data store by verifying operators signatures.
The Mantle sequencer posts the data hash as a commitment to the DataLayrServiceManager contract on Ethereum through an InitDataStore() transaction.
Once the commitment is posted, the sequencer sends the data to the permissioned set of nodes, who sign the data and send back the signatures to the sequencer.
The sequencer then posts the signatures to the DataLayrServiceManager contract on Ethereum through a confirmDataStore() transaction.
The confirmDataStore() function verify the signatures and if the quorum is reached, the data is considered available.
The system consists of the following permissions on Ethereum:
Those are the participants of the MantleEngineeringMultisig.
List of addresses authorized to sign data commitments for the DA bridge.
List of relayers authorized to post data commitments to the DA bridge.
Address authorized to register or change status of DA node operators.
MantleThe system consists of the following smart contracts on Ethereum:
The DA bridge and the entry point for data availability commitments. It is responsible for storing transaction data headers and confirming the data store by verifying operators signatures.
This contract stores the number of Mantle DA operators and their public keys. It also store the quorum threshold and the minimum stake required to be part of the quorum.
This contract is used to manage permissions for the BLSRegistry contract.
This contract is used to manage permissions for the DataLayrServiceManager contract.
Mantle