PROTOCOL NOTES / 05

Control & link health

Prove identity, authorize actions, and test the return path.

Android and iOS software implemented · Apple Wi-Fi Aware, Bluetooth LE and mixing tested on hosts and emulators only · Physical qualification pending

Transport proof comes before engine hello

TLS 1.3 uses self-signed Ed25519 certificates to prove possession; outgoing connections pin the discovered expected identity. Session tickets and caching are disabled. A length-prefixed transport greeting exchanges the transport version, link kind, media port, opposite directions, and attempt ID.

The greeting carries transport version 4 and names the link kind, aware or ble. A peer announcing any other transport version is refused, so every rider in a ride must run a compatible implementation. On Wi-Fi Aware links the media port must be nonzero; on Bluetooth LE links it is 0, because datagrams travel inside the channel. The transport direction identifies the connecting side, not the parent.

Engine hello then checks the ride, version, admission token, and membership rules. Both transport/greeting and hello have bounded establishment deadlines. A valid hello starts direct health tracking; it does not turn a standby edge into an active media path.

After hello, each side sends its signed discovery advertisement as the advert link object, and again whenever it re-signs it. The object is direct, TLS-protected and never relayed, and its key must match the TLS peer. This is how Apple devices, whose Wi-Fi Aware discovery carries no RideWeave data, learn routes.

Signatures do not replace authorization

Signed control bodies carry version, ride, source, increasing sequence, and message type. Verification must also establish whether the source may perform that action: the organizer signs rosters; admitted sources announce their streams; handoff coordination is direct and bound to the TLS peer.

Signatures cover the exact compact body serialization used by pinned nlohmann::json::dump(), not RFC 8785. A compatible implementation must match ordering, escaping, UTF-8, and numeric representation.

Measure a round trip, not just incoming traffic

EventConfigured behavior
Ping interval1 second; signed direct neighbor exchange, never flooded
Suspect3 seconds without the required round-trip evidence
Early suspect2 seconds without a matched pong once media that was flowing has stopped for 1 second
Dead6 seconds; close and repair the affected link
RecoveryTwo consecutive matched round trips; a pong consumes its ping and any older outstanding ones
Hello timeout5 seconds for an establishing protocol peer

Incoming audio is not sufficient proof that a control path works in both directions. Likewise, silence is not proof of a failed connection. Each pong must match a currently outstanding, single-use ping. Liveness timers are identical for every link kind; closing or losing a Bluetooth LE channel is a hard loss that makes the link dead at once. These values are implemented software defaults, not qualified radio thresholds.

Repair the affected scope

Failure detection and scoped repair preserve unrelated branches.
Failure detection and scoped repair preserve unrelated branches. · Open full size ↗

A failed peer does not invalidate every binding on a shared interface. Reasoned state transitions feed diagnostics while reconnection uses the current session and route generation.

Authority: Wire reference; direct link liveness. Public examples are synthetic. This guide is maintained against the private implementation; it does not imply access to its source.