Progress
Written the way the product reports a verdict: each line says what is counted, and anything unfinished says so plainly. Nothing below is aspirational — where it claims something shipped, the release on the download page is the evidence.
Build state
Three states, and the third one is the useful one. A roadmap with no "not started" row is a brochure.
GO / HOLD / NO-GO against validated ledger state, with the deciding rule and a SHA-256 receipt attached. In every build on the download page.
Ledger sync across four public nodes, cadence measured from arrival, and the DEX-derived price used on this site's ticker.
Address, payment, order book, exposure, NFT and node checks, all on the landing page without an account.
Newsroom, mission log, progress, status and contact, rendered before they are served so the content is in the HTML rather than assembled afterwards.
Builds are reproducible from CI and hash-verified, but not yet code-signed or notarised. This is the single largest thing standing between the beta channel and a 1.0.
The verification surface exists in the product; the hosted API and webhook delivery are being built out against the institutional tier.
Stated as not started rather than left off the list. An audit that has not happened is a fact about the project, and hiding it would be the same dishonesty the product exists to argue against.
Recent movement
The desktop builds are pre-1.0 and unsigned while the release pipeline is hardened. The download section now says so on every artifact rather than only in the operator note underneath, so the channel is never read as stable by accident.
OPEN →The site now carries a live XRP newsroom, this mission log, a support console and a contact channel. Every page is rendered on the server before it is served, so the content is in the HTML a crawler receives rather than assembled afterwards in the browser.
OPEN →Sign-in and the hosted dashboard are gone. NOSHASHI runs on your machine and reads public ledger state; the website no longer asks anyone to create an account to evaluate it. Existing links redirect rather than breaking.
OPEN →Built from 01f6d043e5681cea4443a7bf58ddfa8bda82bc00 on macos-latest. Verify your download before running it: shasum -a 256 # macOS / Linux certutil -hashfile SHA256 # Windows The app also hashes its own running binary — Settings › Binary integrity — so you can confirm nothing changed between this…
RELEASE NOTES →Built from d2df012ff9397db2e77304fef90a2303b0e5bbd6 on macos-latest. Verify your download before running it: shasum -a 256 # macOS / Linux certutil -hashfile SHA256 # Windows The app also hashes its own running binary — Settings › Binary integrity — so you can confirm nothing changed between this…
RELEASE NOTES →Built from 53b0ce89fb37d4f0a26db59bbe533013f97bd404 on macos-latest. Verify your download before running it: shasum -a 256 # macOS / Linux certutil -hashfile SHA256 # Windows The app also hashes its own running binary — Settings › Binary integrity — so you can confirm nothing changed between this…
RELEASE NOTES →Built from 103e6075f6ac0554d6df9c8213e8d1b16bc35738 on macos-latest. Verify your download before running it: shasum -a 256 # macOS / Linux certutil -hashfile SHA256 # Windows The app also hashes its own running binary — Settings › Binary integrity — so you can confirm nothing changed between this…
RELEASE NOTES →What "beta" means here
The readings. The engine is deterministic, the tests cover the logic that makes claims, and every number on screen came from the ledger or is not shown at all.
Distribution. Unsigned binaries mean your operating system will warn you, and you are relying on a SHA-256 check rather than a signature. That is a real gap, not a formality.
Use it to inform a decision a person is making, verify the hash, and do not make it the sole basis of anything carrying legal consequence. That is also true at 1.0.