Tesla Megapack PQ-Identity Vault.
1,010,000+ Tesla energy devices. Zero post-quantum protection. Hive ships the receipt rail.
The exposure
Thesis
Every Megapack cycle, whether it’s a charge, discharge, frequency response, or ancillary service bid, creates a settlement obligation. None of those obligations carry a cryptographic receipt today. A FERC examiner in 2036, a NERC auditor in 2038, or a ransomware actor in 2027 can all exploit the same gap: no dual-signed, post-quantum-verifiable identity trail exists for any of the 1.01 million devices. The Hive closes that gap with per-cycle dual-signed receipts, did:hive asset identity binding, NERC CIP-005-7 boundary attestation, and separately selected and specified chain anchor.
Device identity binding
Each Megapack unit is bound to a Decentralized Identifier under the did:hive asset method. The DID document carries both a classical Ed25519 public key and a post-quantum ML-DSA-65 public key (NIST FIPS 204, August 2024), ensuring verifiability past the NIST IR 8547 2035 disallowance horizon.
The DID document is signed off-chain and verifiable offline; any chain anchor must be separately selected and specified at device commissioning. Key rotation events are dual-signed by both the retiring and incoming key pairs and re-anchored. No central registry. No single point of compromise.
- Serial number to DID bindingdid:hive:asset:megapack-<serial>
- Ed25519 verification method (FIPS 186-5)classical · 2030 horizon
- ML-DSA-65 verification method (FIPS 204)post-quantum · 2055+ horizon
- Controller: NERC-registered operator DIDdid:hive:nerc:operator
- Key rotation: dual-signed, on-chain anchored90-day recommended cycle
Per-cycle dual-signed telemetry receipt
Every five-minute dispatch cycle, each Megapack unit generates a dual-signed telemetry receipt. The receipt is signed off-chain and verifiable offline; any chain anchor must be separately selected and specified.
NERC CIP-005-7 boundary attestation
Every receipt includes a NERC CIP-005-7 Electronic Security Perimeter (ESP) boundary identifier, validated against the NERC EACMS registry before anchoring. Receipts for energy transfers outside a validated ESP boundary are rejected. This prevents the settlement rail from being used for unmetered, synthetic, or out-of-boundary transactions.
- ESP boundary identifier in every receiptCIP-005-7 enforced
- Sender DID validated vs. NERC EACMS registryEACMS-bound
- Cross-boundary receipts rejected at protocol layerprotocol-enforced
- Audit log forwarded to NERC CIP-006 systemtamper-evident log
NERC CIP-005-7 Boundary Enforcement
Settlement is physically bounded by the regulated grid perimeter. Software policy alone doesn’t bound it.
NERC CIP-005-7 (Electronic Security Perimeters, effective April 1, 2023) defines the boundary within which BES Cyber Systems operate. GridWave Protocol enforces that all settlement receipts originate from within a validated ESP, binding the digital settlement rail to the physical regulatory perimeter.
FERC Order 2222 DER aggregation
Each receipt carries a FERC Order 2222 compliance attestation field, enabling DER aggregators operating Tesla Megapack portfolios to generate ISO/RTO-format settlement reports directly from the receipt chain. The GridWave receipt is the audit artifact, not a downstream summary.
| Receipt field | FERC Order 2222 mapping | Format |
|---|---|---|
| agent_a.did | FERC market participant ID | via DID registry |
| settled_kwh | Metered output, settlement interval | float64 |
| cycle_start/end | Settlement interval start/end | RFC 3339 UTC |
| lmp_reference | Price reference, LMP node | ISO node name |
| ferc_2222_compliant | Tariff compliance attestation | boolean |
| cip_esp_id | Physical delivery boundary | NERC CIP-005-7 |
Verify a Megapack receipt
Sample verification workflowA FERC examiner, NERC auditor, ISO/RTO settlement analyst, or counterparty can independently verify any Megapack receipt without contacting Hive or Tesla. The verification uses only: the receipt JSON, the sender DID documents (publicly resolvable), and the separately selected and specified chain anchor.
Verification steps
- Retrieve the signed receipt envelope (JSON) for the target receipt_id from the settlement relay or on-chain event log.
- Resolve
agent_a.didandagent_b.didto their DID documents at the did:hive resolver. - Retrieve
#key-ed25519-1and#key-mldsa65-1public keys for both agents. - Remove all four signature fields from the receipt JSON. Compute:
signing_input = SHA3-256(JCS(receipt_without_sigs)) - Verify
Ed25519.Verify(pubkey_a_ed, signing_input, sig_a_ed25519). MUST return true. - Verify
ML-DSA-65.Verify(pubkey_a_mldsa, signing_input, sig_a_mldsa65). MUST return true. - Repeat Ed25519 and ML-DSA-65 verification for agent_b signatures.
- Confirm on-chain: look up the Base 8453 SettlementAnchored event with matching receipt_id. Verify the on-chain calldata matches SHA3-256 of the signed receipt.
- Confirm NERC ESP boundary: validate
cip_esp_idagainst the NERC EACMS registry for the applicable entity.
Post-2035, after NIST IR 8547 classical algorithm disallowance, steps 5 is optional (Ed25519 no longer required for regulatory validity). Step 6 remains the binding verification. ML-DSA-65 carries the long-horizon trust.
Post-quantum readiness
Dual-signed today: valid through 2055+
ML-DSA-65 signed at issuance. Verifiable by FERC, NERC, and tax authorities post-2035 without re-signing.
NIST Interagency Report 8547 (November 2024 initial public draft) mandates the 2030 deprecation and 2035 disallowance of ECDSA, Ed25519, and RSA for new systems. A Megapack receipt signed only with Ed25519 in 2026 will be unverifiable to a FERC examiner in 2036 running on post-2035 quantum-capable infrastructure. The Hive attaches ML-DSA-65 at issuance, so no re-signing is needed at epoch flip.
ROI estimate: annual FERC audit exposure
Illustrative · not a claimed deploymentWithout Hive receipt rail
With Hive receipt rail
Per-event delta: $11.35M. Substrate cost runs $500K to $5M/year at enterprise tier, depending on receipt volume and FERC filing obligations. Numbers are illustrative; actual exposure depends on portfolio size and regulatory history.
Pricing
- Up to 10 Megapack units
- Per-cycle dual-signed receipts (Ed25519 + ML-DSA-65)
- did:hive asset DID provisioning
- separately selected and specified chain anchoring