VOID

$KNX Development Recap: Expanding the Offline Stack Our first live build of offline transfers went live last week on Android. We’ve now moved beyond validating the core offline architecture and are focused on strengthening its reliability, stability, and real-world performance. Offline transfers are working end-to-end — two devices in full airplane mode can send, receive, validate, and acknowledge KNX notes with full lineage intact. That part is done. Now the work is around stabilizing it, improving Bluetooth reliability, reducing payload size, and tightening duplicate detection so it doesn’t break under edge cases. On the app side, we’ve started working on the iOS version to match what we have on Android, adapting the same offline stack within iOS constraints. Android helped us move fast with distribution, but iOS forces us to be tighter on how we implement the native layers, especially around Bluetooth and background handling. We’re also building local wallet scoring heuristics. Since there’s no global state during a transfer, the receiver needs a way to judge what they’re receiving in real time. This runs fully on-device, looking at reconciliation history, transfer patterns, and lineage depth and helps decide whether to accept instantly or verify later. This layer matters because offline transfers aren’t just about moving value, they’re about knowing when to trust it without relying on the network. Stay tuned for more updates.