Blockchain Integration

What we run on.

EDMA executes on its own Layer 2 for speed and cost, and anchors final lineage and governance to Ethereum (Layer 1) for permanence. EDMA L2 handles high-volume activity; Ethereum L1 provides security, auditability, and upgrade governance.

What makes it different.

At the protocol/application layer, Proof of Verification (PoV) is the gate: nothing mints, settles, unlocks access, or disburses until independent verifiers attest to the same evidence, and a global One-Claim Ledger confirms the evidence hasn’t been used elsewhere. In practice: no evidence → no token → no settlement.

Architecture at a glance

• Layer 1 — Ethereum (Security & Audit)

  • Stores immutable lineage (evidence → attestations → proof mint → settlement/retirement).

  • Hosts governance, fee schedule contracts, and long-lived registries.

  • Final anchoring point for regulators and auditors.

• Layer 2 — EDMA (Execution & Scale)

  • Runs proof mints and conversions at gas cost only (ETT, Energy NFT, Carbon Credit NFT, EMT).

  • Runs marketplace and payout flows with low latency and fees.

  • Enforces EDM-based settlement in contracts (Energy/Carbon 4% total, Commodity 0.5% per milestone with caps) with 50% of every fee burned on-chain.

• PoV (Protocol/Application Layer)

  • EAS-style attestations: MeterReadingBatch + role-tagged Verification records (e.g., AUDITOR).

  • PoVAttestorRegistry: role allowlists and quorum policy (default: ≥2 verifications, ≥1 AUDITOR, ≥2 distinct roles).

  • One-Claim Ledger: route-agnostic exclusivity by claimId so the same evidence can’t be used twice.

  • PoV Gate: single entry point every mint/settle/access call uses; reverts if quorum/equality/exclusivity fail.

Data & evidence handling

• Canonical evidence is produced off-chain (sorted/minified JSON with fixed units), hashed as evidenceHash = SHA-256(blob).

• Attestors sign EAS records over that exact hash; the Gate only counts verifications that match.

• Storage: raw artifacts stay off-chain (S3/IPFS/partner vaults) under access control; hashes anchor on-chain.

• Oracles/ingestion: Chainlink-class transports and direct operator APIs bring signed meter/logistics/MRV data into the attestation layer.

Interoperability stance

Primary home is Ethereum/EDMA. Where regulated programs require mirroring to external registries, watchers reconcile retirements/issuances without violating One-Claim. Cross-chain mirrors (with canonical “first-seen” rules) are a future extension, not a dependency.

Why this design

• Integrity first: PoV converts truth into an admissibility rule; duplicates and greenwashing are blocked in code.

• Cost where value realizes: proof mints/conversions are gas-only; users pay EDM at settlement, not at proof creation.

• Audit-ready: regulators and financiers trace claims to immutable L1 lineage.

• Operationally sane: Ethereum security, EDMA throughput, upgrade paths via timelocked governance.

Bottom line: EDMA uses Ethereum for trust, EDMA for throughput, and PoV to decide what’s allowed. Proofs are cheap to create; value only moves when reality is verified—and when it does, EDM settles the action and burns on-chain.