libdaas is the native DaaS-IoT core. It implements the node lifecycle, the DME protocol, DDO exchange, drivers, network formation, routing, and dATS temporal consensus. This history covers only the evolution of the core.
The 0.20 line consolidated the native API and portability. Version 0.21 introduced autonomous network formation, strengthened the protocol and synchronization, and made streams, queues, and policies configurable. Version 0.22.0 adds explicit topology awareness, automatic routing, and node-capability declaration to the core.
0.22.0
Version 0.22.0 brings discovery, join, and routing into the same operational API. A node can detect available networks, join the selected segment, and obtain from the core the information required to communicate without manually building every mapping.
The topology can now be queried at two levels: the view of detected networks and the list of known nodes or mappings. Discovery can be restricted to a specific SID, while the networkDiscovered event delivers DIN, SID, and link together, avoiding the need to reconstruct network context from the detected node alone.
Routing introduces:
- DIN lookup with timeout and TTL;
- an explicit error when no route exists;
- auto-routing activation when a direct send fails;
- configurable timeout, TTL, and packet-state queue;
- distinct states for sent, delegated, queued, or failed packets.
The release also adds a capability registry. A node can declare storage or compute features, inspect those exposed by a peer, and locate a participant by capability rather than only by DIN. Feature requests use a typed action and a compact parameter space, keeping the mechanism independent of the application service that uses it.
The link matrix distinguishes BLE from legacy adapters and includes IPv4, LoRa, MQTT5, UART, Zigbee, and raw transports. The final line also includes stability fixes for ESP32 Xtensa, reconnection on OpenWrt, and memory management on Raspberry Pi ARMv7.
Core builds in this line: Android ARM64, ESP32 Xtensa, Linux x86_64, Raspberry Pi ARMv7 and AArch64, Windows x86/x64 MSVC; the RC phase also includes macOS ARM64 and universal.
0.22.0 RC
The release candidate stabilizes the new 0.22.0 surface on ARM platforms. Network structures, mapping lists, the feature registry, and routing options are already present in their final form. BLE integration on Android targets is also consolidated during this phase.
Core builds: Android ARM64, macOS ARM64 and universal, Raspberry Pi ARMv7 and AArch64.
0.22.0 WIP
The WIP is the first complete materialization of the 0.22.0 line. It introduces join, SID-filtered discovery, topology inspection, feature-based location, and auto-routing options. This is the point at which the core moves from a network formed primarily through mappings to a network capable of discovering, selecting, and maintaining its own paths.
Core builds: Android ARM64, ESP32 Xtensa, Linux x86_64, Raspberry Pi ARMv7 and AArch64, Windows x86/x64 MSVC.
0.21.7
Version 0.21.7 completes consolidation of the 0.21 series. Node state is represented by node_info_t, a consistent structure used both for local state and for remote status, fetch, lock, and synchronization responses. The release also exposes explicit network creation.
BLE receives a link identifier distinct from the preexisting Bluetooth identifier. Core options now cover DDO RX and TX queue sizes, the real-time buffer, and the maximum retry count. A dedicated error distinguishes an active timeout from final error conditions.
Operationally, the release improves C++ stability and corrects timeout handling on slow connections.
Core builds: Android ARM64, ESP32 RISC-V, Raspberry Pi ARMv7.
0.21.6
Version 0.21.6 makes explicit the policies through which a node accepts traffic. The core can reject every request, accept only mapped peers, or extend trust to nodes on the same network, nodes reached through routing, or all participants. The dedicated type removes the use of undocumented numeric values and makes policy part of node configuration.
Discovery can target a specific SID. setOptions centralizes configuration of DDO and real-time buffers, while errorToString makes core errors easier to diagnose. The link matrix is extended with LoRa and Zigbee.
Core builds: Android ARM64/ARMv7/x86_64, ESP32 RISC-V and Xtensa, Linux x86_64, macOS universal, OpenWrt ar71xx, Windows x86/x64 MSVC and x64 MinGW.
0.21.5
Version 0.21.5 redesigns stream transfer. Open, data, and close are distinct events; the application can size the receive queue and apply timeout and retries to each send. Reception returns a buffer sized by the core, eliminating the need to predict frame size.
Statistics separate item count from byte occupancy for RX and TX queues. ERROR_TX_QUEUE_FULL makes it possible to distinguish queue saturation from a channel error or unknown destination.
use, send, and receive: code compiled against the previous series must be adapted, not merely relinked.Core builds: Android ARM64/ARMv7/x86_64, ESP32 RISC-V and Xtensa.
0.21.4
Version 0.21.4 preserves the public surface of the previous release candidate and brings it to a targeted set of platforms. It is a consolidation release: it does not introduce a new application model, but establishes the protocol and discovery foundation on which the configurable streams of 0.21.5 are built.
Core builds: ESP32 Xtensa, macOS x86_64/ARM64, OpenWrt ar71xx, Windows x64 MSVC.
0.21.3 RC
The second release candidate preserves the API and wire protocol of 0.21.2. The main work concerns core portability: OpenWrt ar71xx, Raspberry Pi AArch64, and the Windows x86 and x64 variants join the matrix alongside the existing Android, ESP32, and Linux targets.
The stable interface across two consecutive RCs makes it possible to validate the same discovery, dATS, and DDO behavior on very different architectures without introducing another application migration.
Core builds: Android ARM64/ARMv7/x86_64, ESP32 RISC-V and Xtensa, Linux x86_64, OpenWrt ar71xx, Raspberry Pi AArch64, Windows x86/x64 MSVC and MinGW.
0.21.2 RC
Version 0.21.2 is the most significant protocol change in the 0.21 series. The wire protocol and synchronization model are not compatible with previous releases; persisted configurations must also be regenerated because DIN handling changes.
Discovery supports four operational roles: disabled, send only, receive only, and bidirectional. A node can therefore search for a network without hosting its ingress point, expose an ingress point without emitting beacons, or perform both functions. If SID and DIN are not preassigned, the core can acquire the segment through discovery and produce the identity required for connection.
dATS is integrated into network formation. Before bidirectional communication begins, the new peer completes synchronization with the segment. Time-reference selection no longer depends on startup order: the node receiving discovery controls network entry, while a node joining an existing segment follows the reference already in use. Separate decoding of header and payload also makes it possible to capture arrival time before full message processing, reducing the error introduced by payload size.
The DME protocol moves to a variable-size structure and validates the header first. An invalid frame is discarded without decoding the payload, reducing processing and memory usage for malformed traffic. DDOs may have an empty payload, and the core takes control of the origin and timestamp fields. Send policies can skip a failed DDO, retry it, or apply exponential backoff.
Driver management detects link loss and can try alternative known channels. ACK metrics feed the evaluation of channel latency and reliability. Critical networking and synchronization operations are protected by rollback to the previous valid state.
Core builds: Android ARM64/ARMv7/x86_64, ESP32 RISC-V and Xtensa, Linux x86_64, Windows x64 MSVC and MinGW.
0.21.1 canary
The canary release changes discovery activation from a Boolean switch to a four-state machine. It also introduces a specific error for requests blocked by a strict policy and internal opcodes for acknowledgments and resynchronization.
This release validates the new distributed behavior: discovery and policies are exercised on Android, ESP32, Linux, macOS, Raspberry Pi, and Windows before the protocol break formalized by the following RC.
Core builds: Android ARM64/ARMv7/x86_64, ESP32 RISC-V and Xtensa, Linux x86_64, macOS, Raspberry Pi, Windows x64 MSVC and MinGW.
0.21.0 beta
The first public beta introduces autonomous network formation into the libdaas surface. The core can perform discovery over all links or through a specific driver and reports node detection and successful segment connection as separate events.
locate receives a configurable timeout; the core exposes the count of routed DMEs and distinguishes disabled discovery from other error conditions. Callbacks lose the Event suffix and adopt consistent names, a change that requires updating IDaasApiEvent implementations originating from 0.20.1.
The beta also adds policy enforcement for incoming requests and standardizes the names of the Frisbee and status diagnostic APIs.
Core builds: Android ARM64/ARMv7/x86_64, ESP32 RISC-V and Xtensa, Linux x86_64, macOS, Raspberry Pi ARMv6/ARMv7/ARMv8, Windows x64 MSVC and MinGW.
0.20.1
Version 0.20.1 preserves the 0.20.0 API and adds the raw link, useful for drivers that transport DaaS frames without a predefined channel protocol. The release primarily expands core portability, with separate builds for Android ABIs, ESP32 families, Raspberry Pi generations, and Windows toolchains.
Core builds: Android ARM64/ARMv7/x86_64, ESP32 RISC-V and Xtensa, Linux x86_64, macOS, Raspberry Pi ARMv6/ARMv7/ARMv8, Windows x64 MSVC and MinGW.
0.20.0
Version 0.20.0 defines the foundation of the modern libdaas API. In addition to node initialization, execution, and shutdown, the core exposes drivers, mappings, local and remote state, DDOs, typesets, streams, dATS synchronization, statistics, and Frisbee diagnostics.
Node configuration can be serialized through a storage interface supplied by the application. Both execution modes are already available: a core-managed thread or cyclic progression, suitable for real-time loops. Stateless DDO operations and stream sessions share identities, mappings, and drivers while retaining separate queues and delivery modes.
The first packages in this line use 0.2.0 in the artifact name; in the core history, they are identified as 0.20.0.
Core builds: ESP32, Linux x86_64, macOS x86_64/ARM, Raspberry Pi ARM, Windows x64 MSVC and MinGW.
Compatibility between release lines
| Upgrade | Required action |
|---|---|
| 0.20.1 → 0.21.0 | Rename the IDaasApiEvent callbacks and handle discovery events. |
| 0.21.1 → 0.21.2 | Upgrade all nodes together; regenerate persisted configurations; adopt typed DDO and discovery policies. |
| 0.21.4 → 0.21.5 | Adapt stream signatures and received-buffer handling. |
| 0.21.5 → 0.21.6 | Verify the order of retry and timeout parameters; replace numeric trust levels with the typed policy. |
| 0.21.6 → 0.21.7 | Migrate from nodestate_t to node_info_t and distinguish BLE from the previous Bluetooth link. |
| 0.21.7 → 0.22.0 | Implement networkDiscovered, update list types, and explicitly configure routing and features when used. |