# Introduction
### TL;DR * Most IoT systems rely on centralized cloud trust, creating systemic security, availability, and vendor-dependency risks. * Stateless, proof-based verification allows devices to validate correctness locally without trusting intermediaries or maintaining blockchain state. * colibri applies this model to IoT, enabling trustless interaction under constrained resources and intermittent connectivity. * Devices can autonomously verify payments, access rights, and updates using cryptographic proofs rather than backend services. * Transport channels and distributors are removed from the trust boundary; correctness is enforced locally. * This shifts IoT architecture from cloud-controlled endpoints to autonomous, fully verifying devices, enabling new classes of secure and long-lived IoT systems. ### Abstract *Current IoT architectures are dominated by centralized trust models in which security, authorization, updates, and payments are delegated to cloud-controlled backends and proprietary services. While operationally convenient, these assumptions introduce structural risks that scale with device count, autonomy, and lifetime. Devices remain unable to independently verify correctness, making large deployments fragile, vendor-dependent, and difficult to operate securely over long time horizons.* *Stateless, proof-based verification provides a fundamentally different foundation. By enabling devices to locally verify consensus results, execution state, authorization rules, and update integrity, trust is shifted from intermediaries to cryptographic proofs and protocol-defined rules. Transport mechanisms and data sources are removed from the trust boundary, allowing devices to operate securely under intermittent connectivity and heterogeneous network conditions.* ***Colibri** applies this model to IoT environments through a stateless client architecture and an open verification layer optimized for constrained devices. Building on this foundation, domain-specific components demonstrate how payments, access control, and device updates can be implemented without reintroducing centralized trust dependencies. These components are illustrative rather than exhaustive; the underlying verification model generalizes to additional application domains.* *The result is an architectural shift in which IoT devices act as autonomous, fully verifying participants with bounded risk and long-term operability. Rather than optimizing cloud-centric control, colibri enables entire classes of IoT systems that are more secure, more resilient, and more economically and operationally sustainable than existing approaches.* ## Motivation Secure operation of IoT systems requires well-defined and verifiable trust assumptions. Many existing IoT deployments achieve acceptable security levels under controlled conditions, yet they are predominantly built around centralized, cloud-based control planes. This architectural choice introduces structural dependencies on continuous connectivity, correct cloud operation, and long-term availability of the service provider. In such systems, loss of cloud availability, service discontinuation, or vendor lock-in can directly impair or disable device functionality. Verifiability is therefore treated as a primary design requirement for IoT security in environments where autonomy, resilience, and long operational lifetimes are required. Decentralization and trustless operation address these dependencies by reducing reliance on centralized intermediaries and by enabling devices to validate security-relevant properties independently. Emphasis is placed on stateless, proof-based verification mechanisms that operate on resource-constrained devices and remain viable over long operational lifetimes. The discussion is restricted to security-relevant system properties and deliberately excludes protocol-level, economic, or governance considerations. ### The Core Problem in Today’s IoT Systems Current IoT architectures are predominantly built around centralized cloud services and vendor-operated control planes. While such models can provide acceptable security under normal operating conditions, they introduce systemic risks that scale with deployment size and device lifetime. Even large and well-resourced service providers are repeatedly compromised in practice. When backend systems are breached, IoT devices that implicitly trust their designated cloud endpoints lack the ability to validate received commands, configurations, or updates. In such scenarios, devices can be repurposed at scale, for example as participants in botnets, without local detection. Vendor dependency further amplifies this risk. Many IoT devices remain operationally coupled to the cloud infrastructure of a single manufacturer. If a provider discontinues a product line, exits the market, or decommissions backend services, dependent devices frequently lose essential functionality or become entirely unusable despite being physically intact. This dependency transforms commercial or operational decisions into long-term security and availability risks. Centralized trust models also concentrate attack impact. A successful compromise of a single provider can expose large device fleets simultaneously. Transport encryption, certificate-based authentication, and similar mechanisms protect communication channels but do not mitigate the consequences of a trusted endpoint behaving maliciously or being compromised. Without local verification of security-relevant state and commands, devices remain unable to distinguish legitimate operation from coordinated abuse. ### Verifiability as a Fundamental Security Requirement IoT security must be grounded in cryptographic verification rather than implicit trust relationships. Security-relevant properties such as identity, authorization, configuration state, and permitted actions must be verifiable by the device itself. Verification that depends on trusted intermediaries, external control planes, or delegated decision-making reintroduces single points of failure and undermines resilience. Local verifiability requires that external claims about system state can be checked independently and deterministically. To remain valid at scale and over long operational lifetimes, this verification must rely on a globally consistent reference that is not controlled by a single operator or administrative domain. Concentration of verification authority negates trustlessness and converts verification back into an assumption of correctness. Decentralization is therefore an essential property of verifiable IoT security. It ensures that no single infrastructure provider, vendor, or service operator can unilaterally redefine valid system state. Only under these conditions can local verification remain meaningful in adversarial environments and across heterogeneous, long-living IoT deployments. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://corpus-core.gitbook.io/iot-colibri-stateless/introduction.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.