QMail Link Accept — Group 6, Code 87

The invited device presents the group it was invited to and the pairing code it was given, authenticated with its own coin. On success it becomes a subordinate device of that group at the lowest free slot.

LIVE FLEET-WIDE since 1 October 2026

The four device-link commands (86–89) are dispatched on every RAIDA and the inbox rewrite for linked devices is switched on. Verified against the server source and a live probe of the fleet on 6 November 2026. The link registry is local to each RAIDA: a client pairs its devices on the beacon RAIDA(s) it actually polls.

Quick reference

Command Group6 (QMail)
Command Code87 (0x57)
Server functioncmd_qmail_link_accept in cmd_qmail.c
Body layout48-byte QMail preamble + payload (9) + terminator (2) = 59 bytes
TransportUDP or TCP
EncryptionAs for any other QMail command
AuthenticationThe subordinate device’s own coin in the preamble
Success responseStatus 250, no payload

Device-link model

One user can run QMail on several devices, each holding its own identity coin, so rotating one device’s password (a POWN of that coin) never locks out the others. Devices link under an authority mailbox, which is the public address. A subordinate device’s coin is a device credential only, never a visible identity: while the rewrite is on, a subordinate’s Ping and Peek are served the authority’s inbox, and its Tell is stamped as coming from the authority (the client must already put the authority in the blob’s sender fields, or the Tell is refused with 198). Uploads are not rewritten; objects stay owned by the device coin that uploaded them.

Each group has exactly one admin, normally the authority itself. The admin is the only device that may list (88) or revoke (89). Every device authenticates each of these commands with its own coin in the preamble, exactly like any other QMail command. The registry is kept per RAIDA in that node’s directory database and is never replicated, so a client repeats the pairing on each beacon RAIDA it uses.

Housekeeping the server does on its own

A device idle for more than 24 months is unlinked. An authority idle for more than 24 months with an active subordinate passes admin to the most senior subordinate (succession). Expired invites are purged. These sweeps run at most once a day, triggered by the open DRD sync command (147). Both 24-month windows are deliberately long for the first year of use.

Request body

OffsetSizeFieldDescription
481authority_denDenomination of the group’s authority coin, as returned by Invite.
49–524authority_snSerial number of the authority coin, big-endian.
53–564pairing_codeBig-endian. The 6-digit code from Invite.
57–582Terminator3E 3E.

A device may hold open invites from several groups at once; it joins only the group it names here. The slot assigned is the lowest free one in 1–254 (slot 0 is the authority).

Status codes

CodeSymbolMeaning
250STATUS_SUCCESSAccepted.
175ERROR_BAD_PAIRING_CODENo open invite for this device in this group, the code does not match, or it expired. Ask the admin for a new invite.
176ERROR_DEVICE_LIMITThe group filled up between Invite and Accept.
173ERROR_LINK_NOT_FOUNDThe named authority has no group on this RAIDA.
40ERROR_INVALID_SN_OR_DENOMINATIONAlso returned when the caller is already an active device of another group, or is itself an authority.
16ERROR_INVALID_PACKET_LENGTHBody length or terminator wrong.
40ERROR_INVALID_SN_OR_DENOMINATIONA denomination is outside −8…+6, or the request names an impossible relationship (see each command).
8ERROR_COIN_NOT_FOUNDThe preamble coin (or, for Invite, the invitee) is not an issued coin on this RAIDA.
200ERROR_INVALID_ANThe preamble Authenticity Number does not match this RAIDA’s record for the caller’s coin.
194ERROR_FILESYSTEMThe registry database could not be read or written. Transient; retry.
254ERROR_MEMORY_ALLOCServer allocation failure.

Common mistakes

Accepting with the wrong coin

The preamble must carry the invited device’s coin, not the authority’s. The authority never accepts anything.

Reusing a code on another RAIDA

Each RAIDA issued its own code in its own Invite response. Present each RAIDA the code it issued.