DOLI — Delete Your Producer Registration

This is a hard delete, and it cannot be undone. Your registry row — public key, username, network, claim timestamp and the signature that proved the claim — is removed from the database outright. There is no soft-delete flag, no archive and no restore. Database backups that still hold the row are pruned on the schedule in the operator runbook, currently 30 days. We cannot promise that no copy exists anywhere: that pruning is operator state on the host, and snapshots taken by the hosting provider are outside the registry's control. What the registry itself controls is the live database, and the row leaves it the moment the delete commits.

Your public key is then locked out of the registry for 30 days. Deleting writes a cool-off marker against the pubkey, and re-registration with that same key is refused until it expires. Your name is released immediately, so someone else can claim it while you wait.

If you only want a different name, rename instead — renaming keeps your registration and your claim on the key, and starts a 30-day rename cooldown rather than a 30-day registry lockout.

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.

What is and is not deleted

Data	After deletion
Public key, username, network, claim timestamp, signature, and the four internal bookkeeping timestamps (privacy policy §1)	Erased from the database — every column of the row, not a subset
Public entry on the network dashboard	The row leaves the database at once. The public `/names` list is rebuilt at the origin at most once every 30 seconds and is served with `Cache-Control: public, max-age=30`, so a cached copy can outlive the row. The dashboard reads that list once per page load, so the entry stops appearing on a later load of that page — a dashboard already open keeps showing the old name until someone reloads it. A node in the dashboard's own built-in producer list keeps that built-in name; this delete does not touch it.
Cool-off marker (public key and two timestamps, nothing else)	Kept 30 days, then auto-deleted
Your node, bond and block production	Untouched. This is a name registry only.

Deletion does not affect your producer node in any way. You keep producing blocks; the dashboard just shows your raw pubkey instead of a name. See the privacy policy for the full retention story.

1 Identify 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 see which registration will be erased.

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 Erase it

Available once you generate a command above.

Signature 0 / 128

128 characters. The command above prints it after “Signature:”. Do not paste the “Message:” line.

Type DELETE to confirm

In capitals. This is the last stop before the record is gone.

If it is rejected

The registry answers every failure with the same {"error":"rejected"} body, on purpose — a distinct "no such producer" would let a stranger test which keys are registered. So the page cannot tell you which check failed. In practice it is one of these:

Cause	What to do
not registered	That pubkey has no registry row — possibly already deleted.
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	Three delete requests per hour per public key. Wait an hour.

If you have lost your signing key

There is no recourse, and we will not pretend otherwise. Every route on this page is proved by a signature from your producer key, and the registry holds nothing else that could identify you — no email address, no account, no recovery contact. So if the key is gone we cannot verify that a record is yours, and we will not hand a name to whoever asks for it first.

Concretely: your row stays as it is. The name stays attached to that public key until a signed DELETE arrives, and nobody without the key can produce one. You may still write to privacy@doli.network — we will do what we can, and we would rather hear about it — but treat that as a conversation, not a deletion route. The privacy policy says the same thing in §5.

Advanced: the same request from a terminal. The page is a convenience wrapper; the endpoint is plain HTTP.

$ curl -X DELETE https://doli.network/api/producers/<pubkey> \
     -H 'Content-Type: application/json' \
     -d '{"timestamp":1786097931,"signature":"<128-hex>"}'
# 204 No Content on success; 403 with {"error":"rejected"} otherwise