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.
Create a DNS challenge valid for 48 hours before registering or renewing a Persona. The Directory does not create or renew a Persona until it observes the exact TXT value and the chain accepts its DNSSEC evidence. Registration first checks finalized chain state for uniqueness. An existing canonical Persona returns 409 persona_conflict; a renewal requires the currently registered operator DID.

Request

string
required
A DNS name, URL-encoded when necessary. The Directory returns its canonical lowercase ASCII IDNA form.
The name must be fully qualified and contain at least two DNS labels. URLs, paths, ports, wildcard names, IP addresses, and names whose top-level label is numeric-only are rejected.
string
required
The DID that will operate the Persona.
string
register_persona or renew_persona. Defaults to register_persona.

Response

201 Response
The response may include directory_url, the issuing Directory origin. Use that origin for verification and submission when resuming through a shared Directory hostname. Publish record_value exactly at record_name. DNS responses can be cached, so wait for propagation before submitting the Persona update.

Straight to the point

  • Does not register the Persona
  • Challenge is bound to the action, Persona, operator DID, network, and nonce
  • Challenge is single-use and expires after 48 hours at expires_at