Do I need this? What this does and doesn't do
You must already be running a DOLI producer node — your pubkey has to be in the active set. This form only registers a friendly name; it does not create the node or the bond. See the Producer Guide if you have not set up a node yet.
The registry maps your Ed25519 pubkey to a username. You prove ownership by signing a short message with your node's signing key. The backend then, in this order:
- Checks the username is 3–32 characters drawn from
a–z 0–9 _ - .and that the signed command is no more than 5 minutes old. - Applies two rate limits — one on your IP address, one on your pubkey — and refuses a signed command it has already accepted once.
- Checks the username is not on the reserved list.
- Verifies the signature against the pubkey in the request.
- Checks that pubkey is in the active producer set, fetched from the DOLI node. A producer list too stale to trust is refused rather than guessed at.
- Checks the pubkey is not inside a 30-day post-deletion lockout.
- Writes the row, refusing it if that pubkey, or that username ignoring case, is already in the registry.
Any of those can refuse the claim, and every refusal comes back with the same body: the registry does not say which check failed, so this form cannot be used to discover which names or keys exist. When it happens the page lists the common causes.
If they all pass, the name is yours — immediately and permanently. There is no waiting period, and nothing will ask you to confirm after you submit — the acknowledgement tickbox in step 3 is the last thing between you and a permanent claim. Two signed actions can release it afterwards, and they cost very differently: rename keeps your registration and starts a 30-day rename cooldown, while delete erases the whole row and locks that public key out of registering again for 30 days. Renaming is the cheaper correction; either way the name you leave behind becomes claimable by anyone as soon as the change lands. Choose the name you want before you submit.
No address, contact detail or other personal identifier is asked for or stored. See the privacy policy for exactly what is kept and for how long.
1 Name it
2 Sign it
Available once you generate a command above.
128 characters — what the command above prints after “Signature:”. Do not paste the “Message:” line.
My wallet is somewhere else
Adjust --wallet to your producer key. If
your node runs under systemd, it is the path passed to
--producer-key. Both commands on this
page — this one and the one in step 3 — read the same
wallet, so change it in both.
3 Register it
Available once you generate a command above.
What happens after I register?
- This page shows Registered. That is the whole confirmation — nothing else is pending.
- The username is now bound to your pubkey in the registry and is
returned by
GET /api/producers/names. - The network dashboard reads that list once per page load, so your name appears next to your node the next time someone loads that page — a dashboard already open will not pick it up until it is reloaded. A node whose public key is already in the dashboard's own built-in producer list keeps that built-in name instead. The block explorer does not show it.
Wrong name? Either way the name you are using now is released for anyone else at that moment. Rename keeps your registration and starts a 30-day rename cooldown; delete erases the registration as well and stops this public key registering again for 30 days.
Already registered?
Both of these are signature-gated exactly the way this page is —
you sign a short message with doli sign on
your own machine and paste back the signature. Neither ever asks for a
private key.
- Rename your producer — change the display name attached to your key. Allowed once every 30 days, applied immediately.
- Delete your registration — GDPR Article 17 erasure of your registry record. Permanent, and the key cannot re-register for 30 days.