Anchoring inherits Ethereum’s security
EDMA L2 is a rollup. Transactions execute on the L2; periodically, the L2 commits a compressed representation of its state to Ethereum mainnet. After the L1 commitment is finalised, the L2 state up to that point is also final: reversing it would require reversing Ethereum, which is the same security assumption every Ethereum-based asset operates under.
Settlement finality follows L1 finality. When a milestone PASS mints an EMT and unlocks a tranche of EDSD on L2, the transaction is provisionally final immediately on L2 (sequencer-acknowledged). It becomes cryptographically final after the next L1 anchor confirmation, typically 2 to 10 minutes later. For settlement purposes, both timescales are acceptable: tranches release immediately to the seller’s wallet; auditors and disputes operate on the L1-anchored state.
The L2 runs its own consensus (PoV plus sequencer), but the long-term security guarantee comes from Ethereum. EDMA inherits Ethereum’s social consensus, its decentralised validator set, its cost of attack. The protocol does not need to bootstrap a new security model; it borrows the most-secured public chain that exists.
EIP-4844 blob mechanics
EIP-4844 introduced blob transactions on Ethereum mainnet in March 2024. Blobs are a separate data lane optimised for rollup commitments: cheaper than calldata, retained for approximately 18 days, and verifiable via cryptographic commitments without keeping the full data on consensus-layer nodes forever.
EDMA L2 commits its state via blob transactions every 2 to 10 minutes depending on activity. Active periods (many milestone PASSes, many EMTs) batch into more frequent blobs; quiet periods stretch to the 10-minute target. The protocol pays L1 blob fees in ETH; this is the largest single L1 cost the rail incurs.
After the 18-day blob retention period, the L1 retains only the cryptographic commitment, not the full blob payload. For long-term retention (audit trail, dispute history, regulatory inquiry), the EDMA Data Availability committee maintains the full blob data with cryptographic proofs of correspondence to the L1-committed hashes. This is the standard rollup DA model with explicit long-tail retention guarantees.
Data availability model
EDMA uses a two-tier data availability model. The primary tier is Ethereum L1 blob storage for the 18-day retention window. During this window, anyone with an Ethereum node can independently verify the L2 state without trusting any EDMA-specific infrastructure. This is the strongest DA guarantee available short of full Ethereum calldata, at roughly 100x lower cost.
The long-tail tier is the EDMA DA committee, a federated set of nodes (currently bootstrapped by Anthropic-style audit partners; transitioning to fully decentralised by Stage 5 of the roadmap) that retain full blob payloads beyond the L1 retention period. Cryptographic proofs match the long-tail data to the L1-committed hashes, so the committee cannot serve falsified data without being detected. The committee model trades off pure decentralisation for affordability of multi-year retention.
The Data Availability page covers the full architecture. The Security Model page covers the trust assumptions and the attack surface.
