How the two layers cooperate
Ethereum's Proof-of-Stake gives EDMA base consensus, censorship resistance, and ultimate finality. EDMA runs as a Layer-2 on top of that, with two extra layers of logic that decide what state the chain will accept in the first place.
PoV is not a replacement for PoS. PoS settles "did this transaction happen in this order?" PoV settles a question PoS doesn't even ask: "does this transaction correspond to a real event in the physical world?" Only if PoV says yes does the transaction proceed to mint or settle.
PoV runs as a contract-enforced gate. Every claim, whether it's a meter reading, an inspection result, a customs clearance, or a delivery receipt, has to pass three checks before any asset mints or any cash releases.
The three gates
- 01
Attestation quorum
Independent verifiers on a curated, role-bound allowlist (METER_OP, AUDITOR, GRID, INSPECTOR, CUSTOMS) sign attestations over the evidence hash. The quorum spec is configurable per route but defaults to: minimum 2 total attestations, AUDITOR required, at least 2 distinct roles. No single party can self-attest into existence.
- 02
Equality check
All counted attestations must reference the same evidenceHash and the same batch. If two verifiers signed slightly different versions of the same dossier, the gate rejects them. This is where canonical-JSON serialisation pays off: identical facts produce identical bytes, which produce identical hashes.
- 03
One-claim exclusivity
The same evidence can be finalised exactly once across all routes on the network. The same kWh of solar generation cannot back two energy certificates. The same Bill of Lading cannot fund two milestone releases. The exclusivity is enforced at the contract level, not as a convention.
What lives where
On-chain (L2 → L1)
PoV hash for each gate check. EMT id and stage metadata. State deltas (Locked → Unlocked EDSD per slice). Fee and burn lines. Batches post to Ethereum as EIP-4844 blobs roughly every 2-10 minutes.
Off-chain (access-controlled)
COA PDFs, BL + seal photos, temperature logs, inspection files, EDI messages. Files are stored redundantly; the chain holds their content hashes. Signed URLs deliver access through the API.
Schemas anyone can verify
MeterReadingBatch.v1 (the meter batch), Verification.v1 (a role-tagged PASS/FAIL over the same evidenceHash), RevocationReason.v1 (structured reasons when a verification is withdrawn). Privacy by design: hashes only on-chain, raw evidence off-chain.
Why this is different from oracles
A traditional oracle relays a single price or data point from off-chain to on-chain. Anyone with the oracle's key can write whatever they want; downstream contracts have to trust the oracle.
PoV inverts that: the chain doesn't trust any single party. It enforces an evidence-first protocol where every consequential statement carries cryptographic proof of who signed it, when, and over what. The evidence itself is the source of truth; the chain just enforces the gate.
This is what makes EDMA an L2 for real-world assets rather than an L2 with an RWA oracle bolted on. The verification logic is the protocol.
