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.0.5
A calmer startup, automatic recovery from ordinary chain reorganizations and protection for pending payments. Recovery does not automatically replay old sends.
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.
Pay and Node Kit are the proposed focus. The other ideas support them or depend on them. These are proposed milestones, 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 / 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.
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.
06 / 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.
We aim to share concise progress updates, 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.