QMail Link List — Group 6, Code 88

Returns the roster of a device group: every active device, a demoted former authority if there is one, and every unexpired invite. Only the group’s admin may call it.

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 Code88 (0x58)
Server functioncmd_qmail_link_list in cmd_qmail.c
Body layout48-byte QMail preamble + terminator (2) = 50 bytes, no payload
TransportUDP or TCP; a roster that does not fit one datagram answers 218
EncryptionAs for any other QMail command
AuthenticationCaller’s own coin; the caller must be the group admin
Success responseStatus 250 with count(1) + count × 12 bytes

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

The preamble followed directly by the terminator. The group listed is the one the caller administers.

Response body

OffsetSizeFieldDescription
01countNumber of 12-byte rows that follow, at most 255.
1+12 eachrowsActive devices first (by slot), then a demoted authority self-row, then open invites.

Row layout:

OffsetSizeFieldDescription
+01denSigned denomination of the device coin.
+14snSerial number, big-endian.
+51slot0 = the authority, 1–254 = subordinate slot, 0xFF = an open invite with no slot yet.
+61status1 = active, 2 = a former authority demoted by succession, 0 = an open invite.
+71is_admin1 on exactly one row: the device that may list and revoke.
+84last_used_monthBig-endian year × 12 + month of the device’s last Ping, Peek or Tell, stamped at most once a month for privacy. 0 if never seen.

Status codes

CodeSymbolMeaning
250STATUS_SUCCESSAccepted.
174ERROR_NOT_LINK_ADMINThe caller is not the admin of any group.
218ERROR_TCP_REQUIREDThe roster does not fit one UDP datagram. Retry over TCP.
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

Asking as a subordinate

A plain subordinate gets 174. Only the admin sees the roster; by default that is the authority, but an active subordinate that issued an Invite took admin when it did so.