Security
Check the code you run
The ZCash Name app runs in your browser. Your seed phrase, password and private key stay on your device. Below is every request the app makes, and two ways to be sure you run the published code: compare the site with GitHub, or run the app from your own copy.
On your device
What never leaves your browser
Seed phrase
Your private key is computed from it in the browser. The phrase is never sent, and the app doesn’t keep it in memory once the key is made.
Password
Encrypts and unlocks the copy of your account saved in this browser. It is never sent.
Private key
Kept in memory only while the app is unlocked, to sign your requests. Only the signatures are sent.
Saved account
Your seed phrase, encrypted with AES-GCM-256 under a key made from your password (PBKDF2-SHA-256, 600,000 rounds), plus your public key. It is stored only in this browser, next to your language choice.
Network
Every request the app makes
The app talks to two places only: zcashnames.co for its own files and registrar.zcashnames.co, the registrar’s API. No analytics, no trackers, no ads, no fonts or scripts from other sites.
| Request | What is sent | Why |
|---|---|---|
| zcashnames.co | ||
GET /… | Nothing | The site itself: pages, scripts, styles, fonts, images and translations. |
GET /version.json | Nothing | Checked at start and every 2 minutes, to offer a reload when a new version is out. |
| registrar.zcashnames.co | ||
GET /v1.0/getPaymentAddress | Nothing | The registrar’s payment address, network and how many confirmations it waits for. |
POST /v1.0/prices | Nothing | Current prices, fetched again when older than 5 minutes. |
GET /v1.0/check/<name> | The name you look up | Whether the name is free and what it costs. With an account saved, the lookup is a POST that also asks for the owner’s public key, so the app can tell if the name is yours. |
POST /v1.0/check/<name> | Transaction ID or payment memo | Follows your payment every 30 seconds until it is confirmed. The memo is the signed command that goes on-chain with the payment anyway. |
POST /v1.0/domains | Page, sorting, zone and search text | Names for sale on the marketplace. |
POST /v1.0/domains | Your public key, page and filters | The names that belong to your key. |
POST /v1.0/transactions | Your public key, page, time and signature | Your payment and refund history. The signature proves the request comes from the key’s owner and is accepted only within a minute. |
POST /v1.0/balance | Your public key | Your balance from sales and refunds. |
POST /v1.0/balance | Your public key, payout address, amount, time and signature | Withdraws your balance. The signature covers the address and the amount, so nobody can change them on the way. |
Registering, updating, selling or buying a name happens on-chain: the app builds and signs the command, and you send it with the payment from your own wallet. After that, the app only asks the registrar about its status.
What our server sees anyway
Like any website, it sees your IP address, your browser and the time of each request. It also sees the names you look up and, when you open your names, balance or history, your public key, which ties your names together. A public key can’t sign or spend anything, and it is part of every command you put on-chain anyway. To hide your IP address, use Tor or a VPN.
Browser rules
Enforced by your browser
Every page carries a Content Security Policy. The app’s policy allows scripts only from zcashnames.co (plus one small inline script, pinned by its hash) and connections only to zcashnames.co and its subdomains, *.zcashnames.co, which in practice means registrar.zcashnames.co. If any code tried to send data elsewhere, the browser would block it. The policy also names *.zcashnames.loc: that name exists only on the developer’s test machine and can’t be reached from the internet.
To see it yourself, open the app, press F12, choose the Network tab and use the app: every request goes to one of the two hosts above.
The policy arrives with the page, so a changed page could bring a looser one. That is what the next two sections are for.
Verify
Compare the site with GitHub
The code is open source under GPLv3 at github.com/ZCashNames/zcash-name-front. Each release has a tag named after its version, and the site serves the files of that tag byte for byte.
-
Get the code
You need git and Python 3. Look up the version the site runs in zcashnames.co/version.json and check out its tag, with that version in place of X.Y.Z:
git clone https://github.com/ZCashNames/zcash-name-front.git cd zcash-name-front git checkout vX.Y.Z -
Run the check
tools/verify.pydownloads every file of the site, including the exact addresses the pages load, such asjs/app.js?v=…, and compares the SHA-256 hash of each with your copy. It only sends GET requests to zcashnames.co, needs nothing but Python, and is short enough to read first.python3 tools/verify.pyIt ends with “All files match” or names every file that differs.
-
Or check one file by hand
Hash the file the site serves and your own copy. The two hashes must be equal:
curl -s https://zcashnames.co/js/app.js | sha256sum sha256sum js/app.jsOn macOS, use
shasum -a 256instead ofsha256sum. On Windows, download the file withcurl -o app.js https://zcashnames.co/js/app.jsand runcertutil -hashfile app.js SHA256. -
A public daily check
A GitHub Actions job runs the same check every day, and its logs are public: see the latest runs.
What a check proves
It proves what the server sent to the computer that ran it. A dishonest server could in theory send other files to selected visitors. If you don’t want to rely on that, run your own copy.
Run locally
Run the app from your own copy
Then your browser runs exactly the code you checked out, and our web server is out of the picture. Your copy talks to the same registrar, so you see the same names, balance and history.
-
Start a local server
In the folder you checked out above, run:
python3 tools/serve.pyIt serves the folder to your computer only (127.0.0.1, port 8080). Ctrl+C stops it.
-
Open the app
Go to http://localhost:8080/app. Your copy uses registrar.zcashnames.co, the same registrar as the site.
-
Import your account
A browser keeps saved accounts per address, so the account saved on zcashnames.co isn’t visible on localhost. Choose Log In → Import Account and enter your seed phrase. Always open the same address, or you’ll have to import it again.
Why not open app.html straight from disk? Browsers block the app’s scripts and translations on pages opened as files, so it needs a server. Any static server works, for example python3 -m http.server 8080 --bind 127.0.0.1, then open /app.html.
Libraries
Third-party code
Everything is served from zcashnames.co; nothing is loaded from other sites. The libraries are copies in js/vendor/, built for browsers by esm.sh from npm packages, and most start with a line naming the package and version.
| Library | Used for | License |
|---|---|---|
@noble/ed25519 2.0.0 | Signing your requests and commands | MIT |
@noble/hashes 1.3.3 | SHA-512 for the signatures | MIT |
@scure/bip39 1.2.1 | Creating and checking the seed phrase | MIT |
bech32 2.0.0 | Checking addresses | MIT |
| blakejs (blake2b.js) | BLAKE2b hashing for unified addresses | MIT |
| f4jumble.js | Decoding unified addresses (our own code) | GPLv3 |
EasyQRCodeJS 4.6.1 | Payment QR codes | MIT |
Tailwind CSS 3.4.19 | The app’s styles, compiled into css/tailwind.css | MIT |
| Inter | The font | SIL OFL 1.1 |
To rebuild css/tailwind.css yourself, run npm ci and then npm run build:css: you get the same file as in the repository.
Contact
Found a problem?
Please tell us privately first at info@zcashnames.co, with what you found and how to reproduce it.
How anyone can check the registry itself, independently of this website, is explained in Trust and Privacy.