Architecture
ChainIO separates operational throughput from governance guarantees: raw payloads stay off-chain; hashes, signatures, device identity, and compliance outcomes are anchored on a permissioned Hyperledger Fabric network with 2-of-3 multi-organisation endorsement.
Layer 1: Edge and gateway
Devices and gateways sign canonical telemetry. Only registered, active devices can submit. SQLite buffering preserves order during connectivity gaps.
Layer 2: Blockchain governance
Device registry, event anchors, and compliance alerts live in chaincode on channel chainio-poc. Writes need endorsement from a majority of independent organisations — not a single admin.
Layer 3: Storage and index
Off-chain payload store plus PostgreSQL index for fast dashboard queries, alerts, and verification metadata. Anchoring only hash roots keeps ledger throughput practical for high-volume IoT.
Layer 4: Application
Role-based dashboards for city and plant operators, regulator exports, and public verify/explorer routes that anyone can use without trusting a single dashboard vendor.
Fabric organisation map (PoC)
Endorsement policy: majority of organisations (2-of-3) for write transactions. State PCB endorses both city environmental and industrial compliance data.
| Organisation | MSP ID | Endorsement role |
|---|---|---|
| ChainIO Platform | OrgPlatform | Gateway operations and platform endorsement |
| City ULB | OrgULB | Municipal environmental data endorsement |
| State PCB | OrgPCB | Regulatory endorsement for city and industrial compliance |
Anchor-only storage model
Every IoT reading does not need its own consensus round. The gateway hashes signed payloads, stores full JSON off-chain, and anchors integrity proofs on Fabric. Independent verifiers recompute hashes and check signatures against the on-chain anchor — the same pattern recommended for blockchain–IoT scale.
Try it in the live verifier or explorer.