THE LEDGER CAN BE TRANSPARENT AND STILL BE MISREAD
Every field is public. Not every reading is right.
Six replies read from XRPL mainnet, each shown two ways. The right-hand column is not written for this page: it is what NOSHASHI's own code returns for the recorded reply, and a test fails the build if the two ever disagree.
01 / delivered_amount ≠ Amount
What a basic interface sees
Amount field
100,000 XRP paid
What NOSHASHI verifies
delivered_amount
0.077162 XRP arrived — 0.00008% of the stated amount
A successful (tesSUCCESS) payment carries the amount it asked to deliver and, separately, what arrived. With the partial-payment flag set they differ and the transaction still succeeds. Crediting the Amount field would over-credit by 1,295,975×. This one is an account paying itself through the exchange; the same flag on a payment to an exchange is how deposits get over-credited.
Ledger 107,194,530 · transaction 307662378F… · src/lib/desk/settlement.ts
02 / Quoted depth ≠ fillable depth
What a basic interface sees
Sum of offers
128,309.49 USD on offer
What NOSHASHI verifies
Funded and unexpired
42,328.77 USD can fill — 33% of what is shown; 31 of 60 offers cannot fill at all
An offer stays in the book whether or not its owner still holds the asset, and an expired offer is removed only when something touches it. Summing the advertised figures counts exits that cannot happen.
Ledger 107,194,532 · 60 USD.Bitstamp offers for XRP rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B · src/lib/desk/book.ts
03 / Sequence ≠ transaction count
What a basic interface sees
Sequence
86,795,414 transactions sent
What NOSHASHI verifies
Sequence − creation ledger
0 transactions sent. The account was created in ledger 86,795,414, and as an AMM pseudo-account it cannot send any.
Since the DeletableAccounts amendment, a new account's Sequence starts at the ledger index it was created in. It says when the account began, not what it has done.
Ledger 107,194,965 · account rHUpaqUPbwzKZdzQ8ZQCme18FrgW9pB4am · src/lib/desk/provenance.ts
04 / Quorum ≠ signer headcount
What a basic interface sees
Signers listed
3 signers control the account
What NOSHASHI verifies
Minimum who must agree
2 of 3 can sign: quorum 2 against weights 1, 1, 1
XRPL compares a multi-signature quorum against the sum of signing weights, not the number of signers. The number that describes control is the fewest signers who can reach the quorum.
Ledger 107,194,532 · signer list owner rLdhU5DKrpztzVPnQmtzAbHfiHR8LPYtaX · src/lib/desk/control.ts
05 / Absent ≠ false
What a basic interface sees
Balance
0 XRP
What NOSHASHI verifies
Account activated on mainnet
FAIL — Address is well-formed but has never been funded on mainnet.
The ledger answered actNotFound: there is no account at this address. That is not an account holding nothing; a payment to it would have to create it, and nothing about it can be verified.
Ledger 107,194,798 · address rPGJe8F1FzegsNDJEMkq3hUrupovdBjQMi · src/lib/xrpl/client.ts
06 / Ripple epoch ≠ Unix epoch
What a basic interface sees
date as Unix time
1996-09-24 02:42:12 UTC
What NOSHASHI verifies
date from 2000-01-01
2026-09-24 02:42:12 UTC
Ledger times count seconds from 2000-01-01, not 1970-01-01. Both readings are plausible dates and only one is right; the wrong one is 30 years early.
Ledger 107,194,530 · transaction 307662378F… · src/lib/format.ts
