XRPL

Everything you need to know about XRPL compliance — XRP legal status, native features, and custody implementations.

🌍 Legal status 🏢 Companies 🔐 Custody 🌊 Payments ⚡ Technology

XRPL EVM Sidechain

XRPL EVM Sidechain is an EVM-compatible blockchain bridged to XRPL Mainnet. It allows Solidity smart contracts to run while using XRP as gas.

Same regulatory treatment as EVM-based chains (Ethereum, Polygon). Bridge introduces additional consideration: bridged XRP is wrapped (eXRP) — custody of bridge = IOU/gateway model on XRPL side.

Bridge between XRPL Mainnet and EVM Sidechain involves a witness server network. Wrapped XRP (eXRP) on EVM side = IOU-like exposure to bridge operators. Custody analysis required.

Native XRPL Features

Feature	Standard	Status	Regulatory note
Native DEX	`Protocol`	Live	Front-end may trigger CASP
AMM	`XLS-30`	Live (2024)	Liquidity pools — CASP analysis for front-end
NFT	`XLS-20`	Live (2022)	Broker mode = non-custodial
MPT	`XLS-33`	Live (2025)	Activated on Mainnet 2025 · no explicit MiCA category — case-by-case
RLUSD	`—`	Live (2024)	EMT reference on XRPL
Payment Channels	`Protocol`	Live	No custody — no CASP
Escrow	`Protocol`	Live	No custody if time-locked
IOU / Trust Lines	`Protocol`	Live	Gateway = custodial
Checks	`Protocol`	Live	No custody

Upcoming amendments — what compliance should watch

Selected XRPL protocol amendments in development or proposal. Each row notes what the change does + why a compliance team should care.

Feature	Standard	Status	Regulatory note	Compliance impact
Permissioned Domains	`XLS-46`	Testnet	Credential-based gating at protocol level — issuer can define a 'domain' of KYC-verified accounts. On-ledger compliance gating without an off-chain whitelist.	Native KYC primitive. Reduces reliance on app-layer allowlists. Material for MiCA Art. 75 + Travel Rule scenarios where regulated transfers must be domain-restricted.
Lending Protocol	`XLS-65`	Testnet	Native single-asset lending pools on XRPL. Borrowers, lenders and a vault primitive — interest rates managed by protocol-level rules.	Lending = regulated activity in most juri (CASP lending scope under MiCA, MiFID II for tokenised debt). Front-end likely needs licence; protocol-native lending raises decentralised-DeFi questions.
Single Asset Vault	`XLS-72`	Proposed	Generic vault primitive for tokenised funds, tranches, and structured products. Issuer creates a vault holding one asset type; share tokens issued represent claims.	Direct enabler for tokenised RWA + tokenised funds. Likely captured by Prospectus Reg. + AIFMD if fund-like. DLT Pilot Regime applicable for security-token venues.
Permissioned DEX	`XLS-70`	Proposed	DEX order books restricted to participants holding a specific credential (e.g. KYC-verified). Combines XRPL's native order book with Permissioned Domains gating.	Allows regulated venues (MiFID II MTF / MiCA CASP exchange) to operate a permissioned trading layer on-ledger. Substantial alignment with MiCA Art. 76+.
Cross-Chain Bridge	`XLS-38d`	Voting	Native protocol bridge primitives (witnesses, claims, attestations) for moving assets between XRPL Mainnet and sidechains (notably the EVM Sidechain).	Bridged assets = wrapped IOU on the destination chain. Custody analysis needed on both sides. Witness server set may itself qualify as a CASP service depending on architecture.

Start XRPL Compliance Check →