Tx-Rails for Energy

A cryptographic audit substrate for every actor in the energy system — generators, network operators, retailers, market operators, regulators, financiers, insurers — without forcing any of them onto a single platform.

The energy sector is the most complex multi-jurisdictional, multi-counterparty trust environment in critical infrastructure. A single MWh travels from a wind farm through a transmission grid, across a balancing market, through a distribution network, into a retailer’s billing engine, onto a household meter, and finally into a sustainability disclosure that an auditor and a regulator must both accept — touching a dozen organisations, half a dozen regulators, and three different jurisdictions along the way. Every handover is an audit obligation. Every contract is a settlement obligation. Every meter reading is a tax obligation, a tariff obligation, a Scope-2 disclosure obligation, and increasingly a guarantee-of-origin obligation.

Tx-Rails sits **underneath** these existing systems — billing, ADMS, EMS, SCADA, market-clearing, settlement, GHG inventory — and produces a cryptographic, jurisdiction-independent audit trail for every event a counterparty, regulator, financier, or auditor would otherwise have to take on faith. We do not replace the incumbent systems. We make their outputs provably tamper-evident and interoperable across the federations they belong to. There are four modes of connection:

The four modes

Mode	What customer does	Metadata fidelity	Use case
A. Hash-only	Nothing; tx-rails computes row-hash from CDC	22 / 31 fields, no semantic intent	Low-stakes flows where the audit just needs “this row existed at time T”
B. CDC observation	Adds Debezium / equivalent to their DB; nothing in the app	25–27 / 31 (CRUD intent from CDC; user/role IF the customer’s table has audit columns)	Mid-stakes flows; most existing apps that already write created_by / modified_by to their rows
C. Gateway-mediated	Routes API traffic through the tx-rails gateway; app unchanged	30 / 31 (gateway sees the HTTP method, the JWT, the body — derives semantic intent from path + verb)	High-value flows; new app deployments where touching the network edge is cheap
D. SDK / atomic dual-write	App calls tx-rails alongside its own DB write	31 / 31 with explicit semantic intent	The very-high-value flows where the customer wants explicit REVERSAL / CORRECTION / RESTATEMENT tagging

---

The 26 federations

The energy stack is too federated to model as a single network. A wind-farm operator should not share a database with a gas-midstream pipeline operator; a market operator’s clearing data should not commingle with a retail biller’s customer ledger; an insurer underwriting offshore-wind risk should not see the same data surface as a regulator auditing transmission reliability. Each domain gets its own sovereign federation, with its own member set, its own data scope, its own cross-checks — interoperating through Tx-Rails’ shared underlay rather than through a shared application.

Electricity value chain

• tx-rails-energy-generation — generators (thermal, hydro, nuclear, solar, wind, geothermal). Unit dispatch, fuel burn, availability declarations, outage records, plant-level emissions intensity.
• tx-rails-energy-transmission — TSOs / ISOs operating bulk transmission. Line flows, contingency events, ancillary-service procurement, congestion costs, interconnector schedules.
• tx-rails-energy-distribution — DSOs / DNSPs operating low- and medium-voltage networks. Connection events, outage records, reliability indices (SAIDI / SAIFI / CAIDI), asset-replacement decisions.
• tx-rails-energy-retail — energy retailers. Customer enrolment, tariff assignment, consumption billing, hardship-program enrolment, disconnection events, dispute records.
• tx-rails-energy-market-ops — AEMO / ERCOT / National Grid ESO / market operators. Bid stacks, dispatch instructions, clearing prices, settlement statements, market-power monitoring.
• tx-rails-energy-metering — metering-data providers, AMI operators. Half-hour / 30-minute interval reads, NEM12 / DLMS / IEC 62056 records, suspect-data flags, re-energisation events.
• tx-rails-energy-der-microgrids — distributed-energy resources, behind-the-meter solar, residential / commercial batteries, microgrid controllers, VPP aggregators.
• tx-rails-energy-flexibility — demand response, ancillary services, capacity markets. Curtailment offers, frequency-response delivery, reserve activations, settlement evidence.
• tx-rails-energy-ev-charging — public + private charging operators. Charge sessions, OCPP / OCPI transactions, smart-charging signals, V2G discharge events.

Gas value chain

• tx-rails-energy-gas-upstream — production. Well-level production volumes, royalty calculations, flaring + venting events, methane-leak survey results.
• tx-rails-energy-gas-midstream — pipelines + storage. Pipeline nominations, custody-transfer measurements, storage injections / withdrawals, integrity-management events.
• tx-rails-energy-gas-downstream — distribution + retail. Distribution-network metering, customer billing, mains-replacement records, leak surveys.
• tx-rails-energy-refining-lng`** — refining, LNG liquefaction + regasification, bunkering. Yields, custody transfers, environmental compliance, cargo records.

Cross-cutting commercial

• tx-rails-energy-carbon-renewables — renewable-energy certificates (REC / GO / I-REC), guarantees of origin, voluntary carbon credits. Issuance, transfer, retirement — the audit trail that defends a Scope-2 disclosure or an offset claim.
• tx-rails-energy-payments — settlement payments between counterparties (generator → market → retailer; retailer → customer; capacity-market clearing). Payment events bound to settlement events, no reconciliation drift.
• tx-rails-energy-identity-kyc — participant identity, beneficial-ownership, sanctions screening across counterparties. KYC events with provenance, not a black-box screening result.
• tx-rails-energy-risk-compliance — exposure, credit limits, position monitoring, prudential capital calculations. The audit trail behind every “we were within limit” assertion.
• tx-rails-energy-insurance`** — physical-asset, business-interruption, parametric-weather, cyber, environmental-liability cover. Claim triggers bound to verified telemetry rather than to claimant assertion.

Cross-cutting operational

• tx-rails-energy-iot-scada — field telemetry from substations, plants, pipelines, wind / solar farms. Equipment provenance, calibration events, alarm acknowledgements, PLC program changes — the IEC 62443 / NERC CIP / NIS2 evidence surface.
• tx-rails-energy-weather-geo — meteorological observations + forecasts, soil / hydrological data, satellite imagery. The inputs to renewable-resource forecasts, settlement parameters, parametric-insurance triggers.
• tx-rails-energy-oems-maintenance — OEM service records, scheduled / corrective / predictive maintenance, spare-parts provenance, warranty events.
• tx-rails-energy-cybersec-soc — security operations centre events. Auth failures, anomalous traffic, intrusion attempts, firmware-verification failures — a forensic timeline that survives local-log tampering.
• tx-rails-energy-safety-operations — process safety events (IEC 61511), worker safety, near-misses, lockout / tagout, permit-to-work, emergency response.

Governance + regulatory

• tx-rails-energy-meta-federation — the top-level governance federation. Member admission, role assignments, network-policy changes, dispute escalations across the 26 federations.
• tx-rails-energy-authorities — regulators (Ofgem, AEMC, AER, FERC, ACER, IEA). A read-window into the underlay scoped to each authority’s statutory remit — no parallel data submission, no reconciliation cycle.
• tx-rails-energy-audit-compliance — independent auditors, assurance providers, sustainability raters. Cryptographic verification of any claim sourced from the underlay, without privileged access to the auditee’s primary systems.

—

What the underlay guarantees

Every event written to any of these 26 federations carries the same four properties, enforced cryptographically rather than contractually:

1. Tamper-evidence at the row level. Every record is bound into a Merkle slab. Slab roots anchor to Hedera Consensus Service every 24 blocks, giving you a public, jurisdiction-independent timestamp that you can verify with a single hash and no privileged access.

2. Multi-tenant isolation by entnum. Each member organisation operates within its own enterprise number. The trust boundary is enforced at the gateway, not at the database — there is no shared-credentials path between members of the same federation.

3. 149 cross-checks per transaction. Tx-Rails’ ChubbyChecker audit subsystem runs 149 integrity verifications on every transaction and every block, on independent BFT replicas with no shared failure domain with the workload nodes. If a compromised server count exceeds the BFT threshold, the audit mesh detonates the network rather than silently producing incorrect outputs.

4. No data sovereignty give-up. Each federation’s data stays in the jurisdiction it was generated in. Cross-jurisdictional verifiability comes from the Merkle anchor on Hedera, not from data movement.

How you integrate

Tx-Rails is a substrate, not a replacement. You connect to the federations your organisation belongs to via one of three modes:

• Hash-only — your existing systems remain the system-of-record; Tx-Rails carries only the cryptographic commitment. Lowest integration cost, lowest reconciliation surface.
• Atomic dual-write — every business-relevant event lands in both your system and Tx-Rails in the same transaction. Strongest audit story.
• CDC observer — Tx-Rails subscribes to your change-data-capture stream and writes the cryptographic record asynchronously. No application-layer code changes.

A generator can run Hash-only against its EMS, a retailer can run Atomic dual-write through its billing engine, and a regulator can run CDC-observer across the lot — all interoperable on the same underlay.

—

What this unlocks

• Scope-2 + Scope-3 disclosures that survive third-party assurance. Every MWh in a corporate sustainability claim is traceable to a metered generation event with cryptographic provenance and a Hedera-anchored timestamp.
• Real-time wholesale settlement without a trust intermediary. Generator dispatch → market clearing → retailer settlement → customer billing → payment, all bound into the same audit trail. Disputes resolve against a shared cryptographic record, not against four reconciliation reports.
• Parametric insurance with verifiable triggers. A wind-farm BI policy that pays out when measured production drops below a threshold doesn’t need a claims adjuster — it needs a verifiable measurement. The underlay provides the measurement.
• Regulatory oversight without privileged backdoors. Authorities consume a scoped read-view of the underlay. There is no separate compliance-submission system, and no reconciliation cycle between operator records and regulator records.
• Mergers + acquisitions without forensic data dumps. A buyer’s diligence team verifies an asset’s operating history by replaying the cryptographic record, not by trusting the seller’s report.

Where we are

Tx-Rails is shipping today as the underlay for a UK housing pilot and an Australian R&D programme; the **`tx-rails-energy-*`** federations above are the production-target taxonomy for the energy vertical. Charter-member discussions are open with generators, network operators, market operators, and large retailers in the UK, AU, and EU. If your organisation is one of those — or an authority looking for cryptographic visibility into the sector you regulate — we want to hear from you.

Contact: [john@itotchaincloud.com.au]

---

Tx-Rails — Built by IT/OT Chain & Cloud Australia (ITOTCCA). Sydney · London.