Meeda
Funds can be lost if
Meeda (MemoDA) is a blockchain-based cloud storage protocol developed by MEMO Labs.
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 committee attesting to the availability of data.
The relayer does not contribute to the DA bridge liveness since data availability attestations are not integrated in the scaling solution’s proof system.
Architecture
Meeda’s architecture consists of several components.
Storage Nodes store blob data and generate data availability commitments, with node deployment available to all users.
Light Nodes are responsible for challenging storage nodes through onchain verification, and their deployment is also open to all users.
The Operator, currently deployed by the project itself, handles the erasure coding of data and data chunks distribution, as well as the aggregation of KZG commitment proofs from Storage Nodes.
Storage Nodes, based on seed information generated periodically on the Memo chain, submit KZG data commitments to the Operator.
The Verification Contract is responsible for onchain verification on Memo chain, and it will generate seed information through the VRF-Sampling (Verifiable Random Function) cycle to determine which files to select for verification.
Not all data commitments are verified onchain, but only a subset of data is verified, with the sampling determined by the random seed produced by the Verification Contract.
The operator will then collect and aggregate the KZG commitments for the selected files from storage nodes, and submit the aggregate proof to the Verification Contract.
Optimistic verification assumes that the aggregation commitment submitted by the operator node is correct and only requires checking the accuracy of the associated proof.
If no light node challenges the commitment within the specified validity period, the proof of availability is considered successful.
Submitting a fraud proof is expected to require multiple rounds of interaction, with pledges and rewards for both the challenger and the challenged.
The proving smart contracts (FileProof, ControlFileProof, ProxyFileProof) are deployed to the Memo chain and their code is not public, so the logic and security of the proving contracts is not verifiable.
L2s Data Availability
L2s can upload transaction data to Meeda through the MemoDA RPC, and the Meeda operator will generate an aggregated KZG polynomial commitment based on the transaction data. Nodes can request transaction data on Meeda based on the commitment value of the transaction data.
Funds can be lost if Memo storage nodes do not make the data available.
This project does not have a DA bridge on Ethereum.
There is no committee attesting to the availability of data.
The relayer does not contribute to the DA bridge liveness since data availability attestations are not integrated in the scaling solution’s proof system.
There is no DA bridge on Ethereum.