Status & mission log
The board reports the systems NOSHASHI actually operates. The log below it carries every release, maintenance window and incident. A release only appears once CI has produced an artifact, so the log is a record of builds rather than a list of announcements.
The desktop application reads public XRPL nodes directly from your machine. Nothing on this board can stop it working — an outage here affects this website only.
Mission log
Repository notices merged with the GitHub releases feed.
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 →Built from 2d62cde0a026590261d4b1e041a869b7827401df 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 18c67cd65c5422980b46b4b7a027dcbec3a05daf on ubuntu-22.04. 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 →When support asks to look, the app asks you on whatever screen you are on: 4, 24 or 72 hours, and whether fixes may run without asking. Support sees a read-only snapshot of one computer (version, ledger connection, clock, sign-in, plan, settings health, recent errors; never keys or addresses) and…
OPEN →Built from 3e94236fdf2322e6015ba6181a5c090d06057db8 on ubuntu-22.04. 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 →Issuer screens no longer fail on large issuers such as Bitstamp: when a public server cannot return the total supply in time, the survey shows the holders it read and says so. The welcome screen and Overview open with three live cards, and the website homepage goes from 23 sections to 8.
OPEN →A free page that reads the Bitstamp, GateHub, RLUSD and SOLO books from validated ledgers and shows how much of the advertised depth is actually funded, today and at each of the last seven daily closes. Nothing is stored; every day is re-read at the ledger index shown.
OPEN →One page with the XRP Ledger problems the product addresses, the plans and prices checkout charges, every screen and paid feature in the build, and what is not built yet. A test keeps it in step with the app and the billing catalogue.
OPEN →Holdings, reserves and who can move each wallet at a period end, and how much of the holding funded dollar offers could absorb. Read from validated ledgers with a SHA-256 digest; prints to PDF.
OPEN →Enterprise and Strategic are priced by the year; the uptime SLA, single sign-on and dedicated environments are marked coming soon. The website runs no inline script. An internal security assessment ran on 30 September, and SOC 2 readiness documents and contract templates were added.
OPEN →Every permissioned domain and credential on mainnet, read by a sweep of the ledger; admission checks with SHA-256 records; audit trails screened against OFAC and the scam registry with a signed manifest. Text is larger, scaling fills the window, and 2FA sign-in is fixed.
OPEN →An emergency kit for drained accounts, a reviewed scam registry and phishing check, withdrawal screening, and Customer Asset Protection: proof from the XRP Ledger that customer XRP is backed and yours is counted. Verification, not insurance.
OPEN →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 →GET UPDATES
New releases, new free checks, and real risks we find on the XRP Ledger. Only when there is news. One click to leave.
If something here is wrong, or a build does not do what this site says it does, the contact form reaches the people who wrote it. Vulnerabilities go to security@noshashi.app first.
Releases arrive from the GitHub Releases API. Maintenance and incidents are committed to
site/data/updates.json and reviewed like any other change. Neither can be
posted without leaving a trace in the repository.