On this page
  1. XRP, the XRP Ledger and Ripple
  2. How transactions reach agreement
  3. Transaction costs and account reserves
  4. What XRP is used for
  5. Supply, original allocation and escrow
  6. Development and status as of October 8, 2026
  7. The main risks and practical checks

XRP is the native cryptocurrency of the XRP Ledger, a public blockchain designed to move and exchange value. It pays network transaction costs, supports account reserves and can act as an intermediary between other assets. Ripple is a company that contributes to this ecosystem, but buying XRP does not give someone shares in Ripple.

That distinction is the starting point for understanding the coin. A business announcement about Ripple, a new feature on the XRP Ledger and a change in demand for XRP describe different things. They may be connected, but one does not automatically establish the other. The market panel above provides changing market figures; this profile explains the system behind them.

XRP, the XRP Ledger and Ripple

David Schwartz, Jed McCaleb and Arthur Britto began developing the ledger in 2011. It launched in June 2012. The company that became Ripple was established later that year, with Chris Larsen joining the venture. The early use of the Ripple name for both the technology and the business helps explain why the terms still get mixed together.

XRP is the asset. The XRP Ledger, often shortened to XRPL, is the network and its shared transaction record. Ripple is a commercial participant that contributes software and develops products. Independent developers, server operators, validators and other businesses also participate. XRP ownership is consequently different from owning a contractual claim on the company's revenue.

How transactions reach agreement

The XRP Ledger does not use competitive mining or stake-weighted block production. Its consensus protocol has servers exchange proposals about transactions and agree on the next ledger version. Each server relies on a chosen set of validators, called its Unique Node List, or UNL.

The important qualification is that these choices cannot be made in complete isolation. Reliable agreement depends on sufficiently overlapping trusted validator sets and on those validators behaving correctly. The protocol prioritizes agreeing on a valid result; under sufficiently serious faults it can stop progressing instead of continuing with conflicting outcomes.

Once a ledger version is validated, its results are treated as final. Project documentation describes ordinary settlement in roughly three to five seconds. This is a network characteristic, not a promise that an exchange will credit a deposit within five seconds. Compliance checks, account processing and a service's own policies can add time.

There is no native block reward for simply holding XRP or operating a validator. Products advertising XRP yield therefore need a separate explanation of where the return comes from and what additional exposure the customer accepts.

Transaction costs and account reserves

Transactions destroy a small amount of XRP as an anti-spam measure. The fee is not paid to a miner or distributed to XRP holders. As checked on October 8, 2026, the official documentation lists the normal minimum for a standard transaction as 10 drops, equal to 0.00001 XRP. Network load and some transaction types can require more.

Fees and reserves serve different purposes. A fee is consumed when a transaction is processed. An account reserve is XRP that must remain available to support an account and certain objects it creates. It limits the cost that persistent ledger data can impose on the network.

The documented mainnet base reserve on October 8, 2026, is 1 XRP, with a usual additional owner reserve of 0.2 XRP per qualifying object. Special cases apply, including rules around initial trust lines. Validators can change reserve settings, so a wallet's spendable balance can be lower than its total balance. Users should check the account's actual reserve requirement before assuming all displayed XRP can be transferred.

What XRP is used for

The simplest use is a direct payment from one account to another. XRP also supports the ledger's exchange functionality. Its built-in decentralized exchange allows offers to exchange XRP and issued assets. Where it produces a better route, a conversion between two tokens can pass through XRP as an intermediate asset.

That does not mean every asset transfer needs to buy a large amount of XRP. Trading pairs can involve two issued tokens, while the transaction still needs XRP for the network cost. The role of a fee asset and the role of a traded bridge asset should be assessed separately.

Automated market makers add another source of liquidity. An AMM holds two assets in a pool and applies a formula to price swaps. People who supply the assets receive liquidity-provider tokens representing their pool participation. Providing liquidity introduces exposure to both assets and to changes in their relative prices; earning trading fees is not the same as receiving a guaranteed return.

For another approach to blockchain payments and issued assets, see the Stellar profile. Similar use cases do not make the networks, coins or security assumptions interchangeable.

Supply, original allocation and escrow

The original XRP supply was 100 billion units. The founders allocated 80 billion XRP to the company. Unlike Bitcoin's mining-based issuance, XRP's supply was created at the beginning rather than distributed through a continuing mining schedule. The guide to premines and allocations explains why creation, distribution and market circulation are different questions.

Transaction-cost destruction reduces the XRP remaining in existence. It does not create a predictable market price: demand, liquidity and holder behavior still matter. Similarly, the original supply figure should not be confused with the quantity a market-data provider classifies as circulating today.

Ripple placed 55 billion XRP in escrow in 2017. Escrow locks funds under ledger-enforced conditions, such as a release time. Reaching a release condition is different from selling those funds to the market. A meaningful supply assessment needs dated information about holdings, releases and any later locking, rather than treating every unlock as an identical sale.

Development and status as of October 8, 2026

The XRP Ledger remains an active public blockchain with maintained documentation covering payments, issued assets, its exchange and AMMs. Its development has expanded beyond the original payments focus, but an announced proposal should not be confused with a feature enabled on mainnet.

Changes to transaction processing use an amendment system. Under the documented rules, an amendment needs more than 80% support from trusted validators for two weeks before activation. Software containing a feature can therefore exist before the network enables it. Older servers can become amendment blocked when they cannot interpret newly activated rules.

This separation matters when reading upgrade claims. A roadmap shows an intention; a software release shows implementation work; amendment activation changes what the production network accepts. New functionality should be described at the stage it has actually reached.

The main risks and practical checks

XRP's market value can change sharply even when the ledger is functioning normally. Ripple's original allocation and ongoing holdings also make distribution an important research topic. A low transaction fee does not answer questions about asset demand, concentration or future selling.

On the network side, users depend on sound validator selection, software maintenance and reliable service providers. Issued tokens introduce their own issuer risks. A familiar ticker on the ledger is insufficient identification because different issuers can use the same currency code.

Transfers need careful account details. Exchanges may use one address for many customers and require a destination tag to identify the intended recipient. Missing that tag can prevent automatic crediting even when the ledger payment succeeds. Check the receiving service's instructions, supported network, address and tag before sending. Finally, keep signing credentials private: fast settlement is useful, but it leaves little room to recover from authorizing the wrong transaction.