curl --request PUT \
--url "https://directory.example.com/personas/example.com/operator" \
--header "Content-Type: application/json" \
--data '{
"action": "transfer_persona",
"persona": "example.com",
"current_operator_did": "did:openpayload:1111111111111111111111",
"new_operator_did": "did:openpayload:2222222222222222222222",
"new_controller_keys": [
"did:openpayload:2222222222222222222222#keys-1"
],
"new_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,
"new_operator_signer_key_id": "did:openpayload:2222222222222222222222#keys-1",
"nonce": "<current-operator-nonce>",
"valid_until": "<epoch-milliseconds>",
"signer_key_id": "did:openpayload:1111111111111111111111#keys-1",
"dnssec_proof": "0x<rfc9102-authentication-chain>",
"new_operator_signature": "<base64-new-operator-signature>",
"canonical_payload": "0x<current-controller-authorization-payload>",
"signature": "<base64-current-controller-signature>"
}'
Personas
Transfer a Persona operator
Submit the DNSSEC-verified, two-party Persona transfer
curl --request PUT \
--url "https://directory.example.com/personas/example.com/operator" \
--header "Content-Type: application/json" \
--data '{
"action": "transfer_persona",
"persona": "example.com",
"current_operator_did": "did:openpayload:1111111111111111111111",
"new_operator_did": "did:openpayload:2222222222222222222222",
"new_controller_keys": [
"did:openpayload:2222222222222222222222#keys-1"
],
"new_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,
"new_operator_signer_key_id": "did:openpayload:2222222222222222222222#keys-1",
"nonce": "<current-operator-nonce>",
"valid_until": "<epoch-milliseconds>",
"signer_key_id": "did:openpayload:1111111111111111111111#keys-1",
"dnssec_proof": "0x<rfc9102-authentication-chain>",
"new_operator_signature": "<base64-new-operator-signature>",
"canonical_payload": "0x<current-controller-authorization-payload>",
"signature": "<base64-current-controller-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.
acceptance_payload may be included but is not required at this step.
Request
Include the complete verified transfer intent, including the required echoedverification_expires_at, plus dnssec_proof, new_operator_signature, and these fields:
curl --request PUT \
--url "https://directory.example.com/personas/example.com/operator" \
--header "Content-Type: application/json" \
--data '{
"action": "transfer_persona",
"persona": "example.com",
"current_operator_did": "did:openpayload:1111111111111111111111",
"new_operator_did": "did:openpayload:2222222222222222222222",
"new_controller_keys": [
"did:openpayload:2222222222222222222222#keys-1"
],
"new_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,
"new_operator_signer_key_id": "did:openpayload:2222222222222222222222#keys-1",
"nonce": "<current-operator-nonce>",
"valid_until": "<epoch-milliseconds>",
"signer_key_id": "did:openpayload:1111111111111111111111#keys-1",
"dnssec_proof": "0x<rfc9102-authentication-chain>",
"new_operator_signature": "<base64-new-operator-signature>",
"canonical_payload": "0x<current-controller-authorization-payload>",
"signature": "<base64-current-controller-signature>"
}'
Response
202 Response
{
"status": "accepted",
"persona": "example.com",
"current_operator_did": "did:openpayload:1111111111111111111111",
"new_operator_did": "did:openpayload:2222222222222222222222",
"extrinsic": "apply_persona_with_proof",
"operation": "transfer_persona",
"tx_hash": "<transaction-hash>"
}
202 Accepted confirms submission, not finalization. Read the Persona until the new operator_did, controller set, DNS timestamps, constraints, and revision are finalized.
Transfer clears the previous Persona policy. Publish a new Persona policy under the new controller if one is required. If delivery_constraints was omitted from the transfer intent, the Persona has no Persona-specific constraints and delivery falls through to the remaining effective constraints.
Straight to the point
PUT /personas/{persona}/operator
- Requires fresh DNS verification, new-operator acceptance, and current-controller authorization
- Consumes the transfer challenge on accepted submission
- Replaces the operator and controller set
- Clears the previous Persona policy

