Authentication Services Overview (Group 1)
The live batch-authentication surface for checking and, when requested, rotating coin authenticity numbers.
Overview
Group 1 covers the live authentication commands. These are the commands clients use to verify ownership against RAIDA servers and, in the pown variants, rotate ownership secrets as part of successful validation.
Per-command wire formats live on dedicated pages linked from the sidebar: 10 detect, 11 detect_sum, 20 pown, and 21 pown_sum. Only these four codes are part of the active audited authentication set.
Key terms
| Term | Meaning |
|---|---|
| AN | Authenticity number currently recognized by a RAIDA for a coin. |
| PAN | Proposed new authenticity number supplied by the client. |
| POWN | Password-own flow that validates a coin and rotates AN to PAN on success. |
| Mixed | Status 243. Some items passed and some failed, or the batch needs body-level inspection. |
Response pattern
All four commands share the same outcome pattern: status 241 means every item in the batch passed, 242 means every item failed, and 243 (mixed) means the server returned a per-item bitfield in the response body that the client must parse to learn which items passed and which failed.
Universal preamble (48 bytes)
Modern Authentication requests (detect, pown) start their bodies with a 48-byte authenticated preamble. This structure identifies the coin being used for the operation and provides replay protection.