ETT - Energy Tracking Token: The 10 kWh Atomic Proof Receipt

What ETT is

ETT (Energy Tracking Token) is the EDMA protocol's atomic proof receipt for renewable energy production. Each ETT represents exactly 10 kWh of metered, attested clean-energy generation. It mints automatically as production data lands and is permanently non-transferable: the token serves as audit-grade evidence, not as a tradeable instrument.

ETT sits at the atomic layer of the protocol's energy-attestation chain. The aggregation of 100 ETT produces an Energy NFT (1 MWh tradeable unit), which is the path to external registry instruments (REC, SREC, I-REC, GO) via the CONVERT_CERT milestone. ETT also feeds the carbon routes directly (R4 additionality tonnes, R9 avoided diesel) where the verifier dossier bundles ETT into a vintage carbon batch. CLE (Clean Energy Coin) is a separate consumer currency token minted in parallel from the same 1 MWh production trigger but routed to a completely different purpose: exchange trading, solar-equipment discounts, and peer-to-peer prosumer commerce. CLE is not derived from ETT and not an aggregation of ETT.

ETT is not a credit, a carbon offset, an emissions attribute, or a tradeable token. It is a proof. The credit, attribute, or offset is what gets minted downstream from ETT (a REC for compliance markets, a GO for European clean-power claims, a carbon tonne for the voluntary carbon market). ETT is the receipt that the 10 kWh actually happened and was metered by a trusted source.

Why non-transferable

The non-transferability of ETT is the discipline that makes the protocol's audit story hold. The reasoning: a tradeable proof receipt could be shopped across multiple buyers before consumption. Producer A could sell the ETT to buyer X for REC issuance, then sell the same ETT to buyer Y for a carbon claim. Both buyers receive a receipt; both are told they own the underlying kWh; neither realises until audit that the same kWh was claimed twice.

The non-transferable design closes this attack vector at the contract level. ETT can only be deposited to a pool (where it queues for aggregation or conversion) by the original producer. The pool contract is the only entity that can consume the ETT. The One-Claim Ledger reserves the (asset_id, hour, grid_zone) key at deposit and finalises it at consumption, so no future claim against the same kWh can succeed.

By the time a buyer sees the upstream lineage on a retirement record, every ETT in the chain is either still owned by the original producer (waiting for the next aggregation or conversion window) or stamped consumed for a specific downstream unit. The trail is unambiguous and cannot be rewritten.

ETT LIFECYCLE · METER TO CONSUMED, NON-TRANSFERABLE THROUGHOUTFive stages from the 10 kWh meter window to the permanent consumed stamp. ETT is the protocol's atomic proof receipt; it is never tradeable. The aggregation result is the Energy NFT (1 MWh of certificate-conversion-ready unit), not CLE. CLE is a separate consumer currency, minted in parallel from the same production trigger but routed to a completely different economic purpose.

S01METER

Meter records production10 kWh increments

EvidenceRevenue-grade meter, utility credentials, or inverter telemetry; the asset is registered to the Attestor Registry; each evidence packet covers a contiguous 10 kWh window with start_timestamp, end_timestamp, asset_id, location, fuel_class

ActorMETER_OP role held by the asset owner, the utility, or the IoT aggregator; an additional attestor (installer, O&M provider, IoT integrator) co-signs

OutputValidated METER_WINDOW PoV hash ready for the ETT_MINT milestone

S02MINT

ETT mint per 10 kWh1 ETT = 10 kWh, non-transferable

EvidenceReference to the METER_WINDOW PoV hash; kWh rounding and lotting logic; One-Claim check (no overlapping windows; attestor concurrence present)

ActorETT_MINT contract; PoV Gate evaluates and reverts if any check fails

OutputETT minted to the producer's wallet as a non-transferable proof-only record; each ETT carries the asset_id, hour, grid_zone, fuel_class metadata on-chain

S03DEPOSIT

ETT deposited to a poolmanual or Auto-Deposit

EvidenceProducer chooses (or pre-configures via Auto-Deposit) which regional pool to deposit ETT into: a compliance pool for Route 1 (REC/SREC/SMART/STC), a granular-attributes pool for Route 2 (I-REC/GO/hourly), a Carbon Path queue for Route 4 (energy-side carbon), or held back from any pool for Route 9 (avoided-diesel) where ETT goes directly into the carbon batch

ActorProducer signs the deposit; the pool contract receives the ETT and queues it for the next aggregation or issuance window

OutputETT held in the chosen pool, queued for the next step

S04USE

Aggregate or converttwo paths to certificate or carbon

EvidenceAggregate path (R1, R2): 100 ETT (1,000 kWh = 1 MWh) roll up into 1 Energy NFT, the 1 MWh tradeable certificate-conversion unit; the Energy NFT is then converted to the registry-native instrument (REC, SREC, I-REC, GO, or hourly certificate) via the CONVERT_CERT milestone with the Registry Mirror binding external serial(s).
Direct carbon path (R4, R9): ETT bundles directly into a vintage carbon batch with the EF snapshot, REC retirement IDs (where applicable), storage dispatch proofs, and buffers; the verifier signs; the CARBON_TONNE contract mints

ActorEnergy NFT contract or CARBON_TONNE contract; Registry Mirror binds external serials where applicable; One-Claim Ledger reserves the relevant key

OutputEnergy NFT issued OR carbon tonne minted; the source ETT are stamped consumed pending the final stage

S05 · FINALCONSUMED

ETT permanently consumedstamped non-transferable

EvidenceExternal registry Issue and Retire IDs (where applicable) anchored on Ethereum L1; the consumed-to-{instrument} stamp on each ETT records exactly which downstream unit it backed (Energy NFT, REC, GO, carbon tonne)

ActorETT_MINT contract marks the units consumed; the One-Claim Ledger finalises the key, blocking any future claim on the same kWh

OutputETT visible in the producer's wallet for audit purposes but permanently non-transferable; the producer's downstream unit (Energy NFT, REC, GO, carbon tonne) carries the full upstream ETT lineage

Five stages from the 10 kWh meter window to the permanent consumed stamp. Every stage records the One-Claim Ledger key at the appropriate scope (per-window at mint, per-aggregation at S04, finalised at S05). The non-transferability is encoded in the ETT contract: any attempted transfer reverts.

Where ETT is used

ETT serves as evidence across the energy side of the platform and the energy-to-carbon bridge:

Route 1 (Compliance Credits). ETT deposits into the regional compliance pool; 100 ETT aggregate to 1 Energy NFT (1 MWh tradeable unit); the pool mints the program's recognized unit (DC SREC, NJ SREC-II under ADI, Illinois Shines ABP, Maryland/Pennsylvania SRECs, Massachusetts SMART tariff eligibility, or Australia STCs). The Energy NFT OR the registry-native serial is the buyer-facing instrument.

Route 2 (Granular Attributes & Flex). ETT deposits into the regional granular-attributes pool; 100 ETT aggregate to 1 Energy NFT (1 MWh tradeable unit); the pool mints the recognized unit (I-REC globally, GO in the EU under AIB, or hourly-stamped certificates under EnergyTag protocols for 24/7 matching). Storage discharge hours are cryptographically linked back to source ETT so that time-shifted attributes preserve provenance.

Route 4 (Additionality Tonnes). ETT bundles into a vintage carbon batch with the EF snapshot, REC retirement IDs, storage dispatch proofs, and buffers. The verifier signs; the CARBON_TONNE contract mints; the backing ETT is stamped consumed-to-carbon. This is the route where one-claim discipline is most visible: any RECs, GOs, or I-RECs for the same kWh must be retired or immobilized at S04 before R4 will issue tonnes.

Route 9 (Diesel-Solar Microgrids). ETT mints from the PV and BESS side of off-grid or diesel-dominant sites. The carbon math (Path A fuel-based with 2.68 kg CO2/L diesel, or Path B kWh-based with EF_diesel_kWh typically 0.67-0.80 t/MWh) uses the ETT receipt as one half of the dossier; the diesel baseline pack is the other half. ETT consumed-to-carbon at S06 the same way as R4.

Route 10 (Renewable Thermal). Uses HTT, not ETT. HTT is the heat-side analogue (1 HTT = 10 kWh-th) following the same atomic-proof discipline but on a separate token contract because the underlying asset class is thermal rather than electric.

ETT vs Energy NFT vs CLE vs registry serials

Developers and buyers occasionally conflate these tokens. The distinction matters because each one answers a different question. ETT and Energy NFT are two stages of the same evidence chain; CLE is a separate parallel token in the consumer-currency layer; registry serials are the external programmes' recognized units.

ETT (atomic, 10 kWh). Answers: did the kWh actually happen, and is it provable from a trusted meter? Non-transferable. Visible to producer and auditor; not transferable to a buyer.

Energy NFT (aggregate, 1 MWh). Answers: is there a tradeable certificate-conversion unit a buyer can convert to REC/GO/Carbon? Transferable. The aggregation result of 100 ETT.
CLE (consumer currency, 1 MWh). Answers: is there a circulating currency representing clean energy production for exchange trading, solar-equipment discounts, and peer-to-peer prosumer commerce? Transferable. Independent of ETT and the Energy NFT path; minted in parallel from the same production trigger but routed to a different economic purpose.

Registry serial (REC, GO, I-REC, etc). Answers: does the unit satisfy a specific external programme's eligibility rules and integrity bar (RPS compliance, RE100 procurement, 24/7 hourly matching)? Lives in the external registry; EDMA holds the mapping to the upstream ETT chain.

A single 10 kWh ETT is too small to be tradeable in a meaningful market; a 1 MWh Energy NFT is the right size for the certificate-conversion path. An Energy NFT is too generic to satisfy specific compliance programmes; a REC or GO is the specific instrument the programme recognises. CLE, separately, is the right size for a consumer currency (1 MWh of clean energy as a unit of value for trading and commerce). The protocol provides these layers so each question gets the right answer.

Where it stands

ETT is operational. The ETT_MINT contract is live on the EDMA L2 devnet (chain ID 741), wired to the PoV Gate at the METER_WINDOW milestone. The contract has been exercised against the Week 1 protocol settlement test (transaction hash on the devnet record shows seven events fired, with all five protocol invariants enforced).

What remains for ETT at the mainnet milestone: scale-up of attestor onboarding (METER_OP role for utilities and IoT aggregators across more jurisdictions), live integration with regulated meter data feeds in target markets, and the verifier panel finalising their attestor signatures for the higher-throughput compliance programmes (Route 1 jurisdictions especially).

For the protocol-level architecture ETT depends on, see Proof-of-Verification, One-Claim Ledger, and Attestor Registry. For the consumer-currency token minted in parallel from the same production trigger, see CLE. For where ETT is consumed, see R1 Compliance Credits, R2 Granular Attributes, R4 Additionality Tonnes, and R9 Diesel-Solar Microgrids.