The standard IoT architecture is centralized: devices connect to a cloud server, the cloud server processes data, the cloud server distributes results. This works — until the cloud server goes down, the cloud provider changes its pricing, the internet connection is interrupted, or a regulator decides that health or financial data cannot leave the country.
The Mesh IoT Network (MIoTN) architecture that FidesInnova supports replaces the cloud hub with a peer-to-peer fabric. Devices communicate directly with each other and with local nodes — the cloud is optional, not mandatory. And every interaction in the mesh is governed by ZKP-backed Service Contracts, making trustless peer-to-peer IoT a practical reality.
A Mesh IoT Network is a topology in which each node (device or relay) communicates with its neighbors directly, without routing all traffic through a central server. Data propagates through the mesh by hopping from node to node until it reaches its destination — or is available to all nodes if broadcast.
Mesh networks can cover large areas — warehouses, farms, industrial plants, city blocks — with low-cost nodes, without running cabling or relying on cellular coverage everywhere.
Nodes only need to reach their nearest neighbors, not a distant cloud server. Shorter transmission distances mean lower power consumption — critical for battery-powered sensors.
No single point of failure. A failed sensor, jammed frequency, or severed cable affects only the immediate area — the mesh routes around the problem automatically.
Data can stay local — processed and stored within the mesh without ever leaving the physical site. Critical for healthcare, defense, and financial applications subject to data residency regulations.
Local peer-to-peer communication has millisecond latency versus hundreds of milliseconds for cloud round-trips. Essential for real-time control applications.
Processing and storage happen at the edge. Cloud bandwidth and compute costs drop dramatically — or disappear entirely for applications that can operate fully locally.
FidesInnova's MIoTN implementation uses a three-tier architecture:
The leaf nodes of the mesh. These are IoT sensors and actuators running firmware with the FidesInnova ZKP SDK embedded. Each device generates ZKP proofs for its readings and communicates via MQTT to its local gateway (Tier 2).
FidesInnova Nodes deployed locally — in a building, a factory floor, a vehicle, or a field installation — form the backbone of the mesh. Each node:
Proofs generated in the mesh are periodically anchored to the FidesInnova blockchain for permanent, publicly verifiable storage. This can happen in real time (if internet is available) or in batch mode when connectivity is intermittent (field deployments, remote sensors).
One of the most powerful features of FidesInnova's MIoTN architecture is that Service Contracts can execute across multiple nodes in the mesh — not just on a single central server.
Consider a smart agriculture deployment: 50 soil moisture sensors distributed across a 200-hectare farm, each connected to a local FidesInnova Node at the field edge. A Service Contract running on each node aggregates the readings for its local zone, generates a ZKP proof of the zone average, and shares that proof (not the raw readings) with a coordination node at the farm office.
The coordination node receives verified zone averages without ever seeing the individual sensor readings. If a zone needs irrigation, the coordination node can trigger actuators in that zone — the entire decision chain is provably correct, with ZKP proofs at every step.
In a conventional mesh network, a compromised node can inject false data that propagates through the mesh. A neighbor node has no way to know whether data from a peer node is authentic.
FidesInnova's ZKP framework solves this. Every message that propagates through the mesh carries a proof of its origin and correctness. A receiving node does not need to trust the sending node — it verifies the proof. If the proof fails, the message is rejected. This makes the FidesInnova mesh adversarially resilient: a compromised node cannot inject false data, because it cannot forge valid ZKP proofs.
A manufacturing facility deploys 200 vibration, temperature, and pressure sensors across production machinery. Local FidesInnova Nodes at each production line aggregate readings, run anomaly detection Service Contracts, and share verified alerts with the plant control room. The corporate IT network has no access to raw sensor data — only to ZKP-verified summaries.
University campus buildings each host a FidesInnova Node. Building nodes share verified energy consumption data directly with each other for demand balancing — without routing through a central university IT server. The mesh can continue operating and managing energy locally even during internet outages.
Disaster response teams deploy portable FidesInnova Nodes that automatically form a mesh on arrival. Environmental sensors (air quality, structural integrity, temperature) feed the mesh. All data is locally processed and ZKP-verified — coordination happens peer-to-peer, without depending on any infrastructure that may have been destroyed by the disaster.
Each stage of a supply chain — manufacturing, warehouse, transport, distribution — hosts a FidesInnova Node. Products carry RFID/BLE tags that check in with each stage's node. Each check-in generates a ZKP proof of location, condition, and handling. The full provenance chain — verified at every step — is available to any downstream party, without any single entity controlling the audit trail.