Conference Talks · Part 2 of 2
Your Device Doesn't Have to Trust Its Manufacturer
Devices and software should not depend on a supplier's server to decide what is true, who is authorized, and which code runs. On-chain state plus local verification moves that decision to the edge.

Target audience: Intermediate · 6 min read
TL;DR
- Most connected devices, and most software that reads a blockchain, let a supplier decide what is true, who may use them, and which code runs.
- When that supplier disappears, the device often stops working. No attack is required.
- The remedy is public state plus local verification: the consumer checks proofs regardless of who delivered the bytes.
- Verification does not restore a shut-down cloud service or defend against tampered hardware. Those limits are stated up front.
1. Who Actually Decides?
Two questions collapse into one. Who owns a device that only works while the manufacturer's server answers? Who verifies what an RPC node returns? Both ask where truth, authorization, and trusted code are decided.
The pattern is not new. At Devcon 1 in London in 2015, slock.it demonstrated a smart lock controlled by a contract: the right lived on chain, a phone carried the proof, and the lock verified it locally. No manufacturer callback was required. More than a decade later, almost every connected device still calls home.
Any device, and any application that consumes chain data, must settle three facts: what is true, who is allowed, and which code may run. In practice those facts are settled elsewhere — by a vendor backend for devices, by an RPC provider or update server for software. Systems marketed as decentralized still concentrate control at each of those points.
2. Nobody Attacked Anything
Most of the failures that matter here involve no attacker. The supplier simply ceased to exist.
| Vendor | When | What stopped working |
|---|---|---|
| VanMoof | July 2023 | The e-bike key lived in the vendor's app; repairs and spare parts dried up |
| Fisker | June 2024 | Shortly after the bankruptcy filing, the app that unlocks the doors crashed |
| Insteon | April 2022 | The servers went dark without warning and the hubs went with them |
In each case, authorization lived on infrastructure the owner did not control.
The software side looks different and fails the same way. Infura in 2020 and KelpDAO earlier this year both hinged on RPC data that was believed rather than verified. The analysis is in Four Questions to Ask Before Your RPC Fails You; the accompanying RPC trust checklist (PDF) turns the same four questions and two gaps into a two-page worksheet.
3. Give the Decision Back
The architecture has two parts. First, the facts that matter — a lock right, a balance, an approved firmware hash — live in public state: a contract for access control, the chain itself for software state. Second, the device or application that consumes those facts verifies them locally. Transport may be a phone, a gateway, an arbitrary RPC endpoint, or a USB stick. If the proof fails, the request is rejected.
Transport provides availability. Proofs provide correctness. Bytes still have to be delivered; they no longer have to be trusted.
One assumption remains. Ethereum consensus cannot be verified from an empty starting point, so a recent public checkpoint is required. From that checkpoint the client follows sync-committee updates, or verifies a ZK proof that covers a long sequence of them. The checkpoint can be cross-checked against independent sources. That is a narrower trust assumption than accepting every answer from a single server.
4. Access, Pay, Update
Colibri is built for this model. It is a stateless client: no full node, no persistent state, no background sync. A consensus proof (about 350 bytes as a ZK proof) establishes that a block is final; an execution proof establishes that a balance, storage slot, or event is present in that block. The verification path reduces to a small set of hashes and one signature check, and fits on an ESP32 with roughly 256 kB of flash and 128 kB of RAM.
Three application patterns follow.
Access. A lock receives a request with an attached proof. It verifies the block, the right in the contract, and the conditions (time window, delegation, revocation). Any failure leaves the door closed. If VanMoof-style rights had lived in a contract under owner control, insolvency of the vendor would not have revoked the ability to use the device.
Pay. A device can hold its own wallet and keys. It verifies settlement locally and enforces its own limits on amount, frequency, and purpose. Stablecoins remove exchange-rate risk for machine-to-machine and pay-per-use flows without a billing backend.
Update. A contract publishes approved firmware hashes for given hardware and version ranges. The package may arrive from any source. The device hashes it and installs only on a match.
The same three questions recur beyond locks: shared charging stations, multi-party industrial machines, robots, and agents that pay.
5. Where It Stops
Verification has hard limits. It does not restore a cloud service the vendor shut down — Humane's AI Pin and Belkin's Wemo plugs are examples. It does not supply spare parts. It does not protect against tampered hardware; the Ledger supply-chain attack made that concrete. It also says nothing about what a signer is shown on screen; that is covered in The Wallet Is the New Trust Boundary.
Technical bounds apply as well. Real-time control loops and high-frequency sensor streams do not belong on chain. The checkpoint remains an assumption. Proofs cost bandwidth: a few bytes of answer can arrive with about 28 kB of proof.
The claim is therefore narrow and operational. Truth, authorization, and trusted code should not be decided by the supplier that shipped the device or the software. Those facts belong in public state and must be checked by the consumer. Where that stops working should be stated as clearly as where it starts.
Ask the chain, not the supplier.
Watch the talk
Slides
Try Colibri — Ethereum stateless client
Verify blockchain data locally with cryptographic proofs. No trusted RPC required.