Live on PIVX mainnet
PIVX Name Service maps a short, readable name onto your shielded address. The name is registered by a shielded transaction, so the record lives in the PIVX blockchain itself — and anybody can rebuild the entire registry from it and check the operator kept the rules.
Lowercase letters, digits and hyphens. That's the whole alphabet — no lookalike Unicode to hide behind.
Try it yourself
Now the part that matters. Two addresses below, either identical or differing by a single character somewhere in the middle. Take as long as you like — most people check the first four and the last four, which is eight characters out of a hundred and six.
Now the same check, with names:
Same question, answered in about a second — because you can hold the whole thing in your head. That is the entire point.
Trust model
Most name services ask you to believe a database. This one is designed so that believing is unnecessary: every command that ever changed the registry is a shielded PIVX transaction, and the key needed to read them is published.
Registering, updating, listing or buying a name is a shielded note sent to the protocol address. The amount is the payment and the encrypted memo is the signed command, in one transaction — so intent and payment can't be separated, reordered or invented after the fact.
The registrar publishes the protocol address and its viewing key. Anyone can scan the chain with it and recover every command ever issued, from genesis, in the exact order the blockchain fixed.
Feed that stream through the open-source indexer and you derive the registry state yourself, independently. Run it in one command with the published Docker image, or read the source and build your own.
The state root is anchored on-chain with a zero-knowledge proof that the transition rules were followed. If the operator ever censored a paid command, invented a transfer or reordered history, every independent indexer computes a different root and contradicts it — without permission or special access.
The property is fraud-evident, not fraud-preventing. A bad batch can reach the chain and be contradicted afterwards; nothing here can stop it being published in the first place. What the design guarantees is that it cannot be hidden — and that you never needed our cooperation to find out.
Read the full trust model →What's different
There is no waitlist, no queue, no referral ladder and no reserved block of premium names held back for insiders. The registry opened empty. Every unregistered name is available to whoever asks for it first, and "first" is decided by block height and position — not by us.
There is no expiry date in the protocol, no annual fee and no check-in window you can miss. Registration is once. A name leaves your control only when you sign a command transferring or selling it — there is no mechanism, for us or anyone, to reclaim it.
A name is bound to your Ed25519 public key, and every change is a command you sign yourself. We never hold your keys and never move a name on your behalf. Nothing in the system can be operated by us that you did not authorise.
List a name for sale at your price, unlist it, or buy one that's listed. Sale proceeds credit your balance net of a flat 5% service fee, and a bid that loses a race is returned to your balance rather than lost. Ownership changes hands as a signed, on-chain command like everything else.
.pivx, .private, .secure and
.safe. Same protocol, same pricing, same guarantees — pick the one
that reads best for you.
Change the address behind your name whenever you rotate wallets. Everyone who knows the name keeps paying the right place, and nobody has to be told. The old address simply stops being the answer.
Pricing
Shorter names cost more because there are fewer of them. Registration is a one-time payment — the second column is what it costs to later re-point the name at a different address, which you can do as often as you like.
| Name length | Register (once) | Update address |
|---|
Length counts the part before the dot. Marketplace sales carry a 5% service fee. Prices are protocol constants, identical for every zone and every registrant.
What's next
The protocol is live and finished in the sense that matters — names work, and the registry can be verified by anyone. What follows is about making them easier to use.
A block explorer shows you transactions. This one will show you names: every registration, every address change, every transfer of ownership, every listing and sale — laid out as one searchable history you can follow without running a node yourself.
The point of a name is that you never touch the address. That is only fully true once your wallet resolves names itself, so it is where the effort goes next. If you build a PIVX wallet, we would rather do this with you than around you.
Wallet teams — talk to us →Past those two, the roadmap is deliberately unwritten. Tell us what is missing, what gets in your way, or what you expected to find and did not — that is what decides the order of everything after this.
Send us a feature request →Questions
A record in the registry binding your name to your public key and a target address. Only a command signed by that key can change it. Because the record's whole history is on-chain and the viewing key is public, your claim to it is something a third party can verify without asking us.
The command history is in the PIVX blockchain and the software that interprets it is open source, so the registry can be reconstructed by anyone with a PIVX node and the published viewing key. Resolution can continue without us. That is the reason the design puts the commands on-chain rather than in a database we control.
Commands travel as shielded transactions, so amounts and addresses stay off the public ledger. A name is a way for someone to reach you, not a window into your balance or your history — closer to publishing an email address than a bank statement.
Labels are restricted to lowercase a–z, digits and hyphens, so the
homograph tricks that plague Unicode identifiers aren't possible here. A name can still
be similar to another — but it's short enough to read in full, which is not
true of the address it replaces.
Run an indexer node. It scans PIVX with the published viewing key, replays every command, computes the state root independently and compares it against the root anchored on-chain. The documentation has the address, the key and a one-command Docker image.
It is rejected rather than applied — an invalid command can never corrupt the registry, which is what the on-chain proof enforces. Where the payment can be attributed to you, it is returned to your balance; where the command is malformed past the point of identifying a payer, it cannot be. The app validates commands before you send one.
No queue, no invite, no reservation list. Whoever asks first, gets it.
Open the app