Skip to main content
Submit the verified transfer intent with the new operator’s acceptance signature. The Directory binds that signature and the DNS attestation into the outer canonical_payload for an active current Persona controller to sign. The chain verifies the new-operator signature when the final transfer is submitted. Repeat the Persona, operators, new controller set, constraints, challenge and operator nonces, new-operator signer, and verification_expires_at from verification. Those values are bound by acceptance_payload and a mismatch is rejected. The current controller may choose a fresh active signer_key_id and future valid_until for this outer authorization; repeat those exact outer values in the final transfer request.

Request

In addition to the complete body documented by Verify a Persona transfer challenge, include these fields:
string
required
Exact value returned by transfer verification.
string
required
Directory attestor account returned by verification.
string
required
Directory DNS-attestation signature returned by verification.
string
required
Signature by new_operator_signer_key_id over the decoded acceptance_payload bytes.

Response

200 Response
Decode canonical_payload and sign those bytes with the returned current signer_key_id. The resulting signature is the signature field for the final transfer request.

Straight to the point

  • New operator signs acceptance_payload
  • Current Persona controller signs the returned canonical_payload
  • Preparing does not consume the challenge or submit the transfer