Skip to main content
Prepare a single-label Persona
Use this route for a unique single-label Persona such as compliance. A name containing a dot uses the DNS challenge flow. The operator DID must be active, and every controller key must be one of its published signing keys.

Request

string
required
Single-label Persona name.
string
required
register_named_persona.
string
required
Active DID that will operate the Persona.
string[]
required
One through eight distinct signing-key IDs under the operator DID.
integer
required
Must equal 1.
string
required
Current Persona operator nonce from chain state. If the same operator already owns a Persona, its nonce response includes this shared counter. That endpoint returns 404 for a name that is not registered.
string
required
Future authorization expiration.
string
required
One of the controller keys.
You may include delivery_constraints with requested limits. Do not include the read-only effective_ttl_seconds. The 200 response returns persona, operator_did, signer_key_id, and canonical_payload as 0x-prefixed hexadecimal. Decode and sign those bytes locally, then submit the registration. Preparation checks that the Persona is not already registered; it does not reserve the name.

Straight to the point