A blockchain is a distributed ledger — many nodes hold copies of the same data with no central administrator. When a new transaction or proof is submitted, all nodes must agree on whether to include it and in what order. This agreement process is called consensus.
Consensus solves the Byzantine Generals Problem: how do distributed parties reach agreement when some of them may be malicious or unreliable? Getting this wrong means an attacker can double-spend, fake proofs, or rewrite history. Getting it right means the network can operate trustlessly.
All honest nodes agree on the same history. No two honest nodes accept conflicting blocks at the same height.
The network continues to make progress. New blocks are added at a predictable rate even if some nodes fail or behave badly.
Once a block is confirmed, it cannot be reversed. Critical for ZKP proof storage — a proof must be permanent once submitted.
The network can handle growing transaction volume. IoT deployments can generate thousands of proofs per second — the consensus must keep up.
Proof of Work (Bitcoin's mechanism) requires nodes to perform computationally expensive puzzles to propose blocks. The first node to solve the puzzle earns the right to add a block and receives a reward.
Proof of Stake (Ethereum post-merge) selects block proposers based on the amount of cryptocurrency they "stake" as collateral. Misbehaving validators lose their stake (slashing). No energy-intensive mining required.
DPoS (used by EOS, TRON) adds a layer of delegation: token holders vote for a fixed set of block producers (delegates) who take turns proposing blocks in a round-robin schedule. This dramatically increases throughput.
BFT consensus (PBFT, Tendermint, HotStuff) provides immediate finality — once a block is committed, it is final with no probability of reversal. This is achieved through multi-round voting among a known validator set.
IoT blockchain networks have requirements that existing consensus mechanisms were not designed to handle:
A network of 10,000 sensors each submitting proofs every 5 minutes requires 33 proof transactions per second. A city-scale deployment easily reaches thousands per second. Most blockchains cannot sustain this.
Real-time IoT applications — security alerts, industrial control — need proof confirmation in seconds, not minutes. PoW and standard PoS are too slow.
IoT devices cannot participate in staking or mining. The consensus must be run by infrastructure nodes — not the end devices. The device's only blockchain interaction is submitting a proof transaction.
A trusted IoT data layer cannot have a cartel of 21 block producers controlling it. The node network must be genuinely decentralized to prevent collusion and data manipulation.
FidesInnova's D2PoS (Delegated Decentralized Proof of Stake) is a consensus mechanism designed specifically to satisfy all IoT blockchain requirements simultaneously. It extends DPoS with additional decentralization mechanisms that prevent delegate cartels from forming.
D2PoS key design decisions:
The FidesInnova network has three types of participants:
Full blockchain nodes that participate in D2PoS consensus — propose and vote on blocks, verify ZKP proofs submitted to the chain, and earn block rewards. Running a validator requires holding a Node License and staking tokens.
The FidesInnova IoT Server acts as a relayer — collecting proofs from IoT devices via MQTT and submitting them to the blockchain. Relayers do not participate in block production but are essential for bridging the physical IoT layer with the blockchain layer.
Applications and users that verify proofs without storing the full blockchain. The FidesInnova mobile app and web dashboard operate as light nodes — they verify proof validity by downloading only block headers and the specific proof data they need.
Next Course
MQTT & Secure IoT →