Swap XRP (XRP)

The numbers below were checked on 14 October 2026 against the documentation on xrpl.org.

A ledger every 3–5 seconds, no mining

The XRP Ledger does not have blocks found by miners. A set of validators proposes transactions, agrees on a set, and closes a new ledger version about every 3 to 5 seconds; once validated, a ledger is final and the next one begins. There is no mempool queue in the Bitcoin sense and no waiting for a lucky block. A payment that is accepted into a validated ledger is settled, and the close time written into the ledger is strictly later than the previous one's.

Confirmations the site waits for

The route data behind this site counts an XRP deposit after 2 validated ledgers — a few seconds — and the estimate reads 2–5 minutes, almost all of which is matching the deposit to your swap and preparing the payout. A swap from XRP is in the fastest group here, alongside TRON, Solana and Stellar.

Supply: fixed at the start, falling since

100 billion XRP were created when the ledger began, and the protocol has no way to create more. Every transaction destroys its fee — the docs say the cost "is irrevocably destroyed" rather than paid to any party — so the total only falls. The reference cost of a standard transaction is 10 drops, a hundred-thousandth of an XRP; it scales up when the network is loaded, which is the ledger's defence against spam. In 2017, 55 billion XRP were placed in escrow on the ledger, released on a schedule (xrpl.org's history page); that is visible on the ledger and does not affect a transfer.

Drops

The ledger counts XRP in drops: one XRP is a million drops, and amounts are integers of drops. A payment of 0.0000001 XRP is not a thing; the wallet rounds to six decimal places. For a swap this only matters at the edges — the amount you enter is rounded to drops, and the payout is an exact number of drops.

Reserves: the part that surprises people

An XRP address is not an account until it holds the base reserve. Since 2 December 2024 that is 1 XRP, down from 10; before September 2021 it was 20. The first payment to a new address must be at least 1 XRP or the ledger refuses it, and that 1 XRP stays locked for as long as the account exists. Each object the account owns — a trust line to a token, an open offer, an escrow, a signer list — locks a further 0.2 XRP of owner reserve, down from 2. The reserves are set by validator vote and can change again; the live values are in any server's the server_info method response, and the docs warn against hard-coding them.

One XRP is the price of a new account. If you are paid out to a fresh wallet and the amount after fees is below 1 XRP, the payment fails on the ledger — not here, not at the wallet, but at the protocol. Fund the address first or choose an amount comfortably above it.

An XRP Ledger address is a classic address: Base58, 25 to 35 characters, beginning with r, case-sensitive, with a 4-byte checksum and an alphabet that leaves out 0, capital O, capital I and lowercase l. That was checked on xrpl.org on 14 October 2026. The address is the account; the destination tag is a separate number that travels with a payment.

What the form accepts

For an XRP payout the form takes an r… address and offers a destination tag field. The address is checked for format and checksum; the tag, if you enter one, must be an unsigned 32-bit integer — 0 to 4,294,967,295. The form does not accept X-addresses, because the ledger itself only understands classic addresses and the tag has to be set as its own field. Services that show an X-address can also show the classic form.

The destination tag

The ledger attaches no meaning to the tag. It is a number carried with the payment so that the receiver's software can tell whose it is. Exchanges and hosted wallets keep every customer behind one r… address and give each a different tag; a payment with the wrong tag is credited to the wrong customer, and one with no tag has no customer at all. The RequireDest flag, which most exchanges set on their deposit address, makes the ledger reject a tagless payment outright — a safety net for forgetting the tag, not for mistyping it. Memo, destination tag, payment ID covers the same mechanism across networks.

Which address to give

1. Your own wallet: its r… address, no tag. If the wallet is new and empty, read the reserves section above first: the payout must be at least 1 XRP.
2. An exchange: the address and the tag from its XRP deposit page, both copied, the tag into the tag field. If the page shows an X-address only, look for a switch to classic view.
3. Another person: their r… address. A personal wallet needs no tag; if they give you one anyway, use it — an unused tag is harmless, a missing one is not.

The deposit side

The deposit address the form shows is an r… address, and it may come with a destination tag of its own. If it does, the tag is how your deposit is matched to your swap: enter it in your wallet's tag field or on the exchange's withdrawal form. A deposit that arrives without its tag reaches the address and is not matched to anything until support finds it by hash.

Every transaction on the XRP Ledger has a 64-character hash in upper-case hexadecimal. The status page links the XRP side of a swap to Bithomp, and the same hash can be opened on any XRP Ledger explorer — livenet.xrpl.org is the one run by the ledger's own community.

What a transaction page shows: the result code (tesSUCCESS for a payment that went through), the ledger index it was validated in and the ledger's close time, the sending and receiving accounts, the amount delivered in XRP, the fee in drops, the sequence number, and — for a payment — the destination tag if one was set and the source tag if any. A payment that failed shows a different result code and still appears on the ledger, with its fee destroyed; the amount did not move.

Result codes worth knowing

Each of these is final once validated. A failed payment is not retried by the ledger; the sender sends again with the problem fixed.

A deposit you sent

1. Copy the hash from your wallet or the exchange's withdrawal history.
2. Open it on the explorer. The XRP Ledger validates in seconds, so a hash that cannot be found a minute after sending was never submitted — exchanges in particular hold withdrawals for internal checks before anything reaches the ledger.
3. Check the destination against the deposit address from the form, the destination tag against the one shown with it, and the delivered amount against the figure you entered.
4. The status page updates on its own at the second validated ledger.

A payout you received

1. Open the payout hash from the status page.
2. The destination is your r… address; the delivered amount is "You get" from the form, with the payout network fee already taken out. If you gave a tag, it is shown with the payment.
3. An exchange credits the payout after it reads the tag; a personal wallet shows it at once, less the reserve if the account was new.
4. Keep the hash. It is the evidence the payout happened and what support on either side will ask for.

What a block explorer shows about a swap does the same walk for other networks; Reading a swap status page explains each stage.

XRP's mistakes are about the two things the ledger adds to an address: the tag and the reserve. Both are checked by the ledger itself, which helps, and both can be got wrong in ways the ledger cannot see.

The tag is the whole job

On most networks here the address is the only thing to get right. On the XRP Ledger an exchange's address is shared by every customer, and the tag is what makes a payment yours. The RequireDest flag protects against a forgotten tag and against nothing else: a payment with a mistyped tag is a valid payment to a valid account, and the ledger has done its job. What happens next is the exchange's manual process, if it has one.

A new wallet and the reserve

A wallet app will show you an r… address before the account exists on the ledger; the account is created by the first payment of at least the base reserve. A payout that falls short does not create a partial account — it fails, the swap's payout side sees the failure, and the amount has to go somewhere else. The reserve is small since December 2024, but a swap sized just above the route minimum can still land under it after the network fee. Check "You get" against 1 XRP before you give a fresh address.

Less arrives than the form expects

Exchanges take their withdrawal fee out of the amount you type. The swap runs on what arrived, and if the shortfall takes it under the route minimum it cannot be processed as a swap at all. Minimums, maximums and network fees on small swaps shows how the minimum is set.

The XRP Ledger settles in seconds and does not reverse. A validated payment with the wrong tag is final at the ledger; whether it can be fixed is a question for the exchange that received it.

The XRP Ledger changes by amendment: validators vote a feature in, and it activates once support has held long enough. Most amendments concern tokens, escrows and the decentralised exchange, and change nothing for a plain XRP transfer. The changes that do matter to a sender are reserve changes, which are not amendments but parameter votes. Dates and figures are from xrpl.org, read on 14 October 2026.

September 2021. The first reduction in the ledger's history that most current users saw: creating an account went from 20 XRP to 10, and each trust line or offer from 5 XRP to 2. For a swap it meant a payout to a fresh wallet needed 10 XRP rather than 20.

2 December 2024. The second reduction, voted in by the validators and effective at once: 1 XRP to create an account, 0.2 XRP per object. The blog post notes that XRP previously locked as reserve was freed in existing accounts the same day. For a swap it is the reason the reserve is now a minor consideration rather than a frequent cause of failed payouts — the route minimum is usually above it anyway.

What the reserve mechanism is. The docs describe a fee-voting process in which each validator publishes the reserve and transaction-cost values it wants, and the ledger adopts a value once enough validators agree. The purpose is to keep the cost of an account roughly stable in real terms as the price of XRP moves, so the figures are expected to change again; a wallet or a form that hard-codes them is wrong sooner or later. The live values are returned by any server's the server_info method.

Amendments in general. The ledger has had dozens of amendments since 2017; the ones a sender might read about — tokens on the ledger, automated market makers, clawback — add object types that each carry the 0.2 XRP owner reserve and do not touch a plain payment. The address format, the drop, the destination tag and the 3–5 second ledger have been the same throughout.

What has not changed. 100 billion XRP at the start and a falling total, a fee that is destroyed, the r… address, and a payment that is final a few seconds after it is sent. An address from 2013 still receives XRP today — if it holds the reserve.

The XRP Ledger and Stellar share a ledger-every-few-seconds model and the habit of asking for an extra field when the receiver is an exchange. For a transfer they differ in the details that trip people up. The table uses the confirmation counts and times the site is built from and what was checked on xrpl.org and developers.stellar.org on 14 October 2026; the Stellar side is described on the Stellar page.

The extra field. XRP's destination tag is always a number. Stellar's memo has four types, and an exchange may show a text memo where the form offers only the ID type — a limitation to check on the exchange's deposit page before using a route into XLM. On both ledgers a personal wallet needs no field at all.

Reserves. Both ledgers refuse a first payment below the account minimum. XRP's is 1 XRP; Stellar's is 1 XLM. XRP's per-object reserve is 0.2 XRP against Stellar's 0.5 XLM per trust line, offer or signer. On both, the locked amount stays locked while the account exists.

Fees. Both are tiny next to any swap amount. The difference is philosophical: the XRP Ledger destroys its fees, Stellar sends them to an account no one controls. Neither goes to a validator.

Time. Two ledgers on the XRP Ledger and ten on Stellar are both a matter of seconds; the site's windows overlap almost entirely.

Addresses. An r… address and a G… address cannot be confused with each other or with anything else here, and the form rejects either on the wrong route. The packed forms — X… on the XRP Ledger, M… on Stellar — are both refused: give the plain address and the tag or memo as two fields.