Servers
- wss://xrplcluster.com
- wss://s1.ripple.com
- wss://s2.ripple.com
The app connects directly to public servers: xrplcluster.com, s1.ripple.com and s2.ripple.com, in failover order (the Network view also compares xrpl.ws). The Compliance API reads s1 and s2 over HTTPS. No NOSHASHI server sits between the app and the ledger. Only read commands are sent; the full list is below and is checked by test.
Validated state only
Every state read asks for ledger_index "validated" or reads a validated range. A transaction counts as final only when the server says validated: true; until then it is shown as not final.
Commands sent
account_info · account_lines · account_objects · account_tx · amm_info · book_offers · fee · gateway_balances · ledger · ledger_entry · nft_buy_offers · nft_sell_offers · server_info · subscribe · tx
Never sent: submit, submit_multisigned, sign, sign_for, wallet_propose, channel_authorize, validation_create, wallet_seed. A test fails the build if any covered file sends one, or sends a command not on the list above.
Normalization
Drops become XRP exactly; hex fields are decoded; Ripple-epoch times become UTC; delivered_amount is used instead of Amount; a field the ledger did not return stays empty rather than becoming zero.
The ledger can be read correctly and still be misread. Six recorded cases show a field taken at face value next to what NOSHASHI's code reports for the same reply.
Generated from src/lib/xrpl/link.ts · src/lib/trust/boundary.json