Information Tech/Operational Tech

@IT/OT Chain & Cloud Australia Pty Ltd

Greek: πάντα πιστός
Sanskrit: का संस्कृत अर्थ
Hindi: हमेशा वफादार
Latin: semper fidelis
French: toujours fidèle
Basque: beti leial
Gaelic: dílis i gcónaí
Breton: bepred feal
Welsh: ffyddlon bob amser
Scots: aye leal
Scottish Gaelic: daonnan dìleas
Cornish: pupprys diwysyk
Manx: dy kinjagh jeelys
Portuguese: sempre fiel
German: immer treu
Icelandic: alltaf trúr
Old Norse: jafnan tryggr
Norwegian: alltid trofast
Old English: ǣfre trēowfæst
Middle English: alway trewe
Early Modern English: always faithful
Shakespeare (in a sonnet): “Constant ever”
Jean-Paul Sartre (Existentialist; in opposition
to Faith): “Mauvaise foi”
Frank Sinatra: “Not for just an hour, not for just a day
Not for just a year, but always.”
Czech: vždy věrný
Croatian: uvijek vjeran
Ukrainian: Вірний завжди
Armenian Cypriot: միշտ հավատարիմ
Maltese: dejjem fidila
Moroccan: دايما مخلص
Turkish: her zaman sadık
Kurdish: her tim dilsoz
Arabic: مخلص دائماً
Urdu: ہمیشہ وفادار
Farsi: همیشه وفادار
Tibetan: རྟག་ཏུ་བློ་དཀར།
Nepalese: सधैं वफादार
Chinese: 始终忠实
Japanese: 常に忠実
Korean: 언제나 성실한
Cambodian ជានិច្ចកាល ស្មោះត្រង់
Vietnamese: luôn chung thủy
Thai: ซื่อสัตย์เสมอ
Malay: sentiasa setia
Indonesian: selalu setia

Always faithful.

(Notwithstanding Sartre, existentialism and the US Marines.
Mauvaise foi, indeed)

________________________________________________________________________

You need us. We’re ‘the Minders’.

We are very proud to announce that the code in our Tx-Rails repository is building and deploying successfully. Demonstration scripts are being prepared and tested for this complete Proof of Concept unit, with a Cross-Network Aggregation System. We expect Tx-Rails will attract substantial commercial, NGO, government and academic interest.

Legend

Our intention was always to complete work on a system tolerating faulty servers according to the BFT formula n = 3f + 1: Tolerates 2 (7 Member-Classses, Overseers), 3 (10 governance-commercial, gov-regulators), 4 (13 Power-Funnel) in Fault States

Core Workload Rail	Nodes (N)	Models (M)	Tolerated Faulty Nodes (f = |[N-1]/3|)	Auditor Rail	Nodes (N)	Models (M)	Tolerated Faulty Nodes (f = |[N-1]/3|)
Enterprise Federations Tx-Rails	7	2 (4+3)	2	Audit Organisation Tx-Rails	7	2 (4+3)	2
Executives (Overseers) Tx-Rails	7	2 (4+3)	2	Audit Overseers Tx-Rails	7	2 (4+3)	2
Gov-Regulator National Meta-Federation	10	3 (4+3+3)	3	Audit Regulator National Meta-Federation	10	3 (4+3+3)	3
Gov-Commercial National Meta-Federation	10	3 (4+3+3)	3	Audit Gov-Commercial National Meta-Federation	10	3 (4+3+3)	3
Power-Funnel National Merkle Funnel	13	4 (4+3+3+3)	4	Audit Funnel National Merkle Funnel	13	4 (4+3+3+3)	4
National Registry	13	4 (4+3+3+3)	4	Audit Registry National Registry	13	4 (4+3+3+3)	4

 

This is ITOTCCA’s standardised Backend deployment platform. The assemblage is designed to be openly configurable to suit any stand-alone Enterprise, or General Enterprise Supply Chain Network or Enterprise/Medical Supply Chain Network. It is a doubly indemnified System such that while the Aggregators are working to calculate and record condensed evidence in the form of Transaction Merkle Roots onto an immutable Anchor DLT chain, the ChubbyChecker Auditors are cross-checking all processes (in 6 production layers), and are prepared to ‘detonate’ if more than the tolerated number of Byzantine Faults is evident in any layer. As noted elsewhere, in comparison to our doubly indemnified, dodeca-cross-checked, BFT ‘Rails’, Hyperledger or Corda are offering a single BFT layer with no further indemnification.

Although a full Application for a single medium-sized company could have 300 to 500 or more Use Cases, comprising their own sets of ‘Atoms’, forming the Use Case Graphs, our achievement of completing 762 Business Process Atoms in 31 categories, to be found at actions (Atoms), allows us to demonstrate the Business Process Design Studio, in operation with the Atoms, towards a final Proof of Concept aimed at potential investors and first customers. Admittedly, the Atoms will need to be adapted to the specific mode of integration chosen by customers and their networks. The Atoms cover initial approaches to the following industries and activities, serving as samples only, at this stage. All actions cooperate with your existing Business Procedures:

1. Actions in Common
2. Account Classes
3. Accounts Payable
4. Accounts Receivable
5. Actions Workflow
6. Aviation as Transport
7. Aviation Manufacturing
8. Bank
9. Banking Network
10. Budgeting Activities
11. Chart of Accounts
12. Construction Networks
13. Energy Production, Distribution, Retail
14. Food & Groceries – Supermarkets
15. Generalised Property & Asset Management
16. General Manufacturing
17. Health Supply, Hospital & Medical
18. Inventory Management
19. Industrial Internet of Things
20. Land Title Conveyancing
21. Mining & Minerals
22. Multiparty Transactions
23. Payroll
24. Pharmacies
25. Procurement
26. Profit & Loss/Balance Sheet
27. Real Estate Agencies
28. Social & Affordable Housing
29. Tax
30. Transport
31. Workflow

Nevertheless, ITOTCCA cannot assume that a company or supply network will not already have invested in their own GUIs, Databases, Middleware and Applications and in the added value Technicians’ and Users’ understanding of existing systems posesses, therefore we, as providers, must operate in such a market. For this reason we offer 4 levels of integration, with the foundation level simply needing to add, to a customer’s system, a small routine to calculate a hash signature of each transaction and send that signature to the Tx-Rails system. Details of all levels of Integration, with system integration presented as a Concept, can be found here

Recently we have diversified following the requirements of general national infrastructure, in particular the demands of combining a market-ready range of “shapes” of deployment, capable of “intra pyramid” and “inter pyramid” trade, against the need to rationalise in design and and to simplify. We have managed to reduce a very cumbersome full package (Tx-Rails) with its implied absolute isolation, yet initially unable to trade, into a simplified set of adapted sub-packages that can coordinate transactions in every situation, including globally. The simplified set still includes Tx-Rails, for high risk environments, but also a range of packages (still under the heading Tx-Rails) that provide 3 levels of trade-off between the Degree of Isolation accepted and the Degree to which you Share Resources, and therefore economise. You could refer to the Federation Trust Model page or investigate Schematics and Local View Global View.
For a context-rich analysis of forms of ‘Corruption’ and their prevention, see Proof that doesn’t ask you to trust us.
We have (a) one multi-faceted National Registry, (b) one coordinating and regulating National Meta-Federation and (c) one Merkle Funnel (calculating and anchoring Merkle Roots of Blocks of Transaction Trace Metadata); per country.
When combined with the National Registries (Who is this party, where do they legally sit, and who is entitled to stop them), these 4 Systems define the Tx-Rails Backend.
Details of the operation of our Business Process and Financial systems can be found at Block ‘n’ Tackle

There are 4 Classes of streams sending their metadata to the Merkle Funnel:

1. member-classes (organisation employee level)
2. overseers (organisation Executive level)
3. commercial governors (inter-company level of Executive trade control)
4. Regulators (supra-company regulation level – where applicable)

1 and 2 both share their Federation’s/Company’s installation (Tx-Rails)
3 and 4 both share National Meta-Federation as a base for their operations, when required.

________________________________________________________________________

Licence

Copyright (C) 2011-2026 IT/OT Chain & Cloud Australia Pty Ltd

This program (Tx-Rails) is free software: you can redistribute it and/or modify it under
the terms of the GNU Affero General Public License as published by the Free
Software Foundation, either version 3 of the License, or (at your option) any
later version.
See LICENSE (in Code Repository) for the full licence text.

ITOTCCA: Copyright (C) 2011-2026 IT/OT Chain & Cloud Australia Pty Ltd | | Contributors: John Lloyd Olsen, Edward Bruce Whittle, Muhammad Zohaib Ashfaq, Open AI (Chat GPT), Google (Gemini Code Assist: “Colonel Bogey”), Jetbrains (Junie: “Major Junie”), Anthropic Claude Agent | | Software Systems: Canonical (Ubuntu OS: 22.04 (PostgreSQL containers) & 24.04; Multipass; Microk8s; Juju; LXD);Rancher: k3s/k3d;Authentication: Elastos DID Sidechain; Authorisation: SpiceDB | | Inspiration: IBM India, Elastos & Rong Chen, BFT-SMaRt & Alysson Bessani, Petar Maymounkov & David Mazieres (Kademlia DHT), Hashgraph DLT and the Tendermint Project | | Hardware Systems: MSI, Intel, NVIDIA.

Commercial Licensing:
For organisations that require a commercial licence without AGPL obligations,
please contact john@itotchaincloud.com.au.

________________________________________________________________________

 

________________________________________________________________________

 

 

Tech Exec Dir, Founder & Chair	A dApp Login	Executive Director Strategy & Sales
John Olsen AACS   7/8 BE(Mech, UNSW), Cert IV CITP & Assoc Deg Comp (Charles Sturt University)		Gary Boucher
Director, Engineer & Strategist	Our Mascot	Executive Director-Front of House
Mario Larocca  MIEAust	IT/OT Chain & Cloud Australia Pty Ltd    Milo	Muhammad Zohaib Ashfaq BSc(S/Ware Eng), Riphah Int’l Univ., Pakistan MSc(S/Ware Eng), West Virginia University, United States مُحّمد زوہیب اشفاق
“BFT/DHT BUCORDE”: Dodeca-Quadruple-Networked Striving for the Gold Standard Zero Trust, Zero Tolerated Faults, Utter Data Privacy	A Dodeca-Quadruple-Networked Enterprise Application 6 x Auditor Networks vs 6 x Production Networks vs (GoldBFT + DHT + Kubernetes + Anchor) Networks	OUR FLAGSHIP MIDDLEWARE: Bucordo Security (GoldBFT) + Kubernetes merged with kademlia, and: “ChubbyChecker“ QUIC/HTTP/3 Transport, with End-to-End Encryption, 6-Stage x 132-Factor Cross-Checking, No Operator Read Access, No Operator Write Access

Tx-Rails Provides Access to Databases via Composable GO Actions, we call ‘Atoms’. If you Choose Integration Mode B, C or D, and when Authorised by your company, you can Form Your Own Business Processes from Atoms, in the Overseer Design Studio. These actions can be implemented as new Ionic GUIs or you could attach the new actions as pure Underlay to GUIs your engineers create against our SDK in your own traditional platforms.

The Overseer package then enforces those procedures, including conditional branching, process failure and process success.

Tx-Rails Incorporates:

1. The Following Twelve Operational “Rails”

The system is organized into a hierarchy of ten distinct layers, each with its own Byzantine Fault Tolerance (BFT) quorum (n = 3f + 1)
In the table below, the Statement of Risk pertains to the BFT systems in isolation.
The actions of ChubbyChecker will detect any occurrence of r > f, and detonate:

Layer	Nodes (n)	Tolerance (f)	Statement of Risk (r = f + 1)	Role
Member-Classes (Orgs)	7	2	3 servers are corrupted	Source of Truth for Private Enterprise Data
Overseers	7	2	3 servers are corrupted	Business Process Design & Governance
Governors	10	3	4 servers are corrupted	Cross-Network Transaction Coordination & Governance
Regulators	10	3	4 servers are corrupted	Supra-company Regulation
Powerfunnel	13	4	5 servers are corrupted	Cross-Network Consolidation and Merkle Root Calculation
Registry	13(registry)	4	5 servers are corrupted	314 classified as “Registry Integrity” checks
**Auditors-Orgs	7(orgs)	2	3 servers are corrupted	74 Trace Metadata Cross-Checks
**Auditors-Overseers	7(oseers)	2	3 servers are corrupted	32 Trace Metadata Cross-Checks
**Auditors-Governors	10(gov)	3	4 servers are corrupted	3 Trace Metadata Cross-Checks
**Auditors-Regulators	10(gov)	3	4 servers are corrupted	3 Trace Metadata Cross-Checks
**Auditors-Funnel	13(agg)	4	5 servers are corrupted	9 Trace Metadata Cross-Checks
**Auditors-Registry	13(registry)	4	5 servers are corrupted	3 m classified as “Registry Integrity” checks

2. These Four Technical Pillars

1st Network: Kubernetes (Project-Wide)	3rd Network: Global Distributed Hash Table Network Client Connections libp2p-kad-dht/kademlia
2nd Network: GoldBFT (Individual Orgs & Overseer Layer Federations of Organisations Pan-Network Aggregators Pan-Network Tophats Site-Wide Auditors) Byzantine Fault Tolerance Introducing Preferred Transports QUIC/HTTP3, gRPC/HTTP2	4th Network: Anchor Interface to DLT Tophats Anchor across Business Supply Networks Final Source of Truth

 

________________________________________________________________________

Crash Fault Tolerant Networks

Automatic Crash Recovery

________________________________________________________________________

Byzantine Fault Tolerant Networks

Inter-machinic consensus on inclusion and order-of-commitment of submitted transactions. Consistency across database replicas.

Tolerates 1 (4 total nodes), 2 (7 nodes), 3 (10 nodes) or 4 (13 nodes) in Fault States

Tolerates 2 (7 Member-Classses, Overseers), 3 (10 governance-commercial, gov-regulators), 4 (13 Aggregators, Tophats) in Fault States

________________________________________________________________________

Distributed Hash Table Network

Peer-to-Peer (including Peer to Server) Connectvity without DNS

________________________________________________________________________

132-item Transaction Trace Metadata Cross-Checking

System “detonates” if these Auditors detect more than the tolerated number of corrupt nodes

________________________________________________________________________

Decentralised Ledger Technology

Ultimate Sources of Truth. Not strictly Blockchains

But thousands of times faster in throughput, and just as immutable and secure. Global Governance by reputable consortium of companies and institutions.

________________________________________________________________________

The following diagram represents a collection of the backends of medical and business networks (Member-Classes nodes, Overseers nodes and Federations nodes) in one National or Regional jurisdiction, together with their associated Cross-Network jurisdictional virtual server (incorporating Aggregators nodes and Tophats nodes):

Clients (users) from the constituent Member Companies or Organisations have their own company’s “Entnum” associated with them at their authentication time. Although there are only 4 member-class nodes in a network, and many more members, and thus there will be a surfeit of Members each with their own set of “atoms” composing their own Business Processes, the Entnum field (together with the user’s Role) in a user’s session data is used to restrict access to only appropriate atoms and procedures:

Amongst ChubbyChecker’s cross-checks, in the Overseers layer, there are preventative checks which fire before a proscribed event occurs within a Business Procedure:

The degree to which we extend Security in Tx-Rails goes far beyond the amateur efforts of HyperLedger or Corda. They offer a single layer of BFT protection. We offer 8 times that. They insist on neglecting the very real dangers inherent with the Domain Name System. We use Kademlia’s superior Distributed Hash Table technology. Our 132-Angle ChubbyChecker auditing platform offers a level of final Security totally absent from our competitors. Choose freedom. Choose Security and Peace of Mind. Choose the Minders. 100% Fault Intolerance for Databases.

________________________________________________________________________

Tx-Rails

The sovereign cryptographic underlay for regulated networks

The Underlay! philosophy
Making Your Incumbent Systems
Continuously and Readily Auditable,
With Cryptographic Proof.

Tx-Rails is a Byzantine-fault-tolerant audit and ledger platform that sits **underneath** existing systems. It binds tamper-evident chain-of-custody, automated compliance evidence, and independently verifiable proof to the workflows you already run — without forcing your staff or customers to change a single screen. Australian-built, Australian-copyright, deployable as sovereign infrastructure in your jurisdiction.

We are not a blockchain replacing your ERP. We are the integrity substrate that makes the records in your ERP — and your supplier’s ERP, your regulator’s report, your insurer’s claim — provably the same record, provably untampered, provably backed by independent witnesses.

What we specialise in

Tx-Rails is built for sectors where **provable integrity** is not a feature but a regulatory, safety, or contractual obligation. Each domain below is a live product line with sector-specific evidence formats, regulator alignment, and integration patterns.

Social housing and regulator compliance

For UK housing associations operating under the **Social Housing Regulation Act 2023** and the April 2024 consumer standards. Cryptographically verifiable tenant-record provenance; supplier compliance attestation captured at contract-signing time; Awaab-style hazard escalation triggered by sensor-state changes with tamper-evident sequence. The regulator gets evidence acceptable under FRC Practice Note 14; you get an automated audit trail your housing officer never has to assemble by hand.

Healthcare records and patient flow

For health services subject to TGA UDI, GS1 traceability, and clinical-governance regulators. Per-tx attestation of medication administration, device-lot custody, transfer-of-care handoffs, and consent state. We do not replace your EHR or clinical interface — we provide cryptographic proof that what the EHR says happened, actually happened, in the right order, with the right witnesses. Patient-safety language is for regulator conversations; the platform’s load-bearing claim is *records you can prove*.

Industrial supply chains and manufacturing</span

Multi-tier supplier networks, where Org A produces inputs for Org B who produces inputs for Org C and an end-customer order at C cascades back through the chain. Tx-Rails gives every party a cryptographically verifiable view of inventory state, order flow, and ESG/Scope-3 evidence — without anyone having to trust anyone else’s database. Lot-level traceability is per-tx; aggregated procurement evidence is by-default.

Construction and large-project consortia

Milestone-triggered payment release, supplier compliance attestation at contract-signing time, change-order provenance, and dispute-resolution evidence. Particularly valuable for joint-venture projects where five companies share liability for one outcome and need independent witnesses to who-authorised-what.

Industrial IoT (Industrie 4.0 and OT integration)

Tx-Rails was designed with **Operational Technology** in mind. Sensor data, PLC state changes, robotic-cell handoffs, and asset-management events all attach as first-class transactions. The Kademlia-based edge overlay lets devices participate in the trust mesh without backhauling everything through a central server. Read and write both — closed-loop attestation, not just one-way logging.

Mining and minerals

Provenance from pit to port: ore-grade attestation, custody transfer between haulage / rail / port operators, royalty calculation evidence, ESG and human-rights attestation chains. Critical for the lithium / rare-earths supply chain where downstream OEMs increasingly demand cryptographic proof of upstream conditions.

Defence and critical infrastructure

Multi-classification record handling, supplier-mandate enforcement, joint-warfighter logistics with independent witness from allies in the same coalition. The architectural property that matters here: even a fully compromised single auditor cannot lie about the platform’s records — cryptographic verification trusts the math, not the operator.

Finance, asset management, and chart-of-accounts integrity

A 31-package action library covers double-entry accounting, dimensional cost allocation, asset lifecycle, inventory movements, and M-of-N multi-party authorisation. Plus a declarative workflow sequencer that triggers actions on block boundaries — match end-of-block-N, fire start-of-block-N+1 — for time-boxed financial workflows that need verifiable sequence.

Land title and real-estate conveyancing

Title-state attestation, transaction-chain integrity, conveyancing-firm independence. Even standalone-application deployments (single-firm Real Estate ops or Land Title Conveyancing) are catered for; the network effect compounds when multiple firms and regulators co-participate.

Local government and public-record retention

Council-level record integrity, citizen-benefit-program attestation, FOI-grade evidence retention. Sovereign hosting in-jurisdiction is the default — your records never leave the country, but they remain cryptographically verifiable across borders if you need them to be.

How it works

Every transaction passes through a multi-layer Byzantine-fault-tolerant consensus mesh, with each layer mirrored by an **independent auditor mesh** (ChubbyChecker) that performs 132 cross-checks per transaction and per block. Every 24 blocks, a Merkle root is anchored to the **Anchor Interface of a public distributed ledger** — giving you tamper-evidence verifiable from outside your own jurisdiction. The auditor’s trust root is mathematically independent of the workload’s; a compromise of one side cannot lie about the other. *This is the load-bearing safety property.*

How you integrate (without rewriting anything)

Four modes, pick the one that fits how much change your IT team can absorb:

The four modes

Mode	What customer does	Metadata fidelity	Use case
A. Hash-only	Nothing; tx-rails computes row-hash from CDC	24 / 33 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	27–29 / 33 (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	32 / 33 (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	33 / 33 with explicit semantic intent	The very-high-value flows where the customer wants explicit REVERSAL / CORRECTION / RESTATEMENT tagging

---

(Edge cases — bulk data, air-gapped operation, data sovereignty preservation — are covered in [`underlay-integration-patterns.md`](./underlay-integration-patterns.md).)

What you get

• A regulator-ready audit trail**, automated, per-transaction, with cryptographic proof.
• Independent witness across every layer**, so an internal-fraud or operator-compromise scenario is detectable, not silently catastrophic.
• Sovereign hosting in your jurisdiction**, with cross-jurisdictional verifiability when you need it.
• No replacement of the systems your staff actually use.** The platform is invisible in normal operation; you call on it when you need to prove something.

 

Talk to us

For a pilot or technical deep-dive: john@itotchaincloud.com.au. For investor materials: see [`tx-rails-master-pitch.md`](./tx-rails-master-pitch.md). For sector-specific evidence formats and integration patterns, every domain above has its own briefing in [`docs/pitch/`](.).

________________________________________________________________________

• Core Accounting Functions via the Block ‘n’ Tackle™ in C++, GO, Python, JavaScript & PLpgSQL © by IT/OT Chain & Cloud Australia Pty Ltd 2011-2026

 and Ionic Frameworks: Covering Mobile + Desktop.

~

Open the door to more effective working…

This is what you might call “Enterprise-Web2/3”.

“Web 2” is the term for an older, cloud-centralised format of internet organisation, which we are adapting to store enterprise structured data in an automated Database Trust scenario inspired by IBM, India, but which we have redesigned as a Hybrid form merged with decentralised blockchains and distributed application usage (ie the newest “Web3” formats), to deliver Ultra-Secure & Trustworthy IT/OT operations, with GOOD (Guaranteed Ownership Of Data). See our Security page and our Agreements page regarding GOOD. Hence ..

“Enterprise-Web2/3”.

DataChains/BlockBases and BlockChains provide immutable audit trails for all aspects of work in your organisation, and equally in ours. The importance of this in modern Risk Management, cannot be understated.

“We (the Software Developers) and you (the Business) get together and define the Use Cases (the range of things you want the system to do, in your own terms). We get the database organised, checked and rechecked. We get the cases encoded. You are at the helm of trials as every unit is completed. et Voila! The Key is Turned.”

Remember that Alliances of related Businesses can save a lot of money and enable otherwise unaffordable solutions!