Release evidence / v1.0.27 · beta evaluation
One build-time snapshot from GitHub release records. Source checked: 2026-11-16T13:45:17.185Z.
| Question | Recorded evidence |
|---|---|
| Latest published desktop release | v1.0.27 · 2026-11-04 UTC |
| Latest downloadable, non-prerelease build | v1.0.27 · 2026-11-04 UTC |
| GitHub non-prerelease tag | v1.0.27 · 2026-11-04 UTC. Product status remains beta; a tag does not establish production readiness. |
| Development prerelease | None present in this source reading |
| Latest macOS installer artifacts | v1.0.27 · 2026-11-04 UTC. Artifact availability only. |
| Verified macOS execution / OS signing / notarization | UNKNOWN — not established by release metadata. Updater signature files are separate. Signing scope. |
Older version numbers in the historical changelog are not current download recommendations. See available downloads. No independent security assessment or physical Monterey compatibility is established by this snapshot.
1.0.27
Academy and desktop identity
- Academy adopts the graphite Ledger Desk palette, editorial typography, ruled layouts and clearer course navigation. Academy 0.2.1 has its own Noshashi Academy wordmark and circular launcher icon.
- The main NOSHASHI desktop icon uses the circular seal with transparency outside the emblem, replacing its rounded-square backing.
- Academy screens scroll independently of the console layout, and local video captions work under the Academy's narrowly scoped content policy.
- Updated browser and Academy workstation bundles retain existing course content, saved progress and receipt formats.
The repository also contains the Payment Review browser portal, API and CLI. Production backend and billing rollout remain separate; this desktop release does not activate those services. Installer signing and notarization status are disclosed on the release page.
1.0.26
The Ledger Desk
- A new graphite and warm-paper interface shared with the website's editorial direction: Instrument Serif headings, Inter controls and IBM Plex Mono evidence, with engraved rules and restrained geometry.
- Rebuilt welcome and overview screens with a direct settlement check, selectable authority/liquidity/evidence layers, recent decisions, the instrument directory and the existing first-run guide.
- Redesigned navigation, scene headings, panels, inputs, tables, tabs, buttons and the status rail. Native window commands are unchanged.
- Command search now uses an accessible dialog with immediate input focus, contained keyboard navigation, Escape dismissal and focus restoration.
- Quoted and funded depth share a linear scale in the dimensional overview figure. Zero funded depth is rendered at zero width.
- Startup no longer reports services ONLINE on a timer. Connection state comes from the actual ledger link; the event feed is stationary.
- The public homepage adds an interactive issuer investigation, browser verification of authority fingerprints, JSON export, searchable tools, recorded desktop views and an evaluation invitation.
- Screenshot captions and image URLs follow the committed capture manifest. The Academy's bundled workstation is rebuilt from the same interface.
Policy evaluation, existing receipts, entitlements and signing restrictions retain their behavior. The app remains read-only and cannot submit a transaction.
1.0.25
Test addresses
- The command palette (⌘K, or Ctrl+K on Windows and Linux) has a new TEST ADDRESSES group: twelve real accounts to try the console with, among them the Bitstamp USD, RLUSD, SOLO and CSC issuers, a multi-signature account, a Ripple escrow wallet, an AMM pool, an address that was never funded and a Testnet account. Type "test" to find them.
- Picking one copies the address and opens the screen where it shows something, already filled in and read. Each was read from the ledger before it was added.
- Authority, Issuance and Pool governance now accept an address handed over from another screen, as Provenance and Control surface already did.
Look
- The new blue lotus mark and the navy and electric-blue palette from the website are in the app.
1.0.24
Invoice check
- The receiving account and issuer fields now ignore the spaces, line breaks and invisible characters that copying an address can add, and no longer let the system capitalise or autocorrect what you type.
- An address is checked against its checksum before the ledger is read, so a mistyped character gets a plain message (a capital R, a 0, O, I or l, the wrong length, or a failed checksum) instead of a REJECTED destination mismatch.
- An X-address is accepted and split into the account and its destination tag.
1.0.23
Invoice check
- On the Settlement screen, a new Invoice check panel answers one question: did this transaction pay this invoice? Enter the invoice (the receiving account, an optional destination tag, the asset and the amount you expect) and it reads the transaction from the XRP Ledger.
- The answer is VERIFIED, HOLD or REJECTED, with the reason in plain words. Only VERIFIED is green.
- It credits what was actually delivered, never the amount the sender asked for. A partial payment that delivered less is rejected unless you chose to accept partial payments, and then only if what arrived still covers the invoice.
- Amounts are compared exactly, to the last digit, and the same currency code from a different issuer counts as a different asset.
- By default it reads from two independent operators (XRPL Labs and Ripple). If they disagree, or the transaction is not final yet, it holds rather than guesses.
- Within a session, one transaction cannot settle two different invoices.
- Export evidence saves the record behind the answer as JSON, with a SHA-256 fingerprint anyone can recompute.
1.0.22
Support
- When NOSHASHI support asks to look at your account, the app asks you on whatever screen you are on. You choose 4, 24 or 72 hours, and whether support may apply fixes without asking each time. You can revoke it from the ticket at any time.
- Support can look at the app on one of your computers: version, ledger connection, clock, sign-in, plan, settings health, updates and recent errors. Never keys, addresses or what your settings contain.
- Fixes support sends go to one computer and run only there: switch ledger server, renew the sign-in, repair damaged settings, clear the error log, install the latest signed update, restart the window, and the existing self-check, reconnect, plan re-read and diagnostics. Each waits for your Apply unless you allowed fixes, and every one is in the ticket's log.
- Opening a ticket can share the app's recent errors (on by default, scrubbed of secrets on your computer first) and allow support a 24-hour look (off by default).
- Every screen has a guide (press ?), and there is a guided tour of the app.
1.0.21
Fixed
- Issuer screens no longer fail on large issuers such as Bitstamp. The read of an issuer's total supply can take longer than a public server allows. When it does, the survey still shows the holders it read and says the supply could not be read, instead of showing an error.
- Reads that scan every trust line now get 45 seconds instead of 12.
- The asset passport reads an issuer's holders once instead of twice at the same time, which public servers were throttling.
- When an issuer's supply cannot be read, the authority certificate says there is not enough data. It never treats it as "nothing issued".
- The Issuer screen now unlocks on the Institutional plan, as the pricing page says. It had been unlocking on Pro.
Easier to read
- The welcome screen and Overview now open with three live cards. One for each question: can it move, can you actually sell, can you prove it. The liquidity card reads a real order book and shows what is quoted against what can fill.
- Much less text on the welcome screen, Overview and getting-started guide.
- The website homepage goes from 23 sections to 8, and the pricing, Enterprise, Strategic and Trust pages are shorter.
1.0.20
Prices
- Enterprise is $120,000 a year and Strategic Infrastructure $250,000 a year. Monthly is the year divided by twelve: $10,000 and $20,833.
- The app's plan cards now show the yearly price under the monthly one.
- On the website, the Monthly / Annual prepay switch now changes every plan, including Enterprise and Strategic, and the comparison table lists the yearly price for each paid plan.
Not offered yet: marked as coming soon
- The 99.9% uptime SLA is off every plan until it is funded.
- The uptime SLA, single sign-on and dedicated environments are marked "coming soon" on the pricing page and in the app, and the help and NOSHX answers say so if asked.
Security
- The website no longer runs any inline script. Its security policy allows scripts only from the site itself, which blocks a whole class of injected-script attacks.
- The home page's "find a real partial payment" example now reads only validated ledgers, as everything else in NOSHASHI does.
- The privacy and data-processing policies now name every service that handles your data: Vercel hosts the website and its contact form, and Resend delivers contact and support email.
- An internal security assessment and penetration test ran on 30 September 2026. Every attempt to cross an organization boundary, raise a role, or edit or forge the audit log was refused. The report is in
docs/SECURITY_ASSESSMENT_2026-09.md.
For procurement
- SOC 2 readiness: policies, risk register and a control map with the remaining gaps (
docs/soc2/). No SOC 2 report is held yet. - Contract templates for institutional customers: master agreement, order form and data processing addendum, plus an SLA schedule that is not offered until it is funded (
docs/legal/). These await legal review. docs/FUNDING_NEEDS.mdlists what each "coming soon" item needs, with current prices.
1.0.19
Two new organization roles
- Reviewer: the second pair of eyes. A reviewer can activate a policy someone else wrote and decide an exception someone else raised, including asking for more evidence. They cannot draft, request or administer anything, so four-eyes holds by construction.
- Auditor: an internal read-only seat that can also read the audit trail. It changes nothing. Unlike an examiner seat, it does not expire.
- Both are enforced by the database. The app's role picker, role table and messages name them.
Sign-ins in the audit trail
- Each time a member signs in, the organization's audit trail records when, from which IP address and client, and whether a second factor was used. It is shown under the governance audit trail as SIGN-INS.
- Recording can never stop anyone signing in: if writing the record fails, the sign-in goes ahead unrecorded. Token refreshes are not counted as sign-ins. Recording began on 30 September 2026.
- The privacy policy now says this, including what stays in an organization's trail after an account is deleted.
Faster, calmer, easier to use without a mouse
- Five of the heaviest screens load when first opened, not at startup.
- The Reduced motion setting now governs every animation in the app.
- An automated accessibility check (axe-core) of 11 screens in dark and light themes now finds no violations. Fixed: tabs pointing screen readers at panels that were not there, switches with no name, and light-theme status and brand colours below WCAG AA contrast. Every control shows keyboard focus.
Public legal page
- The bulleted lists in the published policies (what an account stores, what stays on your device, and others) had been missing from the website's legal page, though present in the app. They are back, and the page is again generated from the same source as the app's.
For reviewers and operators
- New:
docs/ENTERPRISE.md(organization setup, roles, controls, integration, and what the price list names that is not built yet) anddocs/DEPLOYMENT.md(every surface, secrets by name, scheduled jobs, release checklist). - The version number is now checked in every place it is written. A release where they disagree fails its tests.
1.0.18
Getting started, on Home
- A first-run guide says what NOSHASHI is for (one ledger, three questions; it reads only and never signs) and walks four steps: choose Executive or Analyst, run a first analysis, check its evidence, set your institution's policy.
- Each step is ticked by what you actually did: a verdict recorded, a receipt re-verified, replayed or exported as a report, a policy made active. Nothing is ticked for having been shown.
- On a plan without Ledger & Policy, the evidence and policy steps say Included in Pro instead of opening a locked screen. The guide can be hidden, and goes away once every step is done.
- The Home introduction now states the product the way the website does.
Compliance API: examples that work
- The Account screen's Calling the API example, and every example in the API documentation, now use the endpoint that is live:
https://xiurbiwuwcfowqnpmwki.supabase.co/functions/v1/noshashi-verify. They previously namedapi.noshashi.app, which is not configured, so a first call copied from them could not connect.
Documentation for reviewers
- New: architecture, data model (every table, who can read it, personal data, retention), policy engine (every rule and the verdict order), evidence (the exact receipt bytes, re-verify, replay, the report), AI governance, incident response and disaster recovery.
- The nightly database backup reports a malformed connection string precisely instead of failing obscurely.
1.0.17
Website: one ledger, three questions
- The homepage now opens with "XRPL intelligence for institutional decisions." and "Analyze compliance, liquidity and control conditions from validated ledger state — then produce evidence you can verify", in all eight site languages.
- A new section right under the hero: One ledger. Three questions. Compliance (can this move?), Liquidity (can it actually exit?), Evidence (can we prove why?), and the workflow from ledger to approval.
- The README is rewritten for a first-time reader; the operator handbook moved, unchanged, to
docs/OPERATIONS.md.
Security and procurement documentation; signing ready to switch on
docs/SECURITY_THREAT_MODEL.md: assets, threat actors, trust boundaries, fourteen threat scenarios each with the code that mitigates it, residual risks and what is out of scope.docs/PROCUREMENT.md: a vendor-risk checklist, every line marked IMPLEMENTED, PARTIAL or PLANNED. Nothing planned is presented as done.docs/RELEASE_SIGNING.mdand the release workflow: macOS signing and notarisation switch on when the company's Apple credentials are added as repository secrets; until then builds are unchanged.- The desktop app can no longer toggle developer tools from the web view.
SECURITY.md's known gaps brought up to date with what has since shipped.
NOSHX: every answer lists what it rests on
- Each reading NOSHX takes carries a citation: the screen that shows it, what was asked, the validated ledger it was read at (taken from the reading itself, never from the model's text) and when. Answers end with SOURCES, each with an open link to that screen, and state which side wins: if the answer and a reading disagree, the reading and the deterministic engine are authoritative, not the assistant.
- Works for hosted and local models and for NOSHX Core.
Evidence: replay and the institutional report
- Replay (Ledger & Policy → Evidence, per verdict): re-reads the subject's account, credentials and the reserve in force at the receipt's own ledger index, re-runs the same rules, and shows rule by rule what matches and what does not, with both digests. A replay is evaluated as of the recorded time, so an unchanged record reproduces its digest exactly. The stored verdict is never changed. Where a public server no longer holds that ledger, replay says so and compares nothing.
- Export report: one HTML document per decision (prints to PDF): executive summary, subject, policy and its SHA-256, decision, key findings, every rule, ledger and source agreement, re-verification, replay, exceptions with their expiry, a reviewer block, and verification instructions that print the exact canonical bytes so the digest can be recomputed with
shasum -a 256without NOSHASHI. - Tested on Bitstamp's real account state, credentials and FeeSettings reserve (1 XRP base, 0.2 XRP per object) at ledger 107,305,907.
Liquidity: what can fill, before what is quoted
- Every exit row on the Risk screen now leads with fillable bids against quoted bids within 10% of mid, the share that is real, and the ledger it was read at. Quoted counts every resting offer at face value; fillable counts only what each offer's owner holds now (
taker_gets_funded). Exit simulation has always filled against fillable depth; now the headline says so. - Tested on a real XRP/USD.Bitstamp book at ledger 107,312,802, where one ask quotes 1,450,000.7 USD and its owner can deliver 3,370.63.
- Invented "confidence" labels (HIGH / MEDIUM) removed from exit and watch signals: they had no defined measure behind them.
1.0.16
Fixed: "too much load" errors from the public XRPL servers
- Every ledger read now goes through one pacer: at most four reads are in flight at once, and when a public server answers
slowDownortooBusy("You are placing too much load on the server") NOSHASHI waits, retries the same read, and moves to the next public server if the throttling continues. Only if that fails does it say so, in plain words, and nothing is decided on a partial read. Busy screens (Audit Trail paging, registry reads, screening batches) no longer trip the limit. - Overview no longer opens a fresh connection to every public node on each visit; one recent reading is shared.
One product, three questions: compliance, liquidity, evidence
- Decision card on Overview. The latest recorded decision (GO, HOLD, NO-GO or INSUFFICIENT DATA) with what it means, the policy or reference profile, how many rules passed, the ledger it was read at, the receipt re-verified on the spot, how many public nodes are in step right now, and the rules that decided it. No scores or confidence percentages: every line is a record or a count. With no analyses yet it says so and offers the first one.
- Executive and Analyst modes. Executive shows the eight screens that answer the three questions; Analyst shows every tool. New installs start in Executive; the switch is at the top of the sidebar and every screen stays one search away.
- Sidebar regrouped into Overview, Compliance, Liquidity, Evidence, then Issuers & Treasury, Intelligence and Public tools.
- Verdicts record their ledger index, beside the receipt rather than inside its digest, so every earlier receipt still verifies.
- Reference rule profiles. The settlement gate's six built-in profiles are named for what they are, with no invented institutions or member counts.
- The vendor's business model is off every customer path; it remains in the command palette, labelled internal.
- The tagline no longer says "autonomous": NOSHASHI analyses and proves; people decide.
- Repository: code from an earlier, never-deployed product (a FastAPI service, a Next.js site, a Swift menu-bar app) and its plans are removed.
docs/IMPLEMENTATION_PLAN.mdrecords the audit and the phases.
Compliance: sources must agree, settings explain themselves, exceptions expire
- No GO without agreement. Before a verdict is issued, every public node is asked for the ledger hash and the account's state at the same validated ledger. The new SOURCE_AGREEMENT rule, recorded in the receipt, holds the verdict (never GO) when nodes disagree, when fewer than two answer, or when the account changed after it was read. It can lower a verdict to HOLD; it never turns one into NO-GO. Offline verdicts record it as not applicable. The Decision Card shows how many nodes agreed.
- Every policy setting is a rule sheet: its value and unit, what it reads from the ledger, the exact condition that triggers it (with the configured value in it), and what that does to the verdict. Built from the same parameters the engine applies, and tested against them.
- Exceptions expire. Every approval now carries an expiry the approver chooses (1 to 365 days, 30 by default), set in the same transaction as the decision and written to its audit event. An expired approval stays on record, is shown as expired and can no longer be cited to close a case. Approvals made before this change are labelled as such; none were edited.
- Policy lifecycle in reviewers' words: Draft, In review, Approved & active (four-eyes: never by the author), Superseded.
1.0.15
Built for banks and compliance officers: readable, real, filed
- Domain Grid, on real data. Every permissioned domain (XLS-80) on mainnet, found by a server-side sweep of the whole validated ledger (about 9,600 pages of 2,048 objects, pinned to one ledger; progress is shown while it runs). Read any domain live by its ID or its owner, and check whether a counterparty would be admitted: the owner always is, anyone else must hold an accepted, unexpired credential the domain accepts. The admission record is saved with its ledger index and a SHA-256 digest. The sample domains, invented member counts and illustrative institutions are gone from this screen.
- Credential Registry. Which real domains the wallet's credentials admit it to; a counterparty's credentials, who issued them and when they lapse (flagged 30 days ahead); and an issuer register for institutions that issue credentials: issued, not accepted, expiring and expired, with CSV export. The "zero-knowledge selective disclosure" panel described something XRPL credentials do not do and is replaced with how they work.
- Audit Trail. Any account, not only the loaded wallet, 400 records at a time back through its whole history. Delivered amounts (partial payments flagged, compared exactly, not as floating point), tokens, destination tags and memos. Every counterparty is screened against the OFAC SDN list and the scam registry; a list that cannot be read is shown as not checked, never as clear. A reporting threshold flags large transfers. EXPORT EVIDENCE writes the CSV plus a manifest with its SHA-256 and ledger range.
- New public API (no account):
noshashi-ledger-registryanswers/status,/domains,/credentials?issuer=|subject=and/issuers. - Readability. No text below 10px anywhere in the app (about 1,300 labels were 7–9.5px), tighter letter-spacing on labels, and stronger contrast for secondary text in both themes.
- Accessibility text size now scales the app to fill the window on every platform. At 125% and 140% it previously shrank into the corner and was clipped on Windows, and the accessibility panel ran off the top of the screen; the panel now scrolls inside the window.
- Top bar. The search no longer slides over the connection status when the window is narrow; the bar drops its secondary readouts first and the search becomes an icon. The status bar at the bottom does the same instead of wrapping.
- Sign-in. An account with two-factor authentication was let through after the password and never asked for its code; it now always gets the code step. The form scrolls instead of losing its top at large text sizes, Escape closes it, and a successful sign-in says so once. The email confirmation link now lands on a page that says the address is confirmed and to sign in from the app, and strips the session tokens from the address bar, instead of silently opening the home page.
- Growth is removed from the app, the docs and the Learn course.
1.0.14
Customer Asset Protection and institutional security tools
- Customer Asset Protection (verification, not insurance: NOSHASHI pays no claims and no government scheme stands behind it):
- Institutional (
proof_of_reserves): name the accounts that hold your customers' XRP and publish the root of a Merkle sum tree over customer balances, built in the app from your own export. Only the root, the total and the count leave the machine. Each customer gets their own inclusion proof. The reserves are read from a validated ledger every day at 06:17 UTC and recorded as an attestation, hash-chained to the one before. - Enterprise (
customer_protection): a protection fund with a per-customer limit. Only XRP locked in escrow, or held under a signer list with the master key disabled, counts as secured. The program can have a public page at/protection/?p=<name>, where customers check their own proof and the latest digest is recomputed in their browser. - Strategic (
protection_monitoring): a signedprotection_alertwebhook when reserves fall below published liabilities or the status worsens. Every attestation also emitsprotection_attested. - Free on every plan:
- Emergency kit and drainer check. Is the account being drained now (keys changed then value out, dust spray then AccountDelete, zero-price NFT offer taken, check cashed at once)? Then the ordered unsigned transactions that save the most, optionally on tickets to sign today and keep offline. The XRP sweep leaves the kit's fees and the reserve of unused tickets behind, so it cannot fail for want of either.
- Who is this? Exchange attribution: a domain that vouches for the address, a domain it only claims, or the behaviour of a pooled service.
- Scam registry and phishing link lookups, at the public
/threatsand/phishingroutes. - Institutional (
threat_registry): file scam reports with transaction evidence. NOSHASHI staff review them, and a reviewer can never confirm a report they filed. Confirmed entries screen deposits and withdrawals. - Enterprise:
- Withdrawal screening (
withdrawal_screening) in the app and atPOST /withdrawal-screen. It flags a withdrawal that would bounce, a destination that is brand new, hours old or imitates a past one, and an OFAC listing or scam report on the destination or up to three funding hops back. - Market surveillance (
market_surveillance): re-quoted orders that never fill, concentration, and trades between accounts of one funder. - Strategic (
phishing_feed): every listed domain as an API feed. The feed reads one validated ledger a minute and keeps domains advertised in XRP dust memos. A domain is listed once it has reached five accounts. - NOSHX gains seven tools for these. Learn gains lesson 23, six questions and eight terms.
Recovery and cybersecurity analysis tools, by tier
- Free on every plan:
- Pre-sign check. Paste any transaction or signing blob and read what it really does before you sign it. It is decoded on the device. It flags new regular keys and signer lists, AccountDelete, NFTs sold for nothing, partial payments, lookalike and OFAC-listed destinations, high fees and links in memos, with a verdict: SAFE-LOOKING, CAREFUL or DO NOT SIGN.
- Recover funds. Finds matured escrows waiting to be finished, expired escrows and payment channels that return when closed, uncashed checks, and reserve locked in old trust lines, orders, NFT offers, preauthorisations and tickets. Each comes with the unsigned transaction that releases it, plus what AccountDelete would return.
- Exposure audit. The XRP Ledger's "revoke approvals": every check, NFT sell offer, payment channel, order, key and preauthorisation that lets someone else take value, each with its revoke.
- Deposit help. A "lost" deposit explained from its hash. When it reached an exchange without the right tag, it writes the letter the exchange needs, with its SHA-256.
- Domain check. Does the domain an account claims list it back in its
xrp-ledger.toml? The file is read server-side at the new publicnoshashi-xrpl-watch/domain-verifyroute. - Asset inventory. Tokens, LP shares, NFTs and open orders.
- Personal Guardian. Native takeover alerts for 3 of your own addresses while the app is open.
- Pro and above (
asset_recovery): - holdings valued in XRP at the live best bid, AMM spot price or pool share;
- recovery and exposure scans across 25 addresses at once (500 on Institutional and above, with CSV export);
- Personal Guardian on 50 addresses;
- the scam cluster mapper, which finds the accounts one operation runs by linking funders, AccountDelete sweeps, vanity endings and shared memos.
- Enterprise: cluster maps four hops and 200 accounts deep, opened as an investigation case.
- Strategic: Security Guardian watches a whole cluster server-side.
- NOSHX gains seven tools for these, and it explains a transaction pasted into a question.
Security Center: cybersecurity for XRP Ledger accounts
- Account check (free). Any address graded A to F from what the ledger shows: who can sign (master key, regular key, signer list and the fewest signers that reach quorum), recent key and settings changes, address- poisoning attempts against it, and the doors strangers use (NFT offers, checks, payment channels). The hardening plan is unsigned transactions to review and sign in your own wallet; NOSHASHI never signs.
- Safe send (free). A pasted destination checked against your own address book for lookalikes, against the OFAC list, and for a required destination tag, before you sign.
- Incident response (Pro and above). For a drained account: the key changes before the theft, the value followed hop by hop through payments and AccountDelete sweeps past the dust, what became of every account it reached, every recovery path that exists rated honestly (a validated transaction is never reversible), and a SHA-256 dossier for police, exchanges and issuers. Enterprise traces five hops and opens the dossier as an investigation case.
- Security Guardian (Strategic). A signed
security_alertwebhook within a minute of a watched account's regular key or signer list changing, its master key being disabled or re-enabled, or its deletion; and one click watches every account in a theft trail. - NOSHX answers "is my account secure?" and "my account was hacked" from the same readers; LEARN has a new lab, and the website course two new lessons and a sixth quiz round.
Sanctions, address poisoning and a widget for your own site
- OFAC SDN screening. Every day NOSHASHI reads the US Treasury's SDN list from treasury.gov and keeps every XRP Ledger address it names. Check an Address reports a listed address with its entry, program and source; deposit screening holds any deposit whose sender, or an account that funded it up to three hops back, is listed, and credits nothing. A failed lookup is reported as unchecked, never as clear.
- Address-poisoning detection. A sender whose address starts and ends like one of your watched addresses or trusted counterparties is flagged, and held when it arrived as dust.
- Website widget (Enterprise, Strategic). One script tag puts three checks on your own site: verify that an address really is your deposit address (naming lookalikes), check any address against the ledger and the OFAC list, and deposit status by transaction hash. It holds no key, answers only on the sites you list, and never tells a customer why a deposit is under review.
- Open a case from a held deposit. A HOLD in the event feed opens an investigation case for the whole organization in one click.
- Dedicated environment is now described as what it is: provisioned per contract.
NOSHX: tickets and self-repair
- NOSHX reads, answers and acts on support tickets: list them, read a thread with the answer NOSHASHI's pages give, reply, resolve, reopen and open one. It writes only when your own message asks. Support staff can have it draft and send answers.
- Self-repair. Say what is wrong, or press SELF-REPAIR: NOSHX checks and repairs the mainnet link, sign-in, plan, saved settings and more, says what it could not fix and how, and can send the report to support.
Fixes
- The ledger connection could hang on a socket that was open but silent; it can now be reset and moves to the next public server.
- Eighteen foreign keys gained indexes, so deleting a watch or webhook no longer scans every event or delivery.
1.0.13
Enterprise and Strategic: deposit screening and XRPL event feeds
- Deposit screening (Enterprise). ADJUDICATION › LEDGER WATCH judges an incoming payment before it is credited, read live: it credits what arrived, never the Amount of a partial payment; holds a familiar ticker whose issuer owes nothing as counterfeit; flags a drop of dust carrying a link as a phishing lure; and traces who created the sender three hops back against your deny list. Watched deposit addresses are screened by the server every minute and sent to your webhooks as
deposit_screened. - XRPL event feeds (Strategic). Up to 100 watched accounts read from validated ledgers every minute; every event is sent to your webhooks as
xrpl_eventand can be pulled as JSON, NDJSON or CSV, with a history endpoint to backfill any ledger range. - Custom schemas, bulk export and retention (Strategic). Your own field-to-column shapes for ledger events and the audit log, used by console exports and the feed API alike; event history kept for 7 days to 10 years, as you set.
Institutional: every listed feature now exists
- Regulator seats. Owners, admins and compliance members give an examiner a read-only seat for 1 to 180 days. The examiner reads the organization's policies, exceptions, investigations and audit trail and can change nothing; the seat ends on its date by itself, and every visit is recorded in the audit trail.
- Scheduled monitoring. PORTFOLIO & RADAR › MONITOR re-runs the redemption stress test for every wallet in the book every 1 to 24 hours and keeps the readings, with a trend per wallet.
- Custom alert logic. Your own rules over those readings (recovery ratio, freezable share, days to exit, trapped value, frozen positions), joined by ALL or ANY, sent to the console, the desktop, or your webhooks as the signed event
custom_alert. - White-label console and reports. Your organization's name and colour at the top of the console and on exported audit files and passports.
- A complete audit log. Every export (with its SHA-256), recorded verdict, monitoring setting change, scheduled run and fired alert is now written to the organization's append-only audit log.
- The server now checks the organization's plan itself before granting a seat, setting a brand or recording a paid action.
1.0.12
Hands-on labs
LEARN opens on seven hands-on labs. Each step sends you to the real screen, with a real mainnet address or token already filled in, says what to look for, and asks one question about what you saw. Questions you answer right come back for review a day later, then after 3, 7, 16 and 35 days, so what you learn stays learned; a missed one comes back the next day. Every fact a lab states is checked by test against mainnet replies recorded in the repository. Check an Address and Token Rights now accept an address or token handed over from another screen, filled in for you to run.
The ledger-misread case about multi-signature quorums now opens Control Surface, the screen that reads signer lists, instead of Mission Control.
Support tickets
NOSHX has a TICKETS tab. Signed-in customers open a ticket with a subject, a topic, a priority and a description, and follow the thread in the app; NOSHASHI support answers every ticket from an inbox on the same screen, and sets status and priority. The other side is emailed on each new message once the project's email is configured. Tickets are private between the customer and support, messages cannot be edited or deleted, and a ticket containing a secret seed is refused before it is sent. The Support chat can carry an unanswered question straight into a new ticket.
NOSHX answers support on the website
The support console on every noshashi.app page is now NOSHX. It runs NOSHX Core in the visitor's browser, so questions are not sent to NOSHASHI and nothing costs money to answer: product questions are answered from the site's support answers and published pages with links to them, and a question naming an XRPL address, NFT id or transaction is read from the live ledger with the app's own readers (address checks share the free allowance of 10 a month). The server's reference answers remain as a fallback when the engine cannot load. A bot reply is no longer cut off at a fixed height.
In the app, NOSHX Core no longer repeats a sentence that two pages share, and on the Free plan a question about an issuer's freeze right is answered from the free address check instead of only pointing at Pro.
1.0.11
NOSHX opens on every Mac
On Macs whose system browser engine predates Safari 16.4, the NOSHX screen showed "NOSHX failed to render". NOSHX Core's sentence splitter used a pattern that engine cannot read, so the whole screen failed to load. The pattern is gone, and a test now fails the build if one comes back anywhere in the app.
Saved settings can no longer break NOSHX
The runtime choice saved by an earlier version is checked as it is read. A missing endpoint or an unknown runtime falls back to a safe default instead of stopping the screen.
NOSHX Core answers when your saved model is not running
If the runtime you chose last time is not running when the app opens (Ollama closed, for example), NOSHX no longer sits disabled. With failover on, NOSHX Core answers and a notice says so. Your choice is kept, so switching back is one click once the runtime is running.
1.0.10
NOSHX, the compliance agent
The Agent screen is now NOSHX. It answers by reading the live ledger with the app's own read-only tools, and lists every read under its answer: issuer authority, order-book depth (listed and funded), settlements, control surfaces, provenance, AMM pools, issuance, the address check, claims, NFT rights, and ledger status and sync. It cannot sign, submit or move anything. Each tool needs the same plan as the screen it mirrors, and address checks on the Free plan count against the same 10 a month.
- It knows NOSHASHI. Questions about the product itself (screens, features, plans and prices, the API and webhooks, security, privacy, and which tools suit a customer) are answered from the product's own pages: the Learn course and its word list, every docs page, pricing, trust, enterprise and legal. The pages are searched inside the app, with no extra model and nothing sent anywhere. With no model running, the support desk answers from the same pages.
- Compliance questions (KYC, AML, the Travel Rule, MiCA, credentials, audit evidence, treasury control) are explained, then pointed at the screen that addresses them and what it does not cover.
Switching between a local model and a hosted one works
Switching the agent from a local model to a hosted one (or back) could revert or fail. Five causes, all fixed:
- The saved choice was overwritten with the default (Ollama) on every launch.
- A hosted provider that failed its first check (no key yet, a slow reply) silently switched back to a local model.
- A slow, older check could overwrite a newer choice.
- Every request to Claude carried a setting current Claude models reject, so the first message failed.
- Custom endpoints could never connect, and some hosted providers were blocked by the app window's security rules.
Each provider now remembers its own endpoint and model, the endpoint can be edited, and optional failover answers with the last runtime that worked when the chosen one fails, and says so.
API keys never enter the app window
Model requests are now made by the app itself rather than its window. A provider key goes from the operating system keyring straight to that provider's own host; the window can store, check or clear a key but not read one back. A named provider's key is only ever sent to that provider, a custom endpoint must use HTTPS, and local models never receive a key.
NOSHX Core: its own engine, no outside model
NOSHX now runs on NOSHX Core by default: NOSHASHI's own engine, with no language model at all. It works out what is being asked (addresses, transaction hashes, currency codes, and what you want to know about them), runs the matching ledger readers, and writes the answer from what it read, in the same words the screens use. Product and compliance questions are answered with the most relevant sentences from NOSHASHI's pages, with their sources, and "which screen" questions name the screens that fit and the plan each needs. It answers in milliseconds, works offline, needs nothing installed and runs on any laptop. Its knowledge of NOSHASHI's pages is compiled when the app is built, so only their text ships (about 75 KB compressed), and it is indexed in the background when the NOSHX screen opens: the first answer no longer waits for it.
A language model is optional. If one is added and cannot call tools itself, NOSHX Core reads the ledger for it. With failover on, any model that fails falls back to Core.
The NOSHX model
A kit to train NOSHX's own language model is in scripts/noshx-model: training data made entirely from NOSHASHI's own content, a free Google Colab notebook, and the Ollama Modelfile. It fine-tunes IBM's Granite 4.0 1B (Apache 2.0 licence) into NOSHX, about 1 GB, which answers quickly on a laptop's CPU. Microsoft's Phi-4-mini (MIT licence, about 2.5 GB) is an option for better writing at lower speed. Local requests use a fixed context size so memory use stays predictable, and deep reasoning, off by default, lets a model think before answering (for Claude it raises the reasoning effort).
Pricing
Single sign-on (SSO/SCIM) is not available yet and is no longer listed as part of the Institutional plan.
1.0.9
Every screen scrolls instead of hiding its panels
Several screens were fixed to the window height and squeezed their lower panels, sometimes to nothing, when the window was not tall enough. They now scroll, and no panel shrinks below its content.
- Mission Control: the ledger cadence, compliance coverage, live ledger stream, wallet gate, policy rule set and network panels were squeezed under the status bar on a normal laptop screen. They are all there again.
- Compliance Agent: the runtime, guardrails and human escalation column was cut off; on a smaller window, human escalation had no height at all. The support and security addresses are shown in full, the "runtime not detected" message reads as two sentences, and Compliance, Support, Observer and Governance are now one set of tabs.
- Trust & Security: the page could not scroll, so "Where your data goes", "Human oversight", "What this does not claim" and the list of ledger commands could not be reached. It now scrolls and has the same margins as every other screen.
- Domain Grid and Growth: their side columns now scroll instead of squeezing network facts and the publishing note.
- Sidebar: the list fades out at the bottom, so a section heading below the fold no longer looks like an empty section.
Groundwork for iPhone and iPad
The desktop-only parts (menu bar tray, HUD, global shortcut, launch at login, updater) are now separated from the rest, the first step to an iOS build from a Mac with Xcode. docs/IOS.md has the steps. There is no iOS release yet, and the desktop app works exactly as before.
1.0.8
Watching, investigating, and saying "no answer" honestly
- Observer (Agent › Observer): watches your saved wallets every 5, 15 or 60 minutes against the validated ledger and reports only what changed: a line frozen or deep-frozen, a holding or XRP balance falling 10% or more, a credential revoked, expired or entering its last week, an issuer's controls drifting, an account deleted. Each observation carries the before and after readings, and one click hands it to the agent, which is told to use only those facts. Readings stay on this device.
- One-click issuer investigation: from the Garden and the authority certificate, one button runs the authority certificate and the issuer's outstanding obligations together and hands the agent every fact found.
- Five-state checks: every check now reads PASS, FAIL, REVIEW, INSUFFICIENT DATA or NOT APPLICABLE. A supply walk that did not finish is "no answer", not a failure; an issuer with no obligations has nothing a concentration check can measure. Receipts and certificates issued before this keep their exact digests. Authority rules are now version 2.
- Exception review: a reviewer can ask for more evidence instead of approving or rejecting. The requester adds links, transaction hashes, accounts or digests, and the exception returns to the queue. Both steps are audited and delivered to webhooks (
exception_evidence_requested,exception_evidence_added). - Landing garden: the pond on the home page and the app's landing screen moves with the XRP Ledger. Each validated ledger that closes sends one ring, stronger the more transactions it carried, and the caption names the ledger. With no ledger arriving the water stays still.
1.0.7
The flower is the brand
- Logo: the owner's flower artwork replaces the rocket on the app icon, the dock, the installers, the favicon, every page header and inside the console. The macOS menu bar uses a flat single-colour version of it.
- Website hero: NOSHASHI as the title above the question; the flower, animated, with smaller flowers around it; the bloom blended behind them; an ASCII pond (asciify-engine) with the XRP mark rippling in the water.
- Whole site: a faint ASCII pond behind every page, green, following the light/dark toggle, pausing under the hero and in background tabs.
- Desktop app: the landing screen carries the ASCII pond and XRP mark; garden patterns replace the orbit graphics; matcha primary buttons.
Fixes
- Enterprise and Strategic subscriptions now receive their tier (database, webhook and API limits); before, they fell through to the free tier.
- The Asset Passport PDF had a corrupt cross-reference table.
- The console showed "100%" stream success and ledger "0" before connecting; it now shows a dash until real data arrives.
- Site header overflowed from 1200 to 1480px; three pages scrolled sideways on phones.
1.0.4
Website design theme unified across all pages
The guide, research/findings and legal pages were still rendering with the old blue-dark palette (--brand:#3A82F6, --ground:#0B0F14) instead of the green-black brand palette that the home page and all other public pages use (--brand:#9BE15D, --ground:#08100B). This made the product look like two different products depending on which page you landed on.
All three pages now link core.css — the single stylesheet that holds the correct tokens — and no longer carry an inline copy of a superseded palette. The inline token block was the only thing that needed to change; layout and component styles were untouched.
Light-mode support is now active across every public page. The color-scheme meta was dark-only on the three affected pages; it is now dark light, and the theme-toggle script and localStorage persistence are wired in, matching every other page on the site.
Pages fixed: /guide/, /research/ (Findings), /legal/ Pages already correct: home, pricing, contact, news, progress, status, certificate, developers, enterprise, strategic-infrastructure
Unreleased
The public site is now rendered before it is served
The website was a hand-maintained static page whose most important section had gone stale. The download block named v0.3.0 while the repository was on v0.3.1, with byte sizes and SHA-256 values to match — on a page whose whole argument is that you should verify the hash before running the binary. A wrong hash there does not just fail; it teaches the reader that the check is noise.
The download section is now generated from the GitHub Releases API at build time. It cannot disagree with the release again, because there is no second copy to disagree with. Every artifact is labelled BETA: the builds are pre-1.0 and unsigned, and that belonged on each one rather than only in a note underneath.
scripts/build-site.mjs renders the landing page from templates/home.html, plus four new pages — /news/, /status/, /progress/ and /contact/. Rendering at deploy time rather than per request was chosen deliberately: it puts the same content in the HTML a crawler receives, without making the homepage's availability depend on a news site's uptime. A failed upstream fetch renders an honest empty state and never fails the build.
Live XRP data, and an honest empty state for it
A market panel carrying spot price, seven days of history, reported volume, and the validated ledger the network is on right now — read server-side from CoinGecko and an XRPL public node, so the page makes no cross-origin request and the CSP stays closed. The charts are SVG rendered on the server with a crosshair, a tooltip carrying the exact value and timestamp, labelled axes and keyboard traversal.
The 24-hour change is not coloured green or red. Status colour is spent on GO/HOLD/NO-GO and a price moving is not a verdict; direction is carried by a glyph and a signed number, which also survives a reader who cannot separate the two hues.
The newsroom merges three public RSS feeds. Two of the three were silently returning nothing at first: the tag extractor stripped markup before unwrapping CDATA, and <![CDATA[Ripple files a brief]]> matches a tag-stripper end to end, which deleted the headline and dropped the whole source. Decode first, then strip.
Accounts and the hosted workspace were withdrawn
/login/, /dashboard/ and /auth/ are deleted and redirect to the root. The workspace presented fabricated figures — "04 open evidence", "07 active workflows" — which is the one thing this codebase bans outright. NOSHASHI runs on your machine and reads public ledger state; the site no longer asks anyone to create an account to evaluate it.
Checkout failures are now diagnosable
Every Stripe error collapsed into 502 "Stripe could not create checkout." — the same five words whether the key was from the wrong mode, the price had been archived, or the account was restricted. Stripe returns a precise code for all three and the handler discarded it. The real error is now logged, the price ID moved to STRIPE_PRO_PRICE_ID (a price ID is mode-scoped, so a literal can only be correct in one of test or live), the fetch is guarded, and the endpoint answers JSON when asked so the page can show the reason in place.
/api/stripe-status reports whether checkout actually works, without revealing the key.
Contact, support and the mission log
A contact form that delivers to every configured channel and refuses to claim a delivery it did not perform — with nothing configured it returns 503 and shows the address that works, rather than accepting a message nobody will receive. /api/contact-status reports what is configured.
A support console answering from api/_lib/kb.js, which is also the source for the landing page's questions section. It works with no API key by retrieval and upgrades to Claude when one is present; both modes refuse to state a figure the site does not state. A price-prediction question used to reach the entry about which network is read, on the word "xrp" alone — a confident answer to a question nobody asked. It now refuses.
A mission log built from repository notices merged with the GitHub releases feed, so a release cannot appear in it without a build behind it, and a status board derived from the log rather than maintained separately.
Elsewhere
- Typefaces are self-hosted on the site, matching the desktop build's policy. Opening a page no longer announces the visitor to a font CDN, and two render-blocking connections are gone.
- Security headers, including a Content-Security-Policy, and a local preview server that applies them — so the policy is exercised against a real browser before it meets production.
/assets/*moved to a five-minute browser cache with a long CDN cache. The filenames carry no content hash, so the previous one-hour browser cache could leave a visitor on new markup with the previous deploy's stylesheet.- The landing page opens with the name and the mission, over a starfield confined to the hero — a bounded exception to the motion rules, recorded in DESIGN.md with the terms it is granted on.
- 32 tests covering the render layer, most of them about escaping third-party feed text, which is the difference between a newsroom and a stored XSS on the marketing site.
0.3.1
LEDGER CADENCE reported a healthy network as failing. 0.3.0 measured the interval between closes by differencing ledger_time, which is not a timestamp of the resolution that implies: XRPL rounds a close time to the ledger's close_time_resolution, and when the rounded value collides with the parent's it takes parent + 1 second instead. Consecutive closes inside one resolution bucket therefore report exactly 1s, and the bucket boundary reports 8s or 9s.
Measured against mainnet on 2026-09-15, thirty-three consecutive intervals read 9,1,1,8,1,1,8 — never once the three to four seconds the network actually runs at. Their mean was 3.94s, which is right, because the rounding preserves the total and destroys the distribution. Drawn per-interval it announced eighteen of twenty-eight closes as out of band while the network was entirely healthy — the panel inventing a fault, which is the one thing this product is sold on not doing.
Cadence is now measured from when each close reaches this machine, and labelled as that rather than as the ledger's own rhythm: it includes the local network path, exactly as roundTripMs does in net/sync.ts. The same window now reads 3.72–4.08s with a mean of 3.85s. closeAt is kept for labelling a ledger and carries a note against using it for intervals.
The ribbon also became a dot strip. As bars it had to be anchored at zero or it would misstate every ratio, and at that scale the real signal — four tenths of a second of spread — was a few pixels inside a wall of identical bars. A dot encodes position rather than length, claims no baseline, and can carry a range zoomed to the data honestly, with the 3–4s band drawn behind it supplying the reference the axis no longer does.
The application icon had white corners. It painted a rounded rectangle on a square canvas, leaving four transparent corners — which render white on any light ground and bake white in through a converter that flattens. Every platform masks an icon itself, so the second rounding underneath was never wanted. The ground is now full-bleed and the mark is centred, six pixels left of true before.
0.3.0
LEDGER CADENCE was not measuring cadence. The panel plotted transactions per close, which is throughput: a ledger carrying four hundred transactions and one carrying none can close on exactly the same rhythm, and a network genuinely slowing down would not have moved the line at all. The one reading the panel is named for was the one reading it did not contain. It now draws the interval between consecutive closes against the three-to-four-second window a healthy network closes in, with the observed median as a centre line and the distribution of intervals down the right edge — twenty closes crossing the band and twenty pressed against one edge of it look alike in sequence and mean different things about the network.
This needed the close time carried through as a number. LedgerTick kept only the formatted string, and an interval cannot be recovered from "14:32:07". LedgerStreamClose.closeAt is the ledger's own close time in epoch millis — deliberately not the moment the frame arrived here, because arrival interval measures this machine's connection and a local network stall would otherwise render as XRPL slowing down. It is zero rather than a date when a node omits ledger_time, since rippleTimeToDate(0) is 2000-01-01 and differencing against it would manufacture an interval.
Two things in COMPLIANCE COVERAGE were drawn as measurements that were not measurements. DOMAIN ENFORCEMENT was connected ? 100 : 0 and NODE LOAD FACTOR was 100 / loadFactor, both rendered as percentage bars. A bar implies a scale and a measured position on it; a binary has no such continuum, and an inverted multiplier is not a percentage of anything. Both are now states, showing the actual load multiplier and distinguishing "not read" from "off" — a node that never reported a load factor is not a node under no load.
The two figures that are proportions became bullet graphs, so each carries the threshold it is judged against rather than leaving the reader to supply one from memory. Credential coverage is judged at 100: a permissioned domain admits on all of its requirements or none, so eighty percent is not most of the way there.
The Compliance API refused every credentialed subject. CredentialType is a variable-length blob and arrives hex-encoded — KYC_LEVEL_1 reaches the edge function as 4B59435F4C4556454C5F31. The console decodes it; the server did not, and compared raw hex against the domain's plain-text requirement. It never matched. Every CREDENTIAL_* check failed for subjects who genuinely held the credential, and the API's answer was no-go regardless of the ledger. Decoded now, exactly as fetchWalletCredentials does.
The same function invented ledger state when it could not read any. rippled's HTTP JSON-RPC reports a command error inside result and sends HTTP 200 doing it — only the WebSocket API puts the error at the top level, which is the shape the code tested for. An unknown or unreadable account therefore arrived as an empty result and became an account with a zero balance and no credentials, which was then adjudicated as though it had been read. It now raises the ledger's own error code: an unfunded account gets the same unfunded record the console produces, so both sides digest the same receipt, and anything else returns 502 rather than a verdict.
Windows and Linux stored no secrets at all. keyring compiles no credential store unless a backend feature asks for one, and falls back to an in-process mock in silence. Only apple-native was listed, so on the Windows and Linux builds the compliance API key and every model-provider key were written to memory: the UI reported success, and the value was gone at the next launch. Backends are now selected per target.
open_external could run arbitrary commands on Windows. It shelled out through cmd /C start, and cmd re-parses its command line with rules Rust's argument quoting does not cover — &, | and ^ reach it unquoted, so a URL of https://example.com/?a=b&calc.exe ran calc.exe. That is the exact escape the command's scheme check exists to prevent. It now uses rundll32, which is not a shell.
export_text_file could write outside Downloads on Windows. Taking the last path segment does not help when join replaces the base path for an argument carrying a drive prefix, so C:audit.csv escaped intact. Names carrying a separator, a drive letter or a control character are refused rather than salvaged.
The version was wrong everywhere it was shown. The About panel, the footer and the legal BUILD row all read 0.1.0 at version 0.2.2, as did both DMG packaging scripts — which meant the release script never found the DMG it had just built and silently repackaged from the .app every time. All of it now reads package.json, substituted at build time.
Automatic updates. Signed, verified against a key compiled into the application, and never installed without a click — see docs/UPDATES.md. Inert until a signing keypair exists, and it says so rather than offering a button that cannot work.
Two receipt lines corrected: ACCOUNT_ACTIVATED said "Account is funded" beside a failed check for an address that had never been funded, and the transferCeilingXrp documentation said zero meant uncapped where the engine — correctly, and under test — treats it as a closed domain.
0.2.2
Linux ships. The 0.2.1 release run failed on one of its four build jobs — Install Linux webview dependencies on the Ubuntu runner — so no .deb or .AppImage was ever attached to that release, while macOS and Windows published normally. The dependency list had drifted from Tauri 2's documented set for Ubuntu 22.04 in two ways: it carried the legacy libappindicator3-dev alongside the ayatana package that supersedes it, and it omitted libxdo-dev, which Tauri 2 requires. Both corrected.
pkg-config --modversion webkit2gtk-4.1 now runs immediately after the install, so a missing webview names itself at the step that installs it rather than surfacing minutes later as an opaque Rust link error.
Releases are no longer marked as pre-releases. The 0.2.1 release carried that flag, which meant releases/latest returned nothing and the repo page never showed a current release.
The site advertised Windows as "Building in CI" for a build that had succeeded and been published. The .exe and .msi are now real downloads with their SHA-256 beside them, and the Linux card states what actually happened rather than claiming a build is still running.
Findings are published at noshashi.app/research: the five mainnet measurements, each carrying the date it was taken and what would need re-running before anyone repeats it — including the negative result that removed address-poisoning detection from the roadmap.
0.2.1
Control-change forensics in Provenance: when the signing authority over an account last moved, and whether that is the shape of a stolen key. Rare events — 7,965 consecutive mainnet transactions contained none — which is what makes each one worth surfacing.
Two site fixes. The header nav wrapped and collided with the wordmark between roughly 900 and 1100px. The hero graphic pushed the page 39px wider than the viewport in the same band.
A handoff sent to a plan-gated scene never expired, so it could fire a stale lookup weeks later once the plan was bought.
Not built: address-poisoning detection. It was on the roadmap and the evidence removed it. Fourteen accounts scanned for lookalike counterparties turned up nothing, and XRPL charges 1 XRP to bring an address into existence — a thousand lookalikes cost 1,000 XRP before a single dust payment, where the same attack on an account-free chain costs only gas. The reserve is a structural deterrent, and building a detector for a threat the ledger already prices out would have meant inventing a problem.
0.2.0
Eight new read tools, two correctness fixes in capabilities that were already shipping, and the first test suite.
Two bugs that were giving wrong answers to paying customers
Order book depth was overstated by up to fourteen times. An offer rests in the book whether or not its owner still holds the asset to honour it, and rippled reports the difference in taker_gets_funded. NOSHASHI was summing the advertised amount. Measured on mainnet on 2026-08-28:
| Book | Advertised | Actually fundable | Phantom |
|---|---|---|---|
| USD / Bitstamp | 1,606,485 | 116,107 | 92.8% |
| USD / GateHub | 1,881,039 | 772,777 | 58.9% |
One offer advertised 1,400,100 USD against an owner balance of 22,273. That figure fed exit liquidity, so the console was telling operators they could exit positions the book could not absorb. Depth is now discounted to what can actually fill, and the advertised figure is kept beside it rather than silently dropped.
Deep-frozen balances were reported as merely freezable. XLS-77 deep freeze is a separate flag from an ordinary freeze and a strictly worse position: an ordinary freeze stops the holder sending, a deep freeze stops them receiving as well. Exposure analysis read only the ordinary flag, so a deep-frozen line came back as "issuer retains the right to freeze this balance" at severity info — a present, total immobilisation described as a future possibility. The free public address check already read both flags; only the paid analysis was blind to it.
New tools
| Tool | Plan | What it answers |
|---|---|---|
| Settlement | Desk | What a transaction delivered, against what it requested |
| Order Book | Desk | How much quoted depth is backed by someone who still holds the asset |
| Provenance | Desk | How old an account is, and who sent it its first XRP |
| Control Surface | Desk | How few signers can actually move a treasury |
| Pool Governance | Desk | Who votes an AMM's fee, and who holds the discounted slot |
| Issuance | Institution | Holder concentration from the issuer's side |
| Inbox | Free | Unsolicited claims, with the claimed issuer verified |
| Ledger Sync | Free | Four public nodes compared, disagreement treated as the reading |
Each is built around a specific field that misleads when taken at face value. delivered_amount against Amount, because a tesSUCCESS payment can deliver 0.4% of the stated figure. Signing weight rather than a count of signers, because five signers where one carries the quorum is a single-key account. A currency code, because it is not a name anyone owns — any account may issue a token called USDT.
Findings now carry between screens: an address named in one is one click from being the subject of the next.
Tests
164, over the logic that makes claims. There were none before.
They are verified by mutation rather than by passing — each safety rule is deliberately broken to confirm a test fails. That process found four cases where a suite passed while the code was wrong, every one of them because the tests exercised the reasoning and never the code that reads the ledger.
CI now runs typecheck, the suite, a build and a production dependency audit on every push, and a release cannot be cut without them.
Security
- Content Security Policy corrected — a node the console queries was not on the connect-src allowlist, which would have failed silently in the packaged app while working in development.
freezePrototypeenabled.- Two database advisories closed: an unnecessary
EXECUTEgrant revoked, and a function'ssearch_pathpinned. Row-level security verified still auto-enabling afterwards.
Housekeeping
The demo's own description of itself, the pricing tiers in the app, the pricing on noshashi.app, the compliance agent's console reference, and the documentation had all been written before these tools existed. All five now agree, and two of them are held to it by tests — the agent's reference against the actual scene list, and the plan catalogue against the entitlements each tier grants.
The agent had also been quoting the wrong keyboard shortcut for every screen, and knew about six of twenty-four. Because it is instructed to say it lacks a fact rather than guess, an incomplete list made it deny features that shipped.
0.1.0
Initial release.
Generated from CHANGELOG.md