Skip to main content
The DNSSEC proof model requires runtime spec 126 or newer and a matching OpenDispatch release. It is available on the alpha network, which currently runs spec 128 / transaction version 6. Domain Personas require a DNSSEC-signed TXT record and a valid delegation chain to an accepted DNS root trust anchor. Unsigned DNS and Directory attestations cannot complete this flow.
Submit the verified transfer intent with the new operator’s acceptance signature. The Directory binds that signature and the DNSSEC evidence into the outer canonical_payload for an active current Persona controller to sign. The chain verifies the new-operator signature when the final transfer is submitted. Repeat the Persona, operators, new controller set, constraints, challenge and operator nonces, new-operator signer, and verification_expires_at from verification. Those values are bound by acceptance_payload and a mismatch is rejected. The current controller may choose a fresh active signer_key_id and future valid_until for this outer authorization; repeat those exact outer values in the final transfer request.

Request

In addition to the complete body documented by Verify a Persona transfer challenge, include these fields:
string
required
Exact value returned by transfer verification.
string
required
Exact hexadecimal RFC 9102 authentication-chain evidence returned by verification. The runtime independently verifies its signatures against active DNS root trust anchors.
string
required
Signature by new_operator_signer_key_id over the decoded acceptance_payload bytes.

Response

200 Response
Decode canonical_payload and sign those bytes with the returned current signer_key_id. The resulting signature is the signature field for the final transfer request.

Straight to the point

  • New operator signs acceptance_payload
  • Current Persona controller signs the returned canonical_payload
  • Preparing does not consume the challenge or submit the transfer