Skip to content

Attach a person's name to their key (operator request directory.write; params keyId, name, salt)

POST
/v1/issuers/{id}/directory/write
curl --request POST \
--url https://api.hardstate.net/v1/issuers/example/directory/write \
--header 'Content-Type: application/json' \
--data '{ "request": { "op": "billing.checkout", "issuer": "example", "key": "example", "ts": "2026-04-15T12:00:00Z", "nonce": "example", "params": {} }, "sig": { "kind": "passkey", "authenticatorData": "example", "clientDataJSON": "example", "signature": "example" } }'

Signed by an institution admin, or a department head for their branch. The name and the 16-byte hex salt must open the key’s holder commitment, so the directory can only say what the log already commits to.

id
required
string
/^[a-z0-9][a-z0-9-]{1,62}[a-z0-9]$/
Media typeapplication/json

Not a log event: an admin’s instruction to the operator. The signed hash is sha256(“hardstate/operator/v1” ‖ JCS(request)); accepted within 5 minutes of ts, once per nonce, from a live admin key of the issuer.

object
request
required
object
op
required
Allowed values: billing.checkout billing.invoice billing.portal anchor.express
issuer
required
string
key
required

The signing admin key id

string
ts
required
string format: date-time
nonce
required

16 random bytes

string
params
object
sig
required
One of:
object
kind
required
Allowed value: passkey
authenticatorData
required
string
clientDataJSON
required
string
signature
required
string

{ keyId, code }

Missing name or malformed salt

Not an admin

The name and salt do not open the key’s holder commitment

HardState is a Zevlat Intelligence venture. © 2026 Zevlat Intelligence.