PROTOCOL NOTES / 02
Invitations & membership
From an out-of-band invitation to a fixed, approved group.
Android and iOS software implemented · Apple Wi-Fi Aware, Bluetooth LE and mixing tested on hosts and emulators only · Physical qualification pending
An invitation is the first trust boundary
A new ride receives a random ride ID and admission token. The organizer’s persistent Ed25519 identity anchors the invitation. The native QR/paste flow validates the format version (3), key-derived organizer identity, field sizes, and token before entering discovery. An invitation of an older format tells the rider to update every phone and create a new ride. The token never belongs in a screenshot, log, or public example taken from a real ride.
The invitation is an out-of-band trust anchor, not a separately signed organizer object. Possessing it does not grant membership: a candidate still needs organizer approval.
Approval turns a candidate into a member
The organizer assigns stable roster indexes from 0 to 11, with itself at index 0. Signed, increasing roster versions distribute membership. An unassigned index of 255 is admission state, not permission to send voice. At most 12 participants belong to a ride; pending candidates are separately bounded.
Plan the lobby for mixed rides
Each join request carries the joiner’s static capability flags: Apple platform, Wi-Fi Aware, NAN Pairing, Bluetooth LE link and host capability, and its Bluetooth LE link limit. The organizer copies them into the member’s roster record. They plan the lobby only; live route decisions use the flags of each signed advertisement.
Apple devices open Wi-Fi Aware data paths only to paired devices, and pairing needs foreground interaction. While admission is open, the lobby recommends only the pairings connectivity needs: each Apple member with Wi-Fi Aware is paired with up to two members that can pair, Apple members first. Pairing state stays on the phone and is never sent on the wire. Bluetooth LE links need no pairing.
Before sealing, the organizer’s lobby checks a capability graph of the roster. If the roster contains Apple devices and some riders could not reach each other over any possible Wi-Fi Aware or Bluetooth LE link, or a phone limited to one Bluetooth LE link and without Wi-Fi Aware has no possible neighbor, the organizer sees a warning. The warning does not block sealing and does not model distance. These lobby rules are implemented software, tested on hosts only.
Membership is fixed before conversation
Closing admission seals the group. Each rider starts audio on their own phone. Source descriptors establish the authorized voice source, key material, clock, frame duration, and progress. Creating or joining a ride alone does not start microphone capture.
Leaving is local
An authenticated leave marks that rider’s source unavailable. It does not rewrite the sealed roster, rekey every source, or terminate all other riders’ sessions. Organizer departure after sealing is not a global authenticated stop command.
Authority: Native protocol; wire reference; scenarios 01–06, 10, 19. Public examples are synthetic. This guide is maintained against the private implementation; it does not imply access to its source.