DOLI — Rename Your Producer

This page never asks for your private key. You sign a short message on your own machine and paste back only the signature.

Why this matters

Your producer signing key is the same key your node signs blocks with. No website should ever ask for it — including this one. Signing is offline and read-only: it never contacts the node or the network, and needs no restart.

One rename per 30 days. A successful rename starts a 30-day cooldown on your public key. There is no undo and no override — if you pick the wrong name you keep it for a month. Read it twice before you submit. (Renaming to the name you already have is rejected as a no-op and does not consume the cooldown.)

How it works

You prove ownership of your producer key by signing a short message with it, exactly as you did when you registered. The backend then:

Verifies the signature against the pubkey in the request.
Checks the new name is free, not reserved, and not the one you already have.
Checks the 30-day cooldown has elapsed on that pubkey.
Applies the rename immediately — there is no confirmation step of any kind, and nothing is sent to you.
Releases your previous name the instant the change commits. It is not reserved for you and there is no cool-off on it: anyone can claim it immediately, including someone who wants to be mistaken for you. If the old name matters, do not free it by renaming.

Your public key and network are untouched, and so is the registration itself: renaming is not a re-registration and does not touch the 30-day post-deletion lockout. Only the display name changes.

The public /names list is rebuilt at the origin at most once every 30 seconds, and it is served with Cache-Control: public, max-age=30, so a client that caches the response can be a further 30 seconds behind that.

The network dashboard reads that list once per page load, so the new name shows up there on a later load of that page — a dashboard already open will not pick it up until someone reloads it. A node whose public key is already in the dashboard's own built-in producer list keeps that built-in name instead.

1 Name it

Public key 0 / 64

64 characters. Run doli ... info on your node and copy the value printed after “Public Key:”. Uppercase is folded to lowercase automatically.

Enter a full 64-character public key to look up your current name.

New username

3–32 characters · letters, numbers, _ . -
Stored lowercase, so Alice and alice are the same name.

Network

Only used to build the wallet path in the command below. It is set for you once your key is found.

2 Sign it

Available once you generate a command above.

3 Rename it

Available once you generate a command above.

If it is rejected

The registry answers every failure with the same {"error":"rejected"} body, on purpose — otherwise the endpoint would tell a stranger which keys and names exist. So the page cannot tell you which check failed. In practice it is one of these:

Cause	What to do
cooldown	Fewer than 30 days since your last rename. Wait it out.
name taken	Another pubkey already holds that name. Pick a different one.
reserved	Names like `admin`, `seed1`, `n1` are blacklisted.
no-op	The new name equals your current name. Nothing to change.
not registered	That pubkey has no registry row. Register first.
signature	The signature does not match the exact command in step 2. Regenerate and re-sign.
expired	More than 5 minutes passed. Regenerate and re-sign.

Rate limit: one rename request per hour per public key (and five per hour per IP address). A rejected attempt still counts, so check the command carefully before you submit rather than retrying blind.