Plain-English definitions for XRPL terms and xrpldashboard methodology concepts. Each entry links to the page where the concept is most visible in context.
A change to the XRPL protocol that activates only when 80% of trusted validators support it for two consecutive weeks. Pending amendments are visible on /amendments before they go live. Once activated, an amendment cannot be reverted.
The process by which XRPL validators signal support for or against a pending protocol change. Each validator broadcasts its position per ledger; the 80%-for-two-weeks threshold triggers activation. Votes are on-ledger and publicly visible.
Automated Market Maker. An XRPL-native DEX protocol that prices token pairs using a constant-product formula (x × y = k). Liquidity providers deposit both sides of a pair; traders swap against the pool. Each pool has its own account on the ledger, enabled by the AMM amendment (XLS-30).
A specific trading pair managed by an AMM account on XRPL. The pool account holds both assets and prices swaps using a constant-product formula. Pool state — reserves, LP token supply, trading fee — is all readable on-ledger.
A weekly XRPL payment from the dashboard’s anchor account (rL2yMECEyUT94pLDrAcetMNMG1H4xqpNWQ) to its ops account, with the snapshot chain’s current chain_root embedded in the memo field. Creates an immutable public record that cannot be backdated: even if the site were compromised, the on-ledger record would remain.
The process of ingesting historical ledger data after a gap or from a new starting point. Backfill coverage is disclosed where it applies: the /nfts historical range starts at ledger 103,252,853 (2026-04-01); earlier history is not yet available. Residual holes are quantified and published, not hidden.
The permanent deletion of an NFT from the XRPL. Once burned, the token ID is retired and cannot be recreated. Burn events appear in the /nfts activity feed.
A hex string that summarizes the entire signed snapshot chain up to the current day. Computed by hashing successive daily snapshots together; a change in any past snapshot would invalidate the root. Published in chain.json and anchored on-ledger weekly so a stranger can verify the record without trusting the site.
CLAIMS.yaml — the site’s public record of every meaningful claim on every page: what data source backs it, which Layer 2 audit rules apply, and what would break it. Each claim has a permanent URI at /claims/xrpl.‹domain›.‹series›. Machine-readable index at /claims/index.json.
An XRPL account whose private key is kept offline. Exchanges typically use cold wallets to hold the majority of customer funds, keeping only a smaller hot wallet online for active settlement. Known cold-wallet balances are tracked on /cold-storage.
The XRPL’s built-in decentralized exchange, where accounts place limit orders that settle on-ledger. Older than AMM pools; offers match and cross in the order book without a third-party intermediary. Trading on the DEX requires no account approval beyond holding the relevant trust lines.
Decentralized Identifier. An XRPL object (XLS-40) that lets accounts publish a self-sovereign identity document on-ledger. The DID document can attest to external credentials without relying on a central registry.
An XRPL object that holds XRP until a time condition or cryptographic condition is met. Ripple uses escrow to release its corporate XRP allocation on a scheduled basis — those releases are visible as large on-ledger transactions.
A per-surface promise about how stale the data on a given page can be, stated as a maximum cache TTL. “Live” means streamed directly from the ledger with no cache layer; “60s” means the query result is cached for up to 60 seconds. The full table of freshness contracts is on /methodology.
An XRPL issuer that creates trust-line balances redeemable for an off-chain asset. A bank or stablecoin operator that issues tokens on XRPL is acting as a gateway. RLUSD is issued by Ripple acting as a gateway on both XRPL and Ethereum.
An XRPL account whose private key is online and used for frequent transactions. Counterpart to a cold wallet; exchanges expose hot wallets to more operational risk in exchange for immediate settlement liquidity.
The XRPL account that created a token. Tokens on XRPL are identified by the pair (currency code, issuer address); the same currency code from two different issuers represents two distinct tokens. The /tokens registry lists issuers with domain attestation where available.
Each “ledger” is a block in XRPL’s history: an ordered set of transactions that validators agreed on, plus the resulting account state. A new ledger closes every 3–5 seconds. The XRP Ledger has been running continuously since January 2013.
A sequential counter identifying each closed ledger. Ledger 1 is the genesis ledger (January 2013); the index increments by one per close. Ledger indices are used throughout the site to anchor data to specific points in time.
The Lending Protocol amendment that adds a native lending market to XRPL — collateralized borrowing and lending without a third-party custodian. Currently in voting phase. /lending tracks its amendment status.
An open standard for connecting AI assistants to live data sources. xrpldashboard’s MCP server lets AI tools query XRPL data directly and receive proof-annotation envelopes rather than raw numbers. The server is free, public, and listed in the Anthropic and Glama directories.
The act of creating an NFT on XRPL under the XLS-20 standard. The NFT is minted into the creator’s account with a unique 256-bit token ID. Mint events appear in the /nfts activity feed.
Multi-Purpose Token. XLS-33 standard for fungible tokens on XRPL with a smaller on-ledger footprint than trust-line tokens. Designed for high-volume issuers: each holder only requires a single ledger object rather than a trust line. The /mpts page tracks all active MPT issuances.
Non-fungible token on XRPL under the XLS-20 standard, enabled by the NonFungibleTokensV1_1 amendment. Each NFT has a unique 256-bit identifier. Mints, burns, offers, and sales are tracked on /nfts.
An on-ledger order placed by an account to trade one asset for another at a specified exchange rate. Offers rest in the DEX order book until filled, cancelled, or expired. Distinct from NFT offers (which are sale listings under the XLS-20 protocol).
An XRPL object (XLS-47) that lets on-ledger accounts publish price feeds or other external data. Oracles enable smart contracts and AMMs to consume real-world data without leaving the ledger.
A disclosure that a dataset doesn’t cover the full range or population a reader might assume. Example: /nfts discloses its residual holes (~129K ledgers not backfilled) rather than presenting an artificially complete number. Scope notes appear wherever coverage is partial.
Permission Domain (XLS-80). An XRPL amendment enabling permissioned DEX and AMM pools where participation is restricted to a defined set of accounts. Designed for regulated token trading where counterparty eligibility matters.
A structured wrapper around every MCP tool response: {data, proof:{source, as_of, freshness_contract, methodology_url, claims_ref, cross_check_status, honest_partial, scope_note}}. Lets a machine verify provenance without trusting the presenter. Full schema at /openapi.json.
The minimum XRP balance an XRPL account must hold. Currently 10 XRP base reserve plus 2 XRP for each object (trust line, offer, NFT page, etc.) the account owns. Reserve requirements prevent ledger spam by making it costly to create unbounded on-ledger objects.
The open-source reference implementation of the XRPL protocol, written in C++. Running your own rippled node gives you a sovereign data source — you can verify every fact against your own copy of the ledger without trusting a third party. xrpldashboard’s live data comes from its own rippled node on the Lenovo box.
Ripple’s USD-pegged stablecoin, issued on both XRPL and Ethereum. Supply and mint/burn events on this site are computed directly from gateway balance RPCs (XRPL) and Ethereum contract state — not from a third-party price API.
A token on XRPL whose value is tied to an off-chain asset: a currency, commodity, real estate instrument, or security. XRPL’s trust-line model makes RWA issuance straightforward; attestation quality varies by issuer. /rwa lists verified RWA tokens with issuer attestation status.
A disclosure attached to a data point that limits its interpretation. Example: “Historical range is 2026-04-01 to present; earlier data not available.” Scope notes appear wherever a number doesn’t cover the full range a reader might assume. They are not disclaimers — they are precision statements.
A daily database export signed with Ed25519, chain-linked to the previous day’s snapshot. The signature proves the data hasn’t changed since it was published; the chain linkage proves the order of publication. Snapshots are free to download and verify independently.
The property of a data source that lets you verify it independently without trusting a third party. Own-node data (rippled) is sovereign; data relayed through a third-party API is not. xrpldashboard’s data sovereignty tier is green for metrics derived from its own rippled node.
A traffic-light rating for each data source. Green: own rippled node — independently verifiable. Yellow: public XRPL RPC — on-chain but relayed through a third party. Red: third-party derived — trust us or check the original source yourself. Each claim on /claims carries its tier.
An accounting relationship between two XRPL accounts that allows them to hold a non-XRP asset. Each trust line has a credit limit set by the holder. Holding a token on XRPL means holding a trust-line balance with the issuer.
The combined value of assets deposited in AMM pools or lending protocols, measured in XRP or USD at current market price. TVL is sensitive to the XRP/USD rate used — the rate source is disclosed on every surface that displays TVL.
The set of validators a rippled node trusts to reach consensus. The XRPL Foundation publishes a recommended UNL. Two nodes with substantially non-overlapping UNLs could theoretically disagree on ledger state, so UNL alignment is a safety property of the network.
A rippled node that participates in the XRPL consensus process by voting on which transactions to include in each ledger. Validators on the default Unique Node List (UNL) carry weight in the consensus vote. Validators do not receive a reward — they run as a public service or to protect their own connectivity to the network.
An account making an unusually large XRP transfer. On /whales, the threshold is 100,000 XRP per payment. The label is descriptive — it identifies transaction size, not trading intent or account status.
The native currency of the XRP Ledger, used to pay transaction fees (which are destroyed, not paid to validators), fund reserve requirements, and serve as a bridge asset in DEX trades. XRP balances require no trust line — every XRPL account holds XRP natively.