XRP Ledger
Everything on this page is generated from the running deployment. If a capability stops being served, the row for it changes rather than staying true-looking.
| What | Method | On XRP Ledger | Notes |
|---|---|---|---|
| Read a balance | balance.get | Not here | Not commercially available on this network. |
| Read network state | network.status | Not here | Not commercially available on this network. |
| Watch for a payment | payments/watch | Available | Followed by the light acquisition path, one bounded read per pass. |
XRP Ledger is NATIVE, chain id 0.
Its engine here is xrpl.
What XRP Ledger means by settled
Reported in this chain’s own vocabulary. It is never translated into a shared “confirmed”, because the translation is where the money goes missing.
This chain has a protocol condition for finality: a block either meets it or does not, and waiting longer does not make a block that has met it any more final. Depth is not meaningful here.
- The strongest thing XRP Ledger says is
VALIDATED. - Its intermediate condition is
VALIDATED. - Depth is not what settles a block here, so this deployment does not count to one.
Paying on XRP Ledger
This deployment follows XRP Ledger for payments and can watch one destination for one asset.
- The asset this deployment can identify here is RLUSD (Ripple USD), named as
RLUSD:rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De, with 6 decimals read from the contract rather than assumed. - Amounts are compared as an integer count of the smallest unit. A float would round, and a rounded payment is a dispute.
- Detection and settlement are separate standings. You choose which one your checkout ships on.
A destination on XRP Ledger needs a destination tag. a 32-bit number that identifies the payee within a shared account. A watch without one is refused when you open it, rather than accepted and never matched.
Known limitations on XRP Ledger
- Free Beta: nothing is priced and no availability is promised.
- Answers here rest on something asserted from outside the protocol -- a checkpoint published by somebody, or a header that carries no proof of its own canonicity. However much cryptography verifies beneath it, the claim is capped by that assertion, and this is said in every response rather than assumed away.
- Source independence is unestablished here: this deployment cannot show that two sources it might ask are operated separately, so agreement between them is treated as availability rather than as evidence.
- No commercial read method is available on XRP Ledger.
- No transaction history, no archive and no broadcast on the Beta surface.