Tx-Rails for Transport
A cryptographic audit substrate for every leg of every journey — aviation, maritime, rail, road, intermodal, urban mobility — and every counterparty that needs to verify what happened on those journeys: regulators, accident investigators, customs authorities, shippers, insurers, financiers, and the public.
Transport is the audit problem with the largest geographic surface. A single shipping container traces a route through a Vietnamese factory’s outbound dock, an inland-haul truck, a port-of-loading terminal, an ocean voyage, a transhipment hub, a destination port, a customs clearance, an intermodal lift, a rail leg, a DC, a last-mile run, and a consignee door — touching 10+ jurisdictions, 20+ operators, half a dozen regulators, and at least three modal change-of-custody points before the door is opened. A single aircraft tail-number accumulates a maintenance history, a flight history, an incident history, and an ownership history that has to remain verifiable across decades and across borders, well after the operators that produced it have been merged, sold, or wound up.
Every handover is an audit obligation. Every container-weight declaration is a SOLAS-VGM obligation. Every aircraft maintenance entry is an EASA / FAA / CASA obligation. Every chain-of-responsibility decision under Australian heavy-vehicle law is a director-criminal-liability obligation. Every bill of lading is the cornerstone of $30 trillion / year of international trade. The system runs on documentary trust at a scale where the documentary trust is increasingly insufficient — bill-of-lading fraud, container-weight misdeclaration, maintenance-record falsification, AIS spoofing, and ELD tampering are all live, ongoing problems with names attached.
Tx-Rails sits underneath the incumbent systems — TMS, WMS, ACARS, AIS, ECDIS, traffic-management, signalling-management, customs-broker, telematics, fatigue-management — and produces a cryptographic, jurisdiction-independent audit trail for every event a regulator, investigator, shipper, insurer, or financier would otherwise have to take on faith.
The 19 federations
A regional airline maintenance department, a Capesize-bulker owner, a rail-freight operator, an Australian heavy-vehicle prime contractor, a customs broker in Singapore, and an air-accident investigator with a 20-year remit — they do not belong on the same database, and they cannot afford to. Each mode and cross-cutting 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.
Modes
tx-rails-transport-aviation— airlines, MROs, aircraft owners + lessors, ANSPs, airports. Tail-number-level maintenance records, ADS-B + ACARS flight records, fuel-burn + emissions data, occurrence reports, fatigue-management evidence, training + licence records. The structural answer to the trust collapse that hollowed out Boeing after the 737 MAX investigations — every maintenance entry, every airworthiness directive compliance event, every flight-data exceedance bound to a Hedera-anchored timestamp that survives the operator long after the operator stops existing.tx-rails-transport-ports-harbours— port + harbour authorities, terminal operators, stevedores, pilots, tug operators. Berth schedules, pilot exchanges, mooring events, container moves, draft surveys, terminal-handling charges, gate-in / gate-out records.tx-rails-transport-shipping— ocean + coastal shipping operators, ship managers, classification societies, P&I clubs. AIS positions, voyage events, port-call records, cargo manifests, SOLAS-VGM container-weight declarations (the fix for chronic mis-declaration), MARPOL discharge records, bunker-delivery notes, ballast-water-management records, emissions evidence under the IMO 2050 trajectory.tx-rails-transport-rail— passenger + freight rail operators, infrastructure managers, ROCs, regulators. Train consist details, control-centre events, signalling exceptions, level-crossing activations, derailment + SPAD (signal passed at danger) records, ETCS / PTC compliance evidence, track-maintenance records.tx-rails-transport-road-highways— road authorities, traffic-management operators, toll operators, highway-maintenance contractors. Incident records, asset-condition surveys, work-zone records, toll-transaction provenance, ANPR events (with privacy-preserving handling).tx-rails-transport-trucking-logistics— heavy-vehicle operators, freight forwarders, fleet managers. Driver-licence + fatigue-management records, electronic-work-diary entries, telematics events, mass-distance-time records under the Australian Heavy Vehicle National Law’s Chain of Responsibility (and equivalents under EU Driving Time Directive + US FMCSA HOS), load-restraint evidence, dangerous-goods documentation.tx-rails-transport-intermodal— multimodal operators, container leasing, ICDs. Container moves across modes, lift events, custody-transfer evidence, condition-survey records.tx-rails-transport-urban-mobility— public-transit operators, micromobility + ride-share operators, AV-pilot programmes. Service-delivery records (reliability + on-time-running, the metrics state contracts hinge on), driver / rider safety events, AV decision-logs (the audit trail an investigator needs after an AV-involved fatality), gig-worker hours + pay records.
Cross-cutting commercial
tx-rails-transport-payments— settlements across the chain (freight payments, port + terminal charges, toll receipts, fuel + bunker payments, insurance premiums + claims). Payment events bound to operational events, no reconciliation drift between TMS records and accounts-receivable.tx-rails-transport-identity-kyc— counterparty identity, beneficial-ownership, sanctions screening. Critical for shipowners + charterers in jurisdictions with OFAC / EU / UK Maritime sanctions exposure (Russia, Iran, Venezuela, North Korea, dark-fleet activity).tx-rails-transport-risk-compliance— exposure, credit limits, sanctions screening of voyage parties, prudential capital. The audit trail behind every “we conducted appropriate due diligence on this charter party” assertion.tx-rails-transport-insurance— hull, P&I, cargo, freight-forwarder liability, aviation hull + war, motor + transit, parametric weather + delay. Claim triggers bound to verified telemetry rather than to claimant assertion — a marine general-average claim, an aircraft hull total-loss claim, a stolen-cargo claim, all settled against an audit trail the insurer + insured + reinsurer all see the same.tx-rails-transport-customs-border— customs authorities, biosecurity, drug-enforcement, border-protection. Export + import declarations, country-of-origin attestations, certificates of origin, provenance evidence for sanctions + dual-use-export compliance, biosecurity inspections + treatments.
Cross-cutting operational
tx-rails-transport-iot-telemetry— telematics, ACARS, AIS, train-on-board, infrastructure-sensor arrays. Equipment provenance, calibration events, alarm acknowledgements, firmware-update evidence — the IEC 62443 / NIS2 / TSA Cybersecurity Directive evidence surface for transport OT.tx-rails-transport-weather-geo— meteorological + hydrological + seismic data. The inputs to flight-planning, voyage-planning, route-restriction, parametric-insurance-trigger decisions that have to remain verifiable years after the journey.tx-rails-transport-oems-maintenance— OEM service records, scheduled / corrective / predictive maintenance, spare-parts provenance, warranty events, airworthiness directives, recall notices. Every entry in an aircraft’s logbook is a future safety-investigation input — captured immutably + Hedera-anchored.tx-rails-transport-cybersec-soc— security operations centre events spanning corporate IT + OT (ATC, port + terminal systems, signalling, telematics). Forensic timeline that survives local-log tampering after a breach — the structural answer to the Maersk-NotPetya-class operational paralysis that costs operators hundreds of millions when it lands.
Governance + regulatory
tx-rails-transport-meta-federation— the top-level governance federation. Member admission, role assignments, network-policy changes, dispute escalations across the 19 federations.tx-rails-transport-audit-compliance— independent auditors, accident investigators (ATSB / NTSB / AAIB / TSB / MAIB / DSB), classification societies, ICAO + IMO safety auditors, ESG raters. Cryptographic verification of any claim sourced from the underlay, without privileged access to the auditee’s primary systems — and without depending on the auditee still existing at the time of investigation.
What the underlay guarantees
Every event written to any of these 19 federations carries the same four properties, enforced cryptographically rather than contractually:
- 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. Critical when the dispute is over what an ELD recorded six months ago, what an AIS reported during a voyage that’s now under sanctions investigation, or what an aircraft maintenance record looked like before the operator went into liquidation.
- Multi-tenant isolation by
entnum. Each member organisation operates within its own enterprise number. A shipowner, a charterer, a port authority, a stevedore, a P&I club, and a flag-state administration all share a federation but no shared-credentials path — the trust boundary is enforced at the gateway, not at the database. - 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.
- 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. A Singaporean shipowner, a Saudi loading port, a Suez transit, a Rotterdam discharge, and an EU customs authority verify the same voyage record on the same audit trail without any of them moving the underlying data.
How you integrate
Tx-Rails is a substrate, not a replacement. You connect to the federations your organisation belongs to via one of four modes:
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 |
A regional carrier can run Hash-only against its MRO system, a Tier-1 box-line can run Atomic dual-write through its voyage + AIS + cargo stack, and a flag-state administration can run CDC-observer across every vessel under its flag — all interoperable on the same underlay.
What this unlocks
- Aircraft maintenance + airworthiness records that survive the operator. Every logbook entry, every airworthiness-directive compliance event, every flight-data exceedance bound to a Hedera-anchored timestamp. Records remain verifiable decades later, after airline mergers, lessor transitions, or operator insolvencies — the structural answer to the trust gaps that have repeatedly surfaced in second-hand-aircraft markets.
- Safety investigations that don’t depend on operator cooperation. An ATSB / NTSB / AAIB investigator with read-window access to the underlay can replay an accident’s lead-up from telemetry + maintenance + crew-roster + ATC + weather records without subpoenaing the operator. Investigations move faster + findings hold up better.
- Container-weight + cargo-manifest declarations that the regulator can verify continuously. Every SOLAS-VGM weight, every container manifest, every dangerous-goods declaration captured immutably + Hedera-anchored. The structural fix for the chronic-mis-declaration problem that contributes to container-stack failures + onboard fires.
- AIS + sanctions-compliance evidence that defends a charter. Every position report, every dark-period explanation, every ship-to-ship transfer captured immutably. A charterer can demonstrate sanctions due-diligence with cryptographic backing; a flag-state administration can audit its registered fleet with verifiable evidence.
- Chain-of-responsibility evidence under Australian heavy-vehicle law. Every fatigue event, every mass-distance-time record, every load-restraint inspection, every consignor + scheduler + driver decision bound cryptographically — the structural defence against the director-criminal-liability provisions in the HVNL (and equivalents under EU + US heavy-vehicle law).
- Bill-of-lading fraud defence. A bill of lading anchored cryptographically at issuance + transfer events captured immutably — a structural answer to the fraud + duplication patterns that cost trade finance billions per year.
- Parametric insurance + delay-cover claims with verifiable triggers. A flight-delay claim, a port-congestion claim, a weather-deviation claim, a war-risk hull claim — settled against an audit trail the insurer + insured + reinsurer all see the same.
- Public-transit performance contracts with continuous regulator visibility. Every on-time / reliability / service-delivery metric captured immutably + verifiable in real time. The structural fix for the chronic disputes between state transport agencies and franchised operators over performance penalties + service rebates.
- Autonomous-vehicle decision logs that survive a fatality investigation. Every perception, every planning decision, every actuator command from an AV captured immutably + Hedera-anchored. The structural answer to the credibility crisis that follows every AV-involved death.
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-transport-* federations above are the production-target taxonomy for the transport vertical. Charter-member discussions are open with airlines + MROs, shipowners + charterers, port + terminal operators, rail operators + ROCs, heavy-vehicle prime contractors, accident-investigation authorities, and customs + border authorities in AU, UK, EU, and Asia. If your organisation is one of those — or a safety regulator looking for cryptographic visibility into the operators you oversee — we want to hear from you.
Contact: john@itotchaincloud.com.au
Tx-Rails — Built by IT/OT Chain & Cloud Australia (ITOTCCA). Sydney · London.