The XRP Ledger quietly built one of the world's oldest decentralized exchanges in 2012, three years before Ethereum existed. Parts 1 through 3 of this series covered how the ledger achieves consensus, how Ripple's commodity ruling changed the regulatory landscape, and how RLUSD and institutional settlement rails are reshaping XRP's use case. This capstone turns to the on-ledger building blocks — native order books, an AMM with an unusual auction mechanism, protocol-level NFTs, and a new institutional token standard — before ending where coin-guide readers actually need to be: self-custody, account reserves, and the one field you must not omit when sending XRP to an exchange.
The XRPL Native DEX: Order Books Since 2012
Most conversations about decentralized exchanges start with Uniswap, which launched in 2018. The XRPL DEX predates it by six years. Since the ledger's genesis, every validator has maintained a Central Limit Order Book (CLOB) — the same order-matching model used by stock exchanges, where buy and sell orders are ranked by price and time and matched against each other without an intermediary.
Trades on the DEX are placed as Offers — XRPL's term for limit orders. An Offer specifies the asset pair and the exchange rate. The ledger matches it against the best available counter-Offer at execution, and any unmatched portion remains on the ledger as a passive order available for future matching.
To hold any token other than XRP, a recipient must first establish a trust line — a bilateral relationship with the token issuer that sets a maximum credit limit. Issued tokens on XRPL are called IOUs (Issued Currencies), and a trust line makes explicit that an IOU is a liability of the issuer, not a native ledger asset. Every trust line an account holds consumes 0.2 XRP in owner reserve.
The DEX has one distinctive routing feature: auto-bridging. When no direct market exists for a given token pair, the protocol automatically routes through XRP as an intermediate asset if that path offers a better rate. This provides implicit liquidity for every pair on the ledger without requiring dedicated markets. Combined with path-finding — the protocol's discovery of multi-hop routes across trust lines — XRPL enables complex cross-currency payments that settle atomically.
The AMM: XLS-30 and the Continuous Auction Mechanism
On March 22, 2024, the AMM amendment (XLS-30) activated on XRPL mainnet, adding Automated Market Maker pools as a native protocol primitive — not a smart contract, but a first-class ledger object operating alongside the DEX order book.
Pricing is algorithmic: like a constant-product formula, the ratio of assets in a pool determines the price at each trade. Critically, the XRPL protocol routes trades across both the AMM and the CLOB simultaneously, selecting whichever combination — or split between them — delivers the best rate for the user.
Liquidity providers receive LP tokens representing their proportional share of a pool. LP token holders vote on the pool's trading fee percentage, introducing decentralized governance over each pool's economics.
The most novel feature is the Continuous Auction Mechanism (CAM). The protocol runs a 24-hour auction slot that arbitrageurs can win by bidding LP tokens. The winner gains access to the pool at a discounted fee rate during their slot, allowing them to capture arbitrage profit more efficiently. Auction proceeds are split: part is returned to the previous slot holder, part is burned. The result is that arbitrage revenue — which on most AMMs flows entirely to the arbitrageur — is partially redistributed back to liquidity providers.
This reduces impermanent loss for LPs, but it does not eliminate it. Volatile pairs can still produce significant opportunity cost relative to simply holding; the CAM reduces the magnitude by recapturing arbitrage revenue, not by removing the underlying price-divergence risk.
Shortly after the March 2024 activation, a routing bug emerged: in complex multi-hop payment scenarios, the DEX payment engine could incorrectly handle routes through AMM pools. Liquidity providers were advised to redeem their LP tokens while validators coordinated a fix. The patch shipped with rippled v2.1.1 and was activated by network vote — a reminder that even native protocol primitives can carry launch-period risk.
NFTs on XRPL: XLS-20
Native NFT support activated on XRPL mainnet on October 31, 2022 — not 2023 as sometimes reported. The NonFungibleTokensV1_1 amendment (XLS-20) added NFTokens: unique, indivisible on-chain objects distinct from the ledger's payment tokens.
Unlike EVM-based non-fungible tokens that live inside smart contracts, NFTokens are native ledger objects. They are minted via NFTokenMint, traded through an explicit offer mechanism (a seller or buyer creates an NFTokenCreateOffer; the counterparty accepts via NFTokenAcceptOffer), and destroyed via NFTokenBurn. Flags set at mint time are immutable — transferability, burnability, and accepted payment currencies cannot be changed after the token exists.
Issuers can embed a transfer fee (royalty percentage of sale price) at mint time, enforced at the protocol level rather than by marketplace contracts. This means the royalty applies across any platform that processes XRPL transactions, not only those that choose to honor it.
Multi-Purpose Tokens (XLS-33): The Institutional Layer
XRPL's original IOU model served DeFi use cases well, but institutional issuers needed finer controls. The MPTokensV1 amendment (XLS-33, known as Multi-Purpose Tokens or MPT) activated on XRPL mainnet in October 2025.
MPTs are a distinct token primitive from trust-line IOUs. Key differences include unidirectional transfers (no rippling between holders), integer arithmetic instead of floating-point, a unique 192-bit issuance ID, and standardized on-chain metadata — including an asset class field that can declare a token as an RWA, stablecoin, or equity instrument.
MPTs carry institutional compliance controls: Require Auth (the issuer must allowlist each holder before they can receive the token), individual or global freeze of balances, clawback authority to recover tokens from any holder if the capability was enabled at issuance, and configurable transfer fees between 0 and 50 percent.
One boundary matters plainly here: these controls apply to issued tokens and MPTs only. XRP itself cannot be frozen or clawed back by any party. There is no issuer of XRP; therefore, no entity can exercise issuer controls over the native asset.
XRPL's tokenized RWA market grew more than 2,200 percent in 2025, from approximately $24.7 million in January to approximately $568 million by year-end. Participants include Archax (UK FCA-regulated), Ondo Finance with tokenized US Treasuries, OpenEden, and the Dubai Land Department's Prypco Mint — one of the first government-backed real-estate tokenization projects on any chain.
Programmability Beyond the Core: Hooks and the EVM Sidechain
XRPL mainnet does not support general-purpose smart contracts — a deliberate tradeoff that preserves throughput and simplicity. Two separate networks address developers who need programmability.
Hooks are small WebAssembly programs that attach to an account on Xahau — a separate XRPL Protocol-based sister chain, not XRPL mainnet. A Hook fires before or after a transaction, enabling on-ledger logic such as spending limits, automated routing, or compliance checks. A Hook can veto a transaction before it executes, a capability distinct from typical L2 smart contracts that can only react after the fact.
The XRPL EVM Sidechain launched on mainnet on June 30, 2025. Built by Peersyst using the Cosmos EVM stack, it provides full EVM compatibility — Solidity, MetaMask, Hardhat — with XRP as the native gas token. It connects to XRPL mainnet via an Axelar bridge and is validated by more than 25 companies. This is a sidechain, not part of XRPL L1. Holding XRP natively in Zelcore means interacting with XRPL mainnet; the EVM sidechain is a separate environment with its own bridging risk and validator set.
How to Hold XRP in Zelcore
Every XRPL address begins with the letter r and is base58-encoded — a format called an r-address. There is one address per account; XRPL does not derive per-token addresses.
Account activation. A freshly generated r-address does not exist on the ledger until it receives at least 1 XRP. This is the base reserve — the minimum balance required to keep an account active. As discussed in the consensus mechanics of Part 1, validators reduced this requirement from 10 XRP to 1 XRP on December 3, 2024 via the fee-voting mechanism. The XRP is not burned; it remains in the account and is recoverable if the account is later closed. It cannot be sent out, however, while required as reserve.
The owner reserve adds 0.2 XRP per ledger object the account holds: each trust line, open Offer, NFT offer, and AMM LP position. An account with five trust lines needs 1 + (5 × 0.2) = 2 XRP in reserve before any XRP is freely sendable.
Transaction fees on XRPL are paid in XRP. There is no second token for gas. Fees are typically fractions of a cent and are permanently burned on execution, making XRP's supply mildly deflationary over time.
The destination tag. When withdrawing XRP from a centralized exchange to your Zelcore wallet, use your r-address alone — a self-custody wallet does not require a destination tag for incoming deposits. The critical case is the reverse: when sending XRP from Zelcore to a centralized exchange or any shared-address service, you must include the exchange's destination tag. This is a dedicated 32-bit unsigned integer field in the XRPL transaction format — distinct from the Memos field — capable of values from 0 to 4,294,967,295. When a receiving account has set the RequireDest flag, the ledger rejects any incoming payment that omits the tag.
Do not substitute a memo for a destination tag. XRPL has both a DestinationTag field and a Memos field; they serve different purposes and are not interchangeable. An exchange that requires a destination tag cannot accept a memo in its place. Omitting a required tag can mean a rejected transaction or, worse, funds credited to an internal limbo account that the exchange cannot automatically route to your balance. The guide on receiving crypto safely in Zelcore covers this pattern for all networks that use routing identifiers.
Self-custody. Zelcore is a self-custodial wallet: you hold the private key directly. No third party can access or freeze your XRP. The corollary is that losing your seed phrase means permanent, irrecoverable loss of access. Back it up securely before funding the account.
Key Takeaways
- The XRPL native DEX (CLOB-based) has run continuously since 2012, predating Ethereum by three years and making it one of the oldest decentralized exchanges in existence.
- The AMM (XLS-30, live March 22, 2024) routes alongside the order book. Its Continuous Auction Mechanism reduces — but does not eliminate — impermanent loss for liquidity providers.
- XRPL supports native NFTs (XLS-20, live October 31, 2022) and institutional Multi-Purpose Tokens (XLS-33, live October 2025), with freeze, clawback, and allowlist controls at the protocol level — none of which can be applied to XRP itself.
- Hooks (on Xahau) and the EVM Sidechain (launched June 30, 2025, via Axelar) are separate networks from XRPL mainnet, each with distinct trust assumptions.
- Holding XRP in Zelcore requires a 1 XRP base reserve to activate a new address; sending XRP to an exchange requires the correct destination tag — a dedicated numeric field, not a memo — or deposits may be lost.
