Cryptographic Per-Trade Proofs for Localvolts

Real Blockchain Solutions · Anchor every matched trade on BSV mainnet · Both parties can verify independently

Localvolts is the only retailer in Australia doing genuine peer-to-peer matching with an AEMO licence. That solves the hardest problem — the bureaucratic one — that has stopped every blockchain-first energy startup including Power Ledger.

This page demonstrates a complementary layer: every matched trade is committed on chain as cell_hash = SHA-256( matching_rule_hex ‖ trade_inputs_sha256 ‖ result_sha256 ). The commitment is 32 bytes, costs under AU$0.01 per anchor, and lets both Alice and Bob — and any auditor either of them brings — independently verify that the clearing they were billed for is the clearing Localvolts actually ran.

The mechanism is identical to what's already running for battery dispatch (see live exhibit below). The Localvolts-shaped version is the second exhibit on this page.

Exhibit 1 — Live mechanism, anchored on mainnet today live

Battery dispatch backtest — QLD1 May–Jul 2022 (gas crisis)

Same envelope shape, applied here to battery dispatch instead of P2P trade matching. The cryptographic primitive is identical: a 32-byte commitment to (strategy_hex, input_data_sha256, result_sha256). Confirms the pipeline produces real on-chain anchors that any browser can verify.

Strategy hex
7c03a08601a2690114a2 10 bytes
Data SHA-256
ce4102258474cff91861b61262e4005459efa5710133396ad64d7c604314b6a0
Result SHA-256
9bb6f0fe69eb263e8e5783b901ac25893b87588d485b024d5ccf5b225613bcbb
cell_hash (on chain)
7b9e848e7b0ebce9d13a7b3b21589bb2a11f51b05726f9e8b62c847b3ba1479d
Transaction
a9ce2f401164fda09312e25a5186de20fe90f2021d152a3a6905af61779ccd8a
Not yet verified
Exhibit 2 — Localvolts production shape (sample trade)

Sample matched trade — Alice → Bob, 5 kWh @ AU$0.20/kWh

A representative Localvolts-shaped trade with all commitment hashes computed below. In production deployment each matched trade is anchored automatically; both Alice and Bob see the txid in their account view alongside the trade record.

{
  "trade_id": "lv-demo-2026-05-26-001",
  "settlement_interval": "2026-05-26T13:45:00+10:00",
  "buyer":  { "alias": "Bob",   "bid_cents_per_kwh": 22, "max_kwh": 5.0 },
  "seller": { "alias": "Alice", "ask_cents_per_kwh": 18, "available_kwh": 5.0 },
  "matching_predicate_hex": "7ca2",
  "matching_rule": "OP_SWAP OP_GREATERTHANOREQUAL — truthy iff buyer bid >= seller ask"
}

What Bob sees in his account

Bought 5.0 kWh from Alice at AU$0.20/kWh

Total paid: AU$1.00

Anchor txid: 6d9d82fe…502e4 →

What Alice sees in her account

Sold 5.0 kWh to Bob at AU$0.20/kWh

Total received: AU$1.00

Anchor txid: 6d9d82fe…502e4 →

Matching predicate hex
7ca2 2 bytes
Trade inputs SHA-256
d0f7f2c9d0a6be96f407442159cf93c4ff6fef0dbccf10d5c84d3dddb89d6fbf
Clearing result SHA-256
73d6d3c4df8a9f90fbb5ae84ca0133be088ab0af1393c9588ac03b27b10b4740
cell_hash (computed)
47855f492479fca71ddf46b3bbed761b19f87ad08161f1811eaedfbcdd24b625
Transaction
6d9d82fe7e1396496f9942c24171ea4fc069f03ac8c9526614f69cfec25502e4 · view raw on WhatsOnChain →
Not yet verified
What deployment would deliver

Scope: AU$50,000, 4–6 weeks, fixed-price. Larger or smaller scope quoted separately if either fits better.