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 on the landing page, plus the authority certificate, issuer badge and alerts, delivered-amount export, treasury report and book health. No account needed.
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 produced by CI with published checksums, but are not yet OS code-signed or notarised. Updater bundles carry separate minisign signatures. A 1.x version number does not remove the beta limitations.
Scoped API keys, the same verdicts and receipts as the console, and signed webhooks (deposit_screened, custom_alert, xrpl_event). Shipped in 1.0.13; the uptime SLA that would sit on top of it is not offered yet.
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 Ledger Desk NOSHASHI now shares a graphite and warm-paper design across the desktop app and website, with editorial typography, precise evidence tables and interactive dimensional layers. - Redesigned welcome, overview, navigation, panels, controls and status rail. - A direct settlement check…
RELEASE NOTES →Built from f8da3a146bd8c22b32d81920007c38add1b79110 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 →Press ⌘K (Ctrl+K on Windows and Linux) and type “test” for twelve real XRP Ledger accounts to try the app with: well-known issuers, a multi-signature account, an escrow wallet, an AMM pool, an unfunded address and a Testnet account. Picking one opens the screen where it shows something, already…
OPEN →NOSHASHI Academy, the free course for NOSHASHI and the XRP Ledger. These builds are not code-signed: macOS and Windows will warn about an unidentified developer.
RELEASE NOTES →NOSHASHI Academy, the free course for NOSHASHI and the XRP Ledger. These builds are not code-signed: macOS and Windows will warn about an unidentified developer.
RELEASE NOTES →Built from 35b0fa62ef4198c2cc2fe51a2dc26e82ae771ffe 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 →The receiving account and issuer fields ignore the spaces and invisible characters copying can add, and no longer get capitalised or autocorrected. A mistyped address is caught by its checksum before the ledger is read, with a plain message instead of a destination mismatch. X-addresses are…
OPEN →A new Invoice check panel on the Settlement screen reads the transaction from the XRP Ledger and answers VERIFIED, HOLD or REJECTED, with the reason. It credits only what was delivered, so a partial payment that fell short is rejected; it compares amounts exactly and reads from two independent…
OPEN →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 published SHA-256 comparison rather than OS publisher authentication. Updater signatures are a separate mechanism.
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.