🚧 Under construction — exhibits and records are being built.

XRPL MUSEUM

Project Directory of the XRP Ledger

How the XRPL ecosystem fits together

A plain-language map of the pieces you will see in this museum

The XRP Ledger is a public blockchain. Anyone can open an account, issue a token, mint an NFT collection, or run software on top of it. This page explains the building blocks in everyday language and points you at real exhibits already in the museum — drawn from the ledger snapshot, each project's own xrp-ledger.toml or website, and public X handles those projects published. Nothing here is financial advice.

1. Accounts & wallets

An account is an address on the ledger (it starts with r…). A wallet is the app you use to control that account. The museum lists issuer accounts on every project page and groups related accounts under Builders.

Example: open the TextRP builder — Confirmed wallets are tied together by on-ledger proof (RegularKey, SignerList, authorized minter, or a two-way xrp-ledger.toml).

2. Issuers

An issuer is the account that creates a fungible token or an NFT collection. For tokens, holders open a trustline to that issuer. For NFTs, the issuer address plus a taxon (a collection id number) uniquely identify the collection.

Example: Ripple USD (RLUSD) is issued by Ripple's TOML-listed account rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De. NFT example: &tag identities is issuer raSsG8F6KePke7sqw2MXYZ3mu7p68GvFma taxon 0 — named from andme.org's own site and present in the ledger snapshot (~64k NFTs).

3. Trustlines

A trustline is your account saying “I am willing to hold this issued token.” It locks a small XRP reserve until you remove it. Always copy the issuer address from the project’s own site or TOML — tickers collide.

Example: the TXT token page (TextRP) shows holder counts read straight from the ledger. Project pages also warn when a name looks like a possible copycat of a major brand.

4. Taxons & NFT collections

Every XRPL NFT belongs to one issuer and one taxon. Human names come from the project's own site or TOML when we have them; otherwise the museum shows the raw issuer+taxon. A collection is Confirmed when that pair is in our ledger snapshot. Outbound “view on marketplace” links use only the issuer and taxon — we do not republish marketplace scrapes as our name database.

Example: browse the NFT collections wing, or open XRPL Awesome Possum / Schmeckles and follow taxon links from their Connections maps.

5. AMMs & the DEX

The ledger has a built-in decentralized exchange (order books) and automated market maker (AMM) pools. Trading front-ends are windows onto those pools — the balances live on-ledger.

Example: the Exchange Court lists AMM pools by the two assets they swap, read from the ledger snapshot.

6. Wallets, explorers & infrastructure

Apps help people use the ledger: wallets sign transactions, explorers show accounts and NFTs, and some projects run validators. The museum's Services hall lists tools with links to each project's own site. Validator claims are taken from the project's published xrp-ledger.toml when present.

Example: Services includes infrastructure such as Anodos Finance (TOML lists XRPL validators). Wallet and explorer entries link out to each project's site — the museum does not host their apps.

7. Builders (creators & teams)

Builders are who the museum means by “who uses the ledger”: the creators and teams behind issuers. A builder page shows wallets → tokens → NFT taxons → project-published X/web, with Confirmed / Not certain styling. X and website columns come from each project's own TOML or site.

Example: start at Builders, then open TextRP, Ripple, or OpulenceX and scroll the Connections map.

8. How to read a Connections map

Solid edges and the green Confirmed badge mean on-ledger proof or a two-way TOML link. Dashed amber and Not certain mean a weaker hint (funding payment, or a self-described X/web link). We never invent a link. Trade deep-links (when shown) are issuer+taxon URLs only.

Concepts: xrpl.org docs. Museum examples link to pages built from the validated ledger snapshot plus each project's own TOML, website, or public X — not from marketplace name scrapes.