Healing Services (Group 2)

The live recovery surface for ticket issuance, ticket validation, ownership-state discovery, and repair.

Overview

Group 2 exists for recovery after RAIDA disagreement or uncertain ownership state. The active healing surface is ticket-based and discovery-oriented. Older healing notes that referenced other command numbers are not part of the live audited set.

Live commands

Code Name Purpose
40get_ticketObtain ticket material proving a coin authenticated at a given RAIDA.
50validate_ticketCheck whether ticket material is valid for the supplied context.
60findDetermine whether a RAIDA recognizes the current AN, the PAN, neither, or a mix.
61fix2Live second-generation repair path.
80fixRepair a disagreeing RAIDA using ticket-backed evidence.

40 — get_ticket

get_ticket is the ticket-issuance entry point for healing. A client authenticates against one RAIDA and receives proof that can be presented to others during repair or ownership validation workflows.

The live implementation enforces a minimum request body length of 39 bytes.

50 — validate_ticket

validate_ticket checks whether a previously issued ticket is valid for the coin and context being claimed. Use it when your application needs proof-of-authentication without exposing the full coin state again.

Request form Body size Success payload
Legacy request23 bytes5-byte response record
Type 7 request7 bytes7-byte response record

60 — find

find is the ownership-state discovery command. It helps a client decide whether a no-response or interrupted rotation left the RAIDA holding the old AN, the PAN, both across a batch, or neither.

The live implementation enforces a minimum request body length of 55 bytes.

Status Code Meaning
FIND_NEITHER208Neither AN nor PAN matched.
FIND_ALL_AN209All matches were against the current AN.
FIND_ALL_PAN210All matches were against the PAN.
FIND_MIXED211Mixed AN/PAN result set.

61 — fix2

fix2 is part of the live audited healing surface and supersedes older documentation that inserted other recovery commands between find and fix. Use it when your client targets the newer repair path.

80 — fix

fix repairs a disagreeing RAIDA using evidence gathered from the wider network, commonly ticket material plus ownership-state knowledge. It is the direct repair step after discovery.

Live surface note

get_ticket_by_sum is intentionally omitted here because it is not part of the current audited live dispatch table.