01 / Direction
A useful network. A stronger foundation.
By September 2027, we want a small community to be able to use, operate and improve Nightfall without relying on one person for every step.
That means reliable wallets, understandable payment tools, independent node operators and critical code reviewed by people outside the project. It also means keeping the scope small enough to deliver responsibly.
02 / The starting point
Progress you can inspect.
The next year starts with working software, documented fixes and an honest list of what remains unproven.
Core Wallet 1.1.4
Faster block validation: the UTXO root keeps each output's leaf hash instead of re-hashing all of them for every block, and difficulty checks read only the blocks they use. A real 533,143-block chain is checked in 42 seconds instead of almost ten minutes, with a new checkpoint at block 530,000.
Read the release notes →Core Wallet 1.1.3
Fast start from the published chain archive, proof-of-work and UTXO-root checks on all processor cores, and a new checkpoint at block 505,000: the 505,591-block archive is checked in under half a minute on a current laptop. Plus clean shutdown, fork choice by work and persistent peer removal. Thank you @nightfall-wizard for #7, #10 and #8.
Read the release notes →Core Wallet 1.1.2
Short-page sync, per-peer fork recovery, recovery of interrupted archive appends and stricter public Light API framing. The block 500,000 consensus upgrade is unchanged. Thank you @nightfall-wizard for #79, #9, #18, #86, #87, #30 and #36.
Read the release notes →Core Wallet 1.1.1
Consensus upgrade at block 500,000: transaction binding, kernel offsets, coinbase and fee rules. Plus Nightfall Pay, My Node and the Node Kit. Required for every node, miner and pool before the activation height.
Read the release notes →Core Wallet 1.0.12
Bounded P2P block responses, stricter CLI scan pages, earlier block-size rejection and recovery-input hardening. Same chain and wallet format. Thank you @nightfall-wizard for #12, #15, #69, #71, #67 and #37.
Read the release notes →Core Wallet 1.0.11
The background wallet scan keeps going for long-running miners whose wallets pass 16 MiB, headless nodes get an offline recover-stalled-fork command, and builders can compare release binaries independently. Thank you @itsct-labs (#64), @parthod0x (#56) and @nightfall-wizard (#62).
Core Wallet 1.0.10
Linux Node Kit installers build with locked dependencies and show the exact source commit and lockfile they compiled, and an optional read-only preflight checks a server before installation. The mining-reward notice in Core is smaller and stays out of the header. Thank you @nightfall-wizard for PRs #60 and #61 and their tests.
Read the release notes →Core Wallet 1.0.9
A new logo and app icons, bounded RPC connections with reliable long-running subscriptions, locked release builds and safer Linux installer cleanup. Thank you @nightfall-wizard for PRs #51, #54, #55 and #57 and their regression tests. The offline recovery proposals remain under review.
Inspect the contributions and release →Core Wallet 1.0.7
Archive nodes no longer copy the whole chain to look at a fork they cannot adopt — the seed behind the web wallet stays fast. Every wallet, macOS included, is built with verifiable GitHub Actions provenance.
Read the release notes →Core Wallet 1.0.6
Nodes no longer mine while catching up and rejoin the network from a short fork however far behind they are. Core explains a dead branch, offers a resync that keeps the wallet, and releases payments the chain can never confirm.
Read the release notes →A wallet for the browser
An encrypted local vault, backup and recovery, payment review and a mobile interface with home-screen support. The web wallet relies on its configured node for chain data.
Open the web wallet →More regression coverage
The 1.0.5 validation records 446 regular Rust tests plus two isolated process runs, alongside browser and recovery checks. Passing tests are not an independent audit.
Inspect the validation →Independent assurance
No independent security audit has been completed. Independent operator coverage and reproducible releases still need evidence beyond project-run checks.
Read the security review →Atomic swaps were withdrawn before 1.0.0 and are not part of this roadmap. Reducing scope is a valid outcome when a feature cannot meet the required safety properties.
03 / Foundations
Before adding more, prove more.
Test the difficult days.
Long offline periods, restarts, network partitions, competing chains and backup recovery should become repeatable multi-node tests. Publish failures and fixes as well as successful runs.
Put critical assumptions under outside scrutiny.
Define a review scope covering cryptography, consensus, transaction validation and supply integrity. Confirm reviewers, funding and scope before announcing an audit date. Publish findings responsibly and track their resolution.
Reduce dependence on the creator.
Help independent operators run nodes, invite external code review and work toward builds others can reproduce and compare. Several servers operated by one person do not establish decentralization.
04 / Product directions
Small tools. Practical reasons to use them.
Nightfall Pay, the Node Kit and My Node shipped in Core 1.1.1. Their evidence of completion still has to come from real use. The other ideas remain proposals, not features available today.
Nightfall Pay
A payment request you can share as a link or QR code. Open it in Core or the web wallet, review the details and choose whether to pay.
Evidence of completionOne documented format works across both wallets, with tests for malformed requests and protection against unnecessary disclosure in URLs and logs.
Nightfall Node Kit
A documented way to install, update, diagnose and recover your own node without personal help from the founder.
Evidence of completionIndependent operators complete installation and a recovery exercise using the published guide.
My Node
Make connecting a wallet to independently operated infrastructure easier, with clear explanations of what the wallet verifies and what it trusts.
Evidence of completionUsers can configure a supported node, understand its trust model and handle an unavailable connection safely.
Backup Check
A guided, local recovery rehearsal that leaves the active wallet untouched and does not upload recovery words or private keys.
Evidence of completionUsers successfully restore a disposable test wallet and recognize an incomplete or incorrect backup.
Nightfall Checkout
A small, self-hosted invoice and payment-status tool for developers and volunteer merchants. Built on a tested payment-request format.
Before a pilotPayment reliability and security review must support the scope. Test on Devnet first; no merchant adoption is claimed.
Nightfall Lab
Focused community sessions to test upcoming changes with testcoins, reproduce bugs and help decide what is worth building.
Evidence of progressPublic test instructions, reproducible reports and links showing which findings were fixed or remain open.
05 / Bigger bets
Ambitious ideas. The same honesty.
These are the bold things we want to explore in 2027. Each one stays research until a design, tests and review support it, and any of them can be dropped if it cannot meet the safety bar.
Nightpool
Pool mining without a pool operator. A peer-to-peer share chain gives small miners steady payouts while the miners themselves still build every block. Today a single third-party pool finds more than a third of all blocks; Nightpool is our answer to that concentration.
Evidence of completionA Devnet share chain where payouts match contributed work, nobody holds miners' coins, and a miner can leave at any time without losing earned shares.
Nightfall Mobile
A native wallet for iOS and Android: biometric unlock, QR scanning and pay links, and sync that keeps working in the background, with the same encrypted local vault as the web wallet.
Evidence of completionPublic beta builds, recovery tested on real devices and a documented trust model for the node the app talks to.
Verify on your phone
A light client that checks block headers, proof of work and the supply proof itself, instead of trusting the node it is connected to.
Evidence of completionAdversarial tests in which the client rejects a fabricated header chain and an inflated supply.
Network health, live
A public page showing block times, node versions and how hashrate is spread across known pools, with a clear warning when mining becomes too concentrated.
Evidence of completionFed only by public data: no addresses, no IP-level tracking, no wallet activity.
Pay links in chat
Built on the Nightfall Pay format: a small helper for Discord and Telegram that posts a payment request for tips and community payments, without ever handing coins to a bot.
Evidence of completionThe helper never holds keys or funds; every payment is reviewed and sent from the payer's own wallet.
Private cross-chain swaps
Atomic swaps were withdrawn because a NIGHT lock could not refund itself. We will only return to swaps with Bitcoin or Monero if a design removes that permanent-loss case completely.
Before any codeA published design and an outside review showing no path in which a party can lose funds permanently.
06 / Reach
More people. The same principles.
Growth should come from people who find Nightfall useful, not from paid hype. These programs make it easier to find, understand, mine fairly and contribute.
Speak your language.
Translate the wallets and this site, starting with German, Spanish, Portuguese, French and Chinese, contributed and reviewed by native speakers.
Night Watch.
An opt-in public directory and a short recognition page for the independent node and seed operators that the Node Kit is meant to enable.
Mine fair.
Clear guides for solo mining with Core and for choosing a pool, until Nightpool can take over that job, so that hashrate stays spread across many hands.
Bounty board.
Small, clearly scoped tasks for documentation, tests, translations and reviews, funded openly by voluntary donations. The project holds no treasury and has no premine to pay from.
Night Call.
A short monthly public update: what shipped, what broke, what comes next and who helped, with a written summary for anyone who could not attend.
Access, without promises.
Many people only discover a coin once they can track it. This is the intended order; each stage starts only when the one before it holds up. As in chapter 01, nothing here is a promised listing, venue or price; listings are initiated by venues and the community. Nightfall pays no listing fees, at any stage. Regulated services in the EU are expected to stop handling privacy coins from July 2027 under the EU anti-money-laundering regulation.
- 01Started
Be easy to evaluate.
Public supply endpoints for trackers, a listing information page with specifications, risks and the supply proof, and entries in mining-pool directories such as MiningPoolStats.
CheckpointTrackers and pool directories can read supply, difficulty and pools without asking anyone.
- 02Community-initiated
A first market.
A venue or swap aggregator that already supports privacy coins, for example NonKYC.io, with clear risk notes for anyone who uses it.
CheckpointDeposits and withdrawals work against a venue-run node, and the risks are published next to the market.
- 03Then
Trackers.
CoinGecko and CoinPaprika. CoinGecko only lists a coin once it trades on a venue it already tracks.
CheckpointTracker pages use the public supply endpoints and link the supply proof.
- 04Only with real volume
Larger venues.
Venues such as MEXC or Gate, or KuCoin's community vote for proof-of-work projects, only once organic trading shows real demand.
CheckpointSustained independent volume, and a venue that accepts the privacy model as it is.
07 / Sequence, not a countdown
The path to September 2027.
Work advances when the evidence supports it. These stages describe the intended order, not fixed quarterly delivery dates.
- 01Foundation first
Make reliability measurable.
Expand recovery and multi-node testing, collect real-device feedback and prepare an independent review scope.
CheckpointDocumented test conditions, unresolved failures and a clear review brief.
- 02Then build
Make everyday actions simpler.
Develop Pay and the Node Kit, with backup rehearsals and community testing shaping the implementation. Start the Nightpool research and the network-health page alongside, because mining concentration is a risk today.
CheckpointCross-wallet test requests and independent installation reports.
- 03When ready
Try a small, voluntary pilot.
Explore Checkout only after the foundations justify it. Start with Devnet, then consider limited real-world use with clearly explained risks.
CheckpointReview of payment failures, recovery, usability and voluntary repeat use.
- 04Year-end review
Show what stands on its own.
Assess whether people can install, operate and test Nightfall without the founder intervening. Keep useful tools, revise weak ones and retire ideas that do not work.
CheckpointA public account of delivered work, independent contributions and remaining dependencies.
08 / Community
Help make the next step real.
You do not need to hold coins to contribute. A careful bug report, an independent node or a clear explanation can move the project forward.
Try the awkward cases.
Test a restart, a long catch-up or recovery with a disposable Devnet wallet. Report the version, steps and result. Never include recovery words, private keys or RPC credentials.
Bring an independent perspective.
Operate a node, review a change, improve setup instructions or compare a build. Share what worked and where you still needed help.
Alongside the monthly Night Call, we aim to share focused test invitations and an open record of delivered, proposed and unresolved work. Participation should be voluntary; progress should be measured without tracking personal wallet activity.
Found a security vulnerability? Use the private reporting instructions instead of a public issue.