curl --request POST \
--url "https://directory.example.com/personas/example.com/dns-challenges/<challenge-id>/verify" \
--header "Content-Type: application/json" \
--data '{
"action": "register_persona",
"persona": "example.com",
"operator_did": "did:openpayload:1111111111111111111111",
"controller_keys": [
"did:openpayload:1111111111111111111111#keys-1"
],
"controller_threshold": 1,
"delivery_constraints": {
"requested_cache_seconds": 86400,
"max_http_envelope_bytes": 26214400,
"max_unchunked_message_bytes": 16777216,
"max_chunk_bytes": 2097152,
"max_replicas": 2
},
"challenge_id": "<challenge-id>",
"verification_expires_at": 1796083200000,
"nonce": "<operator-nonce>",
"valid_until": "<epoch-milliseconds>",
"signer_key_id": "did:openpayload:1111111111111111111111#keys-1"
}'
Personas
Verify a Persona DNS challenge
Verify the TXT record and prepare a canonical Persona payload with DNSSEC evidence for local signing
curl --request POST \
--url "https://directory.example.com/personas/example.com/dns-challenges/<challenge-id>/verify" \
--header "Content-Type: application/json" \
--data '{
"action": "register_persona",
"persona": "example.com",
"operator_did": "did:openpayload:1111111111111111111111",
"controller_keys": [
"did:openpayload:1111111111111111111111#keys-1"
],
"controller_threshold": 1,
"delivery_constraints": {
"requested_cache_seconds": 86400,
"max_http_envelope_bytes": 26214400,
"max_unchunked_message_bytes": 16777216,
"max_chunk_bytes": 2097152,
"max_replicas": 2
},
"challenge_id": "<challenge-id>",
"verification_expires_at": 1796083200000,
"nonce": "<operator-nonce>",
"valid_until": "<epoch-milliseconds>",
"signer_key_id": "did:openpayload:1111111111111111111111#keys-1"
}'
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.
canonical_payload.
Request
Optional body copy of the canonical path Persona. When supplied, it must match after normalization.
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.Optional complete requested limits. Omit
effective_ttl_seconds. A renewal that omits this field retains the finalized Persona constraints.Operator-DID verification-method ID that will sign the returned canonical payload. It must also be an active Persona controller for renewal.
Unix-millisecond DNS-verification expiration. It must be in the future and cannot be more than 365 days away.
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.verification_expires_at or verification_days when verifying. Submission requires the returned absolute expiration.
curl --request POST \
--url "https://directory.example.com/personas/example.com/dns-challenges/<challenge-id>/verify" \
--header "Content-Type: application/json" \
--data '{
"action": "register_persona",
"persona": "example.com",
"operator_did": "did:openpayload:1111111111111111111111",
"controller_keys": [
"did:openpayload:1111111111111111111111#keys-1"
],
"controller_threshold": 1,
"delivery_constraints": {
"requested_cache_seconds": 86400,
"max_http_envelope_bytes": 26214400,
"max_unchunked_message_bytes": 16777216,
"max_chunk_bytes": 2097152,
"max_replicas": 2
},
"challenge_id": "<challenge-id>",
"verification_expires_at": 1796083200000,
"nonce": "<operator-nonce>",
"valid_until": "<epoch-milliseconds>",
"signer_key_id": "did:openpayload:1111111111111111111111#keys-1"
}'
renew_persona. Omit controllers and constraints to retain their finalized values, or repeat the existing controllers exactly. Renewal cannot rotate controllers.
Response
200 Response
{
"status": "verified",
"challenge_id": "<challenge-id>",
"persona": "example.com",
"operator_did": "did:openpayload:1111111111111111111111",
"action": "register_persona",
"challenge_nonce": "0",
"record_name": "_openpayload-persona.example.com",
"record_type": "TXT",
"record_value": "openpayload-persona-dnssec-v1=<request-bound-challenge>",
"expires_at": "2026-09-19T12:00:00Z",
"dns_proof_hash": "0x<64-hex-dns-proof-hash>",
"verification_expires_at": 1796083200000,
"operator_nonce": "0",
"canonical_payload": "0x<canonical-payload>",
"dnssec_proof": "0x<rfc9102-authentication-chain>"
}
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
POST /personas/{persona}/dns-challenges/{challenge_id}/verify
- 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

