PoS base layer
What anchors EDMA
EDMA runs as an L2 anchored to Ethereum’s Proof-of-Stake (PoS). Ethereum validators provide ordering consensus and data availability for our batches (via blobs), while EDMA’s application rules (PoV, EMTs, One-Claim, must-fund) decide what is admissible and when money moves. Think of it as two complementary guarantees:
L1 (Ethereum PoS): blocks, security, and permanence.
L2 (EDMA rules): “is this allowed?” and “does cash unlock now?”
We rely on PoS for honest finality and public availability of the facts we post (PoV hashes, EMT mints, fee/burn lines, Locked→Unlocked EDSD deltas). We do not rely on it to decide business truth—that’s enforced on L2 by PoV/EMTs.
How your transaction reaches PoS finality
Operationally, your team feels L2 finality in seconds; economically, the batch anchors to Ethereum and becomes irreversible after the challenge window.
L2 block (seconds): Attestors submit evidence → PoV passes → EMT mints → the slice flips Locked→Unlocked EDSD → receipt returns. Trucks can move; tokens can settle.
L1 batch (minutes): The sequencer posts the batch and blob to Ethereum.
L1 economic finality (after the window): When the challenge window elapses, the batch is final under PoS; permissionless exits/withdrawals respect this clock.
Operate on L2; reconcile to L1. Day-to-day releases don’t wait for the L1 window, but cross-chain withdrawals do.
What PoS gives us
Consensus & finality: Honest validators make it extremely costly to rewrite history after the window.
Data availability: Batches sit in EIP-4844 blobs so anyone can reconstruct state.
Censorship resistance: If an L2 sequencer misbehaves, we can force-include transactions through the L1 inbox.
What PoS does not give
Business admissibility: That’s PoV/EMTs.
Early money movement: Our contracts enforce No EMT, no funds.
Duplicate protection at the domain level: That’s One-Claim on EDMA.
How EDMA uses the base layer
Posted to L1: PoV hash commitments, EMT ids, Locked→Unlocked EDSD deltas, fee & burn lines (with the EDM burn tx), One-Claim updates.
Kept off-chain (role-gated): COA/QA PDFs, BL + seal photos, temperature logs, customs EDI, DC QA images—served via signed URLs; the chain holds hashes.
Invariant bridge rules: Permissionless exits after the L1 window; forced inclusion via L1 inbox if needed.
Threats we assume at the base layer—and our countermeasures
Temporary reorgs / finality delays: Risk: finality stalls or small reorgs during network stress. Mitigation: treat L2 receipts as operational truth; treat L1 as economic truth. We delay permissionless exits until the window; receipts/burns are re-anchored in the next canonical batch.
Sequencer censorship: Risk: an L2 operator withholds a transaction. Mitigation: L1 forced inclusion guarantees the next batch must include the pushed tx; status pages expose inbox depth; governance can rotate the sequencer.
Data unavailability: Risk: a batch is posted without its blob or blobs can’t be retrieved. Mitigation: the rollup refuses to finalize without blobs; off-chain vaults + redundancy + hash commitments let auditors re-hydrate evidence; PoR keeps EDSD reserves reconcilable.
L1-level attack (extreme): Risk: coordinated validator attack. Mitigation: the window provides time to detect and respond; EDMA can pause new gates and keep Locked EDSD intact; permissionless exits remain possible once canonicality resumes.
Why this is safe for money
PoV Gate: checks the checklist; if it fails, the gate stays red.
EMT mints only on pass: without it, a slice can’t flip.
Locked EDSD: prevents leakage; off-platform cash-out is allowed only when the seller’s schedule completes.
One-Claim: prevents duplicate use of evidence anywhere on the rail.
50% of each protocol fee burns in EDM at release: burns are never advanced or discounted.
What operators should remember
Treat L2 receipts as operational truth; treat L1 anchors as economic truth.
If an L2 tx stalls, use forced inclusion; if you need to exit, use the permissionless bridge after the window.
Keep evidence in your vault; reconcile hashes against the Explorer and the blob index when you audit.
Plain recap
Last updated