> For the complete documentation index, see [llms.txt](https://corpus-core.gitbook.io/iot-colibri-stateless/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://corpus-core.gitbook.io/iot-colibri-stateless/applications-and-colibri-products/colibri-products/colibri-sdk.md).

# Colibri SDK

Foundation for Trustless IoT Integration

## Scope and Design Goals

The **Colibri SDK** defines the foundational software layer for trustless IoT systems. Its scope is limited to enabling local, stateless verification of externally provided information using cryptographic proofs and deterministic protocol rules. The **SDK** is designed as an embedded verification runtime rather than a full client, backend service, or application framework.

It builds on the **colibri.stateless** infrastructure defined in the [Colibri Whitepaper](https://corpus-core.gitbook.io/whitepaper-colibri-stateless) and [Specification](https://corpus-core.gitbook.io/specification-colibri-stateless), where proof construction, witness generation, and protocol-level semantics are specified. The **SDK** encapsulates the verification-relevant components of this infrastructure and exposes them in a form suitable for embedded and resource-constrained environments.

The **SDK** follows two primary design goals: feasibility on constrained devices through bounded and predictable resource usage, and composability through minimal, orthogonal primitives. Higher-level functionality is intentionally excluded and implemented as optional products on top of the **SDK**. Integration into existing IoT and embedded **SDKs** is a core requirement, enabling seamless adoption without introducing new trust assumptions.

## Core Capabilities and Verification Model

The **Colibri SDK** exposes stateless verification as a local, deterministic capability that can be embedded directly into device logic. It validates externally provided claims against protocol-defined rules using cryptographic proofs, without relying on persistent chain state, trusted intermediaries, or continuous connectivity.

The **SDK** provides verification primitives for consensus and execution proofs. Consensus proofs establish that a referenced state root belongs to the canonical chain. Execution proofs establish that specific state elements—such as balances, storage values, events, transactions, or contract interactions—are correctly derived from that finalized state. Proofs may be provided individually or in aggregated or zk-compressed form without altering verification semantics.

Verification follows a deterministic pipeline with explicit inputs and outputs, bounded resource usage, and no background synchronization. This enables devices to make autonomous decisions based on locally verified information across online, offline, and delayed interaction scenarios.

## Integration and Constraints

The **Colibri SDK** is embedded into existing IoT and embedded software stacks at the application or firmware layer. It exposes a narrow verification interface that can be invoked by device logic to validate external claims. No assumptions are made about network topology, transport protocols, or backend availability.

Verification operates solely on provided inputs and requires no background synchronization or persistent state. This allows integration into systems with intermittent connectivity or offline operation without additional coordination mechanisms.

The **SDK** enforces explicit constraints. It does not generate proofs, manage wallets, host blockchain state, or provide cloud services. Resource usage is bounded and predictable, determined by proof verification rather than chain size or activity. These constraints ensure suitability for constrained devices and long-lived deployments while preserving the trustless verification model.