Illustrative protocol model

Energy flow

Explore an illustrative path from energy data and verification to coordination and XRPL settlement. Values shown are synthetic, not live network measurements.

CaptureVerifyAnchorSettle

Visual Sequence

From physical energy to settlement records.

01

Capture

A proposed integration captures signed energy measurements.

02

Attest

Evidence carries source references and sequence checks.

03

Certify

Application verifiers assess evidence under a shared policy.

04

Anchor

An authorized reference is submitted through a supported XRPL transaction.

05

Settle

A validated transaction result is reconciled with the participant obligation.

Grid Architecture

Signal integrity across every layer.

This illustration connects source evidence, application verification, and settlement records. It does not demonstrate a live deployment.

  • Source records support energy provenance
  • Verifier checks assess repeated or conflicting evidence
  • XRPL finality confirms a validated transaction result

Scene 01 / StorageProof Stream

Physical energy enters the proof layer.

Example source records combine meter references, sequence identifiers, and operating context for application-level assessment.

epoch_id E-48291
window 00:05:00
kWh_avail 18.742
SoC 82.6%
storage_id STG-EU-0429-7A meter_root sha256:7d4c:91af:e032:aa0b SP.digest 0x8f41c7b0e7129f3c nonce_chain n-48290 -> n-48291 slope_guard PASS / bounded discharge

Scene 02 / Verifier Mesh

Illustrative verifier agreement before ledger submission.

N 11 Verifiers f 3 tolerated faults quorum 8 signatures votes 9 / 11 bitmap 11110110111 p95 latency 242ms

Scene 03 / Application State

Checks before ledger submission.

The proposed application checks duplicate records, sequence changes, and policy consistency. These are not native XRPL energy-verification rules.

validate(QC)PASS
seen[ES]false -> true
last_epoch[storage_id]48290 -> 48291
policy_hashPINNED
RecordLockWRITE
Sample close 4.1s

Scene 05 / Enerdex Proof Trace

One EnergySlice, one complete audit path.

Follow an illustrative energy record through source evidence, verifier agreement, duplicate checks, coordination, and XRPL result reconciliation.

storage_id STG-EU-0429-7A energy_slice_id ES-48291-18.742 qc_hash 0x9fa1e2c7b441 anchor_commit AC-91844241
01

StorageProof

Example source evidence and measurement references.

02

EnergySlice

A record links a measurement batch, status, and sequence.

03

QuorumCert

Example agreement under a stated membership policy.

04

AnchorCommit

An evidence reference links to a ledger transaction result.

05

RecordLock

Application checks flag a duplicate record before submission.

06

XRPL settlement

A validated result is linked to the participant obligation.

EnergySlice.schema ES-48291-18.742
source_storage_id STG-EU-0429-7A epoch_start sample-window-start epoch_end sample-window-end kWh_available 18.742 SoC_start 84.1% SoC_end 82.6% meter_root 0x7d4c91afe032 nonce_prev n-48290 nonce_next n-48291 qc_required 8 / 11 record_status locked policy_hash pinned

Scene 06 / EnergySlice Schema

An evidence object for coordination.

The proposed EnergySlice record links measurement references with verification status. It supports traceability without proving physical delivery.

n-48288 n-48289 n-48290 n-48291

Scene 07 / RecordLock Matrix

Application checks protect record integrity.

This illustrative matrix shows proposed checks for duplicate records, sequence continuity, and policy consistency. Production enforcement requires implementation and validation.

qc.signatures >= N - fPASS
nonce_next == last_nonce + 1PASS
duplicate EnergySlice IDREJECT
policy_hash driftREJECT
RecordLock already existsREJECT
write AnchorCommit + RecordLockSEALED
OPEN RESERVED RECORDED SETTLED CLOSED
Grid Signal Surface illustrative data
p50 96ms p95 242ms QC build 0.8s sample close 4.1s

Scene 08 / Grid Signal Surface

An illustrative view of energy coordination.

Synthetic signals show how evidence, participant activity, and ledger results fit the proposed Enerdex framework. They are not operational metrics or performance commitments.