DRD Server Post — Group 16, Code 149

Quick reference

Request body

After the 16-byte challenge prefix, payload fields are:

TLV tags

Known tags are role-gated. A known tag used on the wrong role is invalid (198).

QMail discovery fields

The following implemented QMail tags extend the table above. Numeric fields use big-endian encoding; optional fields omitted from a Post retain their previous server-side value. Get replies report field presence separately from a zero value.

• 0x02 jurisdiction: also supported for QMail, 1..64 bytes.
• 0x26 listening port: 2 bytes, 1..65535.
• 0x27 access policy: 1 byte, 0 or 1.
• 0x28 upload_bps and 0x29 download_bps: 8 bytes each, bits/second, nonnegative and at most INT64_MAX.
• 0x2A key_id: 1 byte, nonzero. 0x2B node_id: 1 byte. QMail clients support node IDs 0..24.
• 0x2C framing: 1 byte. QMail clients require framing 2 and encryption_types containing the exact token 9 for Content Server sessions.
• 0x41 reputation: 1 byte, 0..100. QMail publishes its automatically tracked rolling 30-day uptime here as an owner report.
• 0x43 withdrawn: 1 byte, value 1; send as the only TLV to withdraw a QMail descriptor and set field_count to 0x8001 (withdrawal marker plus one TLV). A later regular publication makes it discoverable again.

Storage and bandwidth are owner reports, not independently verified capacity. Type 9 applies to connections to QMail Content Servers; advertising it does not add a Type-9 listener to RAIDAX. No advertisement lease is implemented.

What a RAIDA reports, and what it does not

The bandwidth tags are not interchangeable, and a RAIDA fills only one of them. 0x28 upload_bps and 0x29 download_bps are directional achieved throughput: they describe transfers a server has actually measured. Nothing on a RAIDA times a transfer, so a RAIDA never publishes 0x28 or 0x29 and a client must not expect them from one. A standalone Content Server may publish both.

0x12 network_speed_bps is the single symmetric figure a RAIDA can publish. Since 2026-09-24 a RAIDA reports the negotiated link rate of the network interface that carries its default route — and only when that interface holds the public address the node is publishing. A node behind NAT reports nothing here, because its link rate describes the local network rather than its path to the internet, and a figure that wrong is worse than an absent one. An operator who knows the real uplink may declare it in the node’s configuration, and the declaration takes precedence over the probe.

None of these figures are verified by the directory. They are the server’s own report, and the reporting node is paid for the traffic it carries, so a consumer that ranks servers by bandwidth should weight an unverified claim accordingly.

QMail server software version

Tag 0x25 is the existing four-byte unsigned big-endian version field. QMail publishes its server release date as YYYYMMDD, for example 20260922 for September 22, 2026. Zero or an absent field means unknown. This is the running Content Server executable's version, read from its validated local status, not the desktop application's version or the date of publication. A RAIDA publishes this tag too, carrying its own build date, so the field is populated for RAIDA rows as well as Content Server rows — do not assume it is Content-Server-only. Because the value identifies the software that produced a row, it also tells a reader which rules generated that row's other figures, such as the speed semantics above.

Regular publications and retries carry this value. Withdrawal remains a single 0x43 TLV with field_count=0x8001 and includes neither version nor uptime metadata. Command 150 returns the stored version using the same 0x25 tag; no new wire command or DRD database column is required. Clients should display the version as reported, without treating it as proof of supported features. Use authenticated capability negotiation to determine which operations a server actually supports.

Validation rules

• Authentication check (dn+sn+AN) runs before TLV parsing. Unknown coin returns 40; bad AN returns 200.
• field_count must match parsed TLV count exactly, or request fails as malformed (16).
• Duplicate TLV tag or TLV overrun returns 16.
• role=raida requires dn=5 plus TLVs raida_id and jurisdiction.
• Role/dn matrix: qmail allows dn 3, 4 or 5; drd/rke allow dn 4 or 5; beacon allows dn ≥ 4. Mega (dn 3, 1,000 CC) was admitted to the qmail role on 2026-09-22 so a Mega identity can host a Content Server; the other roles were unchanged. A denomination outside a role’s set is refused, and withdrawal is held to the same rule as publication.
• If both ip4 and ip6 are absent, server fills ip4 from observed peer address.
• RAIDA slot/coin binding is strict: conflicting slot claim is rejected (198), not auto-taken over.

Response body

Status codes