The XRP Ledger (XRPL) is a public blockchain that processes XRP transactions without the need for energy-intensive mining. Instead, it relies on a consensus protocol where validators vote on transactions, confirming transfers within three to five seconds at a minimal cost.
Separating the Network, Token, and Ripple
The XRP Ledger serves as the blockchain where XRP transactions occur. XRP is the native cryptocurrency used to pay transaction fees. Ripple, a private financial technology company, develops payment products and holds a large amount of XRP, but it does not own the ledger. Independent developers maintain the open-source software, while universities, exchanges, and other organizations run servers.
The network was developed by David Schwartz, Jed McCaleb, and Arthur Britto starting in 2011, with the goal of creating a payment system that did not depend on mining. The XRP Ledger launched in June 2012 with a fixed supply of 100 billion XRP. The founders later gave 80 billion XRP to the company that became Ripple, which placed much of its supply in escrow accounts releasing XRP on a fixed schedule. Critics have raised concerns about the concentration of tokens under one company.
Validator Consensus Without Mining
The XRP Ledger uses the XRP Ledger Consensus Protocol instead of proof-of-work mining. Validators review proposed transactions and vote on the next ledger version. Each validation round typically takes between three and five seconds, and a transaction becomes final once validators approve the updated ledger. Users do not need to wait for multiple block confirmations.
Each server follows a Unique Node List (UNL) that identifies the validators it trusts when checking transaction proposals. Operators can create their own lists, though many use a recommended default. The system continues to operate when fewer than 20% of trusted validators act incorrectly. If the share exceeds that level, the network may stop reaching consensus. More than 80% would need to coordinate to approve an invalid transaction.
Account Reserves and Destination Tags
The XRP Ledger requires each active account to hold a base reserve of 1 XRP, with an additional 0.2 XRP required for certain ledger objects such as trust lines and open trading offers. This rule limits the creation of unused accounts and reduces unnecessary ledger data. Users cannot spend the reserved amount while the account remains active, so anyone moving XRP into self-custody should include the reserve in their planned balance.
Destination tags are essential when sending XRP to an exchange. Many exchanges use a single XRP address for multiple customers, and the destination tag tells the exchange which customer should receive the deposit. A missing or incorrect tag may prevent automatic crediting, and the XRP may remain under the exchange’s control until support staff can identify the sender. Users should verify both the address and tag before approving a transfer.
Fees, Self-Custody, and German Tax Rules
A standard XRP Ledger transaction carries a minimum fee of 0.00001 XRP, which can rise during heavy network activity. The network destroys the fee instead of paying it to validators, discouraging spam and gradually reducing the total XRP supply.
The ledger also includes a decentralized exchange where users can trade XRP and issued tokens through offers recorded on the network. Non-XRP tokens require trust lines because another party issues and backs them.
Users who keep XRP on an exchange do not control the private keys. Self-custody gives them direct control but also makes them responsible for protecting the recovery seed. A personal XRP wallet normally does not require a destination tag.
In Germany, selling XRP within one year of purchase may create a taxable private disposal gain. Crypto-to-crypto swaps can also count as sales. Investors should retain complete transaction records and seek qualified tax advice, as individual circumstances and future legal changes can affect the final treatment.