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.
After publishing the Persona TXT record, submit the intended registration or renewal. The Directory checks DNS, validates the intent against finalized state, collects the DNSSEC delegation and signatures and checks the evidence against finalized chain state, and returns the exact canonical payload your operator key must sign. This step does not register or renew the Persona. Do not sign a locally reconstructed payload; sign the decoded bytes returned in canonical_payload.

Request

string
required
Canonical Persona from the challenge.
string
required
Challenge ID returned by the challenge endpoint.
string
Optional body copy of the canonical path Persona. When supplied, it must match after normalization.
string
required
register_persona or renew_persona. It must equal the challenge action.
string
required
Operator DID bound to the challenge. It must be active in finalized chain state.
string[]
One through eight unique signing-key IDs published by operator_did. Required for registration. Renewal must omit this field or repeat the finalized set exactly.
integer
Required for registration and must equal 1. Renewal cannot change the finalized value.
object
Optional complete requested limits. Omit effective_ttl_seconds. A renewal that omits this field retains the finalized Persona constraints.
string
Optional body copy of the path challenge. When supplied, it must match.
string
required
Current operator_nonce returned with the challenge or by the Persona nonce endpoint.
string
required
Short-lived Unix-millisecond or ISO-8601 expiration for the prepared operation.
string
required
Operator-DID verification-method ID that will sign the returned canonical payload. It must also be an active Persona controller for renewal.
integer
Unix-millisecond DNS-verification expiration. It must be in the future and cannot be more than 365 days away.
integer
Alternative to an absolute expiration during preparation: 1–365 days. The Directory calculates and returns verification_expires_at using finalized chain time. Keep that returned absolute value in the signed submission.
Supply verification_expires_at or verification_days when verifying. Submission requires the returned absolute expiration.
For renewal, use renew_persona. Omit controllers and constraints to retain their finalized values, or repeat the existing controllers exactly. Renewal cannot rotate controllers.

Response

200 Response
Decode canonical_payload, sign those bytes with signer_key_id, and submit the result to PUT /personas/{persona} before the challenge and valid_until expire. Repeat the echoed verification_expires_at exactly.

Straight to the point

  • DNS TXT record must already be visible
  • Response prepares but does not submit the chain operation
  • Sign the returned canonical bytes exactly
  • DNS or DNSSEC verification failure does not consume a successful registration