curl --request PUT \
--url "https://directory.example.com/personas/example.com" \
--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",
"dnssec_proof": "0x<rfc9102-authentication-chain>",
"canonical_payload": "0x<canonical-payload-from-verification>",
"signature": "<base64-ed25519-signature>"
}'
Personas
Submit a Persona registration or renewal
Sign and submit the canonical Persona payload with DNSSEC evidence prepared by a Directory
curl --request PUT \
--url "https://directory.example.com/personas/example.com" \
--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",
"dnssec_proof": "0x<rfc9102-authentication-chain>",
"canonical_payload": "0x<canonical-payload-from-verification>",
"signature": "<base64-ed25519-signature>"
}'
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 that already binds the DNSSEC evidence, operation, nonces, operator DID, constraints, and expiration. A registration payload also binds the proposed controllers and threshold. A renewal preserves the finalized controller set instead of encoding a replacement; use the controller-rotation endpoint for changes. Decode and sign the returned bytes locally. Submit the bound intent fields again so the Directory can reconstruct and compare the payload; do not alter them between verification and submission.
Persona v1 requires controller_threshold to equal 1. The controller set can contain more than one authorized verification-method ID, but each current update carries one active-controller signature.
Request
Controller set from the verified intent. Required for registration; renewal must omit it or repeat the finalized set exactly.
Exact hexadecimal RFC 9102 authentication-chain evidence returned by verification. The runtime independently verifies its signatures against active DNS root trust anchors.
Ed25519 signature over the decoded canonical payload bytes, encoded as hexadecimal or Base64.
curl --request PUT \
--url "https://directory.example.com/personas/example.com" \
--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",
"dnssec_proof": "0x<rfc9102-authentication-chain>",
"canonical_payload": "0x<canonical-payload-from-verification>",
"signature": "<base64-ed25519-signature>"
}'
Response
202 Response
{
"status": "accepted",
"persona": "example.com",
"operator_did": "did:openpayload:1111111111111111111111",
"extrinsic": "apply_persona_with_proof",
"operation": "register_persona",
"tx_hash": "<transaction-hash>"
}
operation is renew_persona. The finalized renewal can reactivate an expired or revoked Persona under its existing operator. 202 Accepted confirms chain submission, not finalization. Read the Persona until its revision, active, verified_at, and verification_expires_at reflect the finalized operation.
Submission errors
An explicit chain refusal returns422 with error: "chain_submission_rejected" and the public rejection reason in message. The transaction was not accepted; correct the intent and prepare a fresh request before retrying. Input and DNSSEC validation errors are rejected before chain submission.
A 502 chain_submission_failed can mean the submission outcome is uncertain. Resolve the Persona and check its finalized revision and operator state before deciding to retry. Do not treat a transport failure as proof that no transaction was submitted.
Straight to the point
PUT /personas/{persona}
- Prerequisite: verified DNS challenge through the same Directory deployment
- Sign: decoded
canonical_payloadreturned by verification - Challenge: single-use
- Accepted submission:
202

