Every public blockchain turns your salary, your rent and every donation you make into a permanent record anyone can read. Nightfall hides the amounts and the addresses — and still lets you prove nobody printed a coin.
Every node re-checks that no coin exists which was never mined. The raw figures are at /network.json — height, difficulty, supply. No addresses, on that endpoint or anywhere else.
Amounts and addresses are hidden. The transaction graph is mixed inside every block, not erased. We will not claim otherwise.
v4 had a balance proof that proved nothing. v7 minted almost everything too early. We published both failures and started over.
The cryptography was written and reviewed by the same people. Passing tests is not an outside review.
Three things you would normally have to dig for. The complete list of what is missing · Why we reset
Choose by how you want to use Nightfall — and how much you want to verify yourself.
Send, receive, run a full node and mine from one app. Stores the chain locally and applies the client's validation and checkpoint rules.
Get CoreNo installation. Your keys stay in this browser; a node supplies chain data. Back up your recovery words before receiving NIGHT.
Open web walletRead how Nightfall differs from Monero and Zcash, or open the current security review. No price promises and no safety score.
Compare the coinsHidden amounts still need accountable supply. Nightfall's consensus checks a balance equation across unspent outputs and transaction kernels, alongside signatures and range proofs. Run your own node to check the chain; the website displays a node's reported result.
Sum every unspent output, subtract every transaction kernel, and the result must equal exactly the coins that were legitimately mined minus the fees that were burned — and, after the subsidy ends, not minted as extra. This invariant is one safeguard, not a substitute for correct cryptography, validation or an independent security review.
Every output carries a zero-knowledge proof that its hidden amount is a real number between zero and 2⁶⁴. Without it, a negative amount would mint value while the books still appeared to balance.
Each transaction proves knowledge of a secret with respect to a second generator. That is only possible if the amounts cancel exactly — it is the mathematical statement "I created no money".
The fee is the one public number in a transaction, deliberately. Today it is burned, and anyone can check the burn instead of taking it on faith. Once the last subsidy is paid, that same visible fee goes to the miner who found the block. Neither case mints anything.
Privacy here is not a mode you switch on. There is no transparent path to fall back to, because there is no transparent path at all.
A block does not store a list of transactions. Every payment in it is merged into one flat, sorted set of inputs and outputs, so an observer cannot tell which input paid which output. Not an optional mixer you remember to use, not a service that takes a cut — it happens to every payment, in every block, whether you asked or not.
Hand an accountant a view key and they see every amount and memo you send or receive — and nothing else. It is structurally incapable of moving a coin. Need to prove a single payment instead? A receipt opens exactly one output and leaves the rest of your wallet shut.
What lands on the chain is a Pedersen commitment — a point on an elliptic curve that mathematically binds the sender to a value while revealing nothing about it. Only you and the recipient know what moved.
Every payment generates a fresh one-time key derived from a shared secret. Two payments to the same address share no visible field — not even the sender can link them afterwards.
There is no mint authority, no blacklist, no pause switch. Not as a policy — the capability simply does not exist in the protocol, and a fair genesis with zero allocations is enforced in code.
Attach a note to a payment; only the recipient can read it. Every payload is padded to the same size, so even the length of what you wrote gives nothing away.
A transaction is handed to one random peer before the rest of the network hears it, so the node that relays it first is not obviously its origin. Tor is on by default; if it is down the node falls back to clearnet and tells you.
Nighthash-v2 is Argon2id: producing a single hash requires 32 MiB of randomly-addressed memory. Purpose-built hardware would need that much fast RAM per parallel core, which is exactly where the economics of an ASIC stop working.
There is no pool to join, no configuration file, no separate miner to install. The wallet runs a full node inside itself and uses every CPU core but one.
The wallet dials the network on startup and there is nothing to enter. It matters because two miners who never meet build two separate chains from the same genesis, and the lighter one is discarded when they finally connect. So if the wallet ever says No peers — mining solo, something is in the way — a firewall, a dead proxy, no connection. Fix that before you leave the machine running for hours.
Chain selection compares cumulative proof of work, never block count. Difficulty retargets every single block over a 90-block weighted average, so the network absorbs hashrate swings in minutes.
Block subsidies unlock after 1,440 blocks, roughly six hours. The delay protects you from reorganisations — the coins are already yours, just not spendable yet.
Every coin that will ever exist has to be mined. There was no allocation to a team, a foundation or a fund — the genesis block contains nothing, and the code refuses to start if it ever does.
6 NIGHT per block, halving every 7,500,000 blocks (~3.6 years). Half the supply in the first era, 89 million around year 23. After the subsidy ends, fees go to miners. The August 2026 chain that minted 20 NIGHT is buried — those coins are not these coins.
Ristretto throughout. Blake3 for hashing, Bulletproofs for range proofs, Schnorr for signatures, XChaCha20-Poly1305 for payloads, Argon2id for proof of work. No trusted setup, anywhere.
Workspace crates, no unsafe code in the consensus path, and a regression suite that replays the six real attacks against the previous protocol version and asserts every one of them now fails.
The Core Wallet runs a complete node inside itself. No server to trust, no third party watching your balance, nothing to configure.
Private payments, verifiable supply and explicit trust boundaries. Twenty chapters, with implementation sources and open risks.
English edition · 8 September 2026 · Software 1.0.4macOS refuses a normal double-click: right-click the app → Open → Open, once. Windows shows SmartScreen: More info → Run anyway. On a phone or tablet there is nothing to sign and nothing to install — the web wallet runs in the browser and can be added to the home screen.
Code signing certificates are issued to a company. There is no company here, which is the same reason there is no premine.
Compare the file you got against the published checksum before you run it:
Or skip the question entirely and build it yourself from source — that is the point. A one-command node install is on the build page.
The essentials before creating a wallet or sending your first payment.
Core runs on your computer with a local node and mining tools. The web wallet works on phones and desktops without an installation, but relies on a remote node for balances and chain data. Both need a safe backup. Compare the download options.
Write down the wallet's 24 recovery words and keep them offline and private. Never send them to support or enter them on another website. Browser storage can be cleared or lost; it is not a backup. On a shared or compromised device, another person or malicious software may access your keys.
A submitted payment is not confirmed until the chain includes it. Newly mined rewards also have a maturity delay. Let your wallet finish syncing, check its transaction status and avoid sending again just because a balance has not refreshed. The network page shows the node's latest reported chain state.
They were withdrawn before 1.0.4 and removed from the wallet. Nightfall has no script language, so a NIGHT lock cannot refund itself on a timer the way a Bitcoin lock can — which left a permanent-loss case no implementation could remove. Shipping that without an independent audit was not a trade worth making. No consensus rule changed and no user funds were ever at risk: the feature was blocked on mainnet in every published build.
A privacy project that hides its weaknesses is a privacy project you should not use. Here is everything currently missing, in plain language.
The previous protocol version had a balance proof that proved nothing — anyone could have minted unlimited coins. We found it, published the full analysis, threw the chain away and started over. Read the current review · v4 audit.