Understanding XRP & The XRP Ledger
A plain-English guide to XRP and the XRP Ledger — how consensus works, why fees are destroyed, what trust lines are, and how native NFTs make projects like Fuzzy possible.
A plain-English guide for people who keep hearing about it — and why it's the reason Fuzzy works the way it does.
Start Here: Two Different Things
Almost every argument about XRP online comes from people mixing up two things that aren't the same.
The XRP Ledger (XRPL) is a blockchain. A public, open-source database that anyone can use, launched in 2012.
XRP is the digital asset that lives on it — used to pay fees, move value, and bridge between currencies.
Ripple is a separate, private company that builds payment products using the XRPL. Ripple did not invent XRP out of thin air and does not control the ledger. It's a large holder and a major contributor, but the network runs without it.
Getting this straight is genuinely half of crypto literacy. The ledger is public infrastructure. The company is a business that uses it.
How It Actually Works
There is no mining
Bitcoin uses proof of work: computers race to solve puzzles, burning enormous electricity, and the winner writes the next block. Ethereum uses proof of stake: validators lock up capital as collateral.
The XRPL does neither.
Instead, every server picks a list of validators it trusts — a Unique Node List. Those validators propose which transactions should go into the next ledger, then revise their proposals over several rounds until a large enough share agree. When they do, the ledger closes and consensus is declared.
Consensus continues unimpeded as long as fewer than 20% of trusted validators are faulty.
The practical consequence: confirming a transaction doesn't require what the XRPL's own documentation calls "wasteful or competitive use of resources." No mining rigs. No energy arms race. Just agreement among independently operated servers.
Fees are destroyed, not paid
This one surprises people.
On most blockchains, your transaction fee goes to a miner or validator as payment. On the XRPL, the fee is irrevocably destroyed — removed from existence permanently. Nobody collects it.
The base cost is 10 drops, which is 0.00001 XRP. A fraction of a fraction of a cent. It rises temporarily if the network gets busy, which is precisely the point: the fee exists to make spam expensive, not to pay anyone.
Because every transaction burns a tiny amount, the total supply of XRP only ever decreases. No more can ever be created.
Worth separating that from circulating supply, which is a different number and which has been increasing as escrow releases unlock. Total supply shrinks; the amount available in the market has been growing. People routinely blur these two to make whichever point they're arguing.
Reserves
To keep the ledger from filling with abandoned junk, accounts must hold a small amount of XRP they can't spend:
- Base reserve: 1 XRP to have an account at all
- Owner reserve: 0.2 XRP per object your account holds — trust lines, offers, NFT pages
These are set by validator vote and have changed over time.
Supply
100 billion XRP were created at the very beginning. All of it, at once. None has been mined since, and none ever will be.
Of that, the founders gifted 80 billion to the company that became Ripple and retained 20 billion themselves. In 2017 Ripple placed 55 billion XRP into escrow — 55 contracts of 1 billion each, expiring monthly — so that supply entering the market became predictable rather than arbitrary.
This is a real and fair criticism people raise about XRP, and it deserves a straight answer rather than a defensive one: a large share of supply started concentrated. The escrow was designed to address it. Whether it addresses it enough is a legitimate debate, and anyone who tells you the question is settled is selling something.
The Part Most People Miss: It's Not Just A Payments Coin
The XRPL has features built directly into the protocol that other chains need smart contracts to imitate.
A built-in exchange
The XRPL has had a decentralized exchange inside the ledger itself since 2012 — years before "DeFi" was a word. Trading isn't an app running on top of the chain. It's a native function of the chain.
Trust lines
To hold a standard issued token, your account explicitly opts in by creating a trust line to that issuer.
It feels like an extra step. It's actually a security feature: nobody can force an unwanted token into your wallet, which is a genuine, ongoing problem on chains without this design.
(One nuance, since this gets stated too absolutely: the newer Multi-Purpose Token standard is now live and uses a different issuance model that doesn't rely on trust lines. Trust lines govern classic issued tokens, not literally everything that isn't XRP.)
This is also why "David Schwartz set a trust line with Fuzzy" was meaningful news. A trust line is a deliberate, signed act — not something that happens passively, and not something anyone can do to you.
That one is on the ledger too. On 3 May 2026 at 04:25:02 UTC, in ledger #103,971,664, the account publicly known as David Schwartz — rHzWtXTBrArrGoLDixQAgcSD2dBisM19fF — submitted a TrustSet to the Fuzzybear issuer, with a limit of 320,930,450,547 FUZZY. Essentially the entire supply.
One honest caveat, because it matters: a trust line means an account is willing to hold a token. It does not prove the account holds any. The two get conflated constantly. What the ledger shows is a deliberate opt-in by a named individual — which is genuinely notable — not a purchase, and not an endorsement.
Automated market makers
The XRPL supports AMM pools natively, letting anyone provide liquidity and earn fees — again, protocol-level rather than bolted on.
NFTs without smart contracts
Under the XLS-20 standard, NFTs are native ledger objects, not smart contract entries.
Minting, transferring, and burning are built-in operations — NFTokenMint, NFTokenCreateOffer, NFTokenBurn. Storage is efficient by design: up to 32 NFTs owned by one account are packed into a single page object, which keeps reserve costs low. (In practice pages split by ID sorting and rarely stay full, so 32-per-page is the best case rather than the norm.)
Issuers can also set rules permanently at mint time, including a transfer fee — a royalty of 0% to 50%, fixed at mint and enforced by the ledger itself rather than by a marketplace's goodwill. The enforcement covers on-ledger offers; a private off-ledger handoff sits outside it.
If you've followed NFT royalties on other chains, you know how much that last sentence matters.
Why This Matters For Fuzzy
Every design choice above shows up in something Fuzzy does. This is the part where the technology stops being abstract.
Burning is a real operation, not a workaround
The Fuzzycards burn portal asks you to destroy an NFT to claim physical cards. On the XRPL, NFTokenBurn is a native ledger instruction. The asset is genuinely, verifiably gone — not sent to a dead wallet that technically still holds it.
That's the difference between a burn and a burn-flavored gesture, and it's why "burn to claim" is clean here rather than clever.
The economics only work because fees are near zero
Fuzzy has 10,930 holders. Fuzzycards involved thousands of NFTs across four collections. Now add a burn event where hundreds of holders each destroy an NFT and claim physical goods.
On a chain with meaningful gas fees, the transaction costs alone could rival the value of a booster box, and the burn portal would be economically absurd. At 0.00001 XRP per transaction, it's a rounding error.
Cheap fees aren't a bragging point. They're the precondition that makes the entire product possible.
Native NFTs mean no contract risk
There is no Fuzzycards smart contract that can be exploited, drained, or bricked, because there is no smart contract. The NFTs are ledger primitives governed by the same rules as everything else on the XRPL.
Fewer moving parts, fewer ways to fail.
Enforced royalties
Because XLS-20 lets issuers set a transfer fee at mint, a project can earn on secondary sales at the protocol level. Across four Fuzzy collections with roughly 3.5m XRP in lifetime volume, that's an actual, durable revenue mechanism — one that funds continued building rather than depending on marketplaces choosing to honor royalties.
You can verify the token yourself
Everything above is theory until you check it. So here is the $FUZZY token as the ledger actually reports it — go look for yourself rather than taking anyone's word for it.
Issuer account: rhCAT4hRdi2Y9puNdkpMzxrdKa5wkppR62
Currency code: 46555A5A59... — hex, which decodes to the ASCII letters FUZZY
Verified domain: fuzzyxrp.com, with the account name registered as "Fuzzybear (Issuer)"
Issuer account created: 23 January 2025
Total issued: 320,929,807,851 FUZZY
That last figure is worth pausing on. The stated supply is 321 billion, and the ledger reports 320.93 billion outstanding — about 99.98% of it. The roughly 70 million difference is supply that has been sent back to the issuer and retired.
The claim and the ledger agree. That is the entire point of a public blockchain, and it takes about thirty seconds to confirm.
And one flag matters more than all the others: the issuer account has its master key disabled.
In plain terms, that means nobody can sign transactions from the issuing account anymore. No new FUZZY can be minted. The supply is not "promised" to be fixed — it is structurally incapable of increasing, and that constraint is enforced by the ledger rather than by anyone's good intentions.
This is the standard "blackholed issuer" pattern on the XRPL, and it is the single most useful thing to check before trusting any XRPL token. Plenty of projects say the supply is fixed. Far fewer have given up the keys.
The lore is on-chain too
Fuzzy's origin story is a real wallet activated in 2013, and a real order placed on January 1, 2014 — 1 XRP for 1 BTC.
And this is where learning to read a block explorer stops being academic, because you can check the whole thing yourself.
The FuzzyBear account is rjh37UraJGNsxTLuXRQVCT7wvhzfVF4ig, activated 21 February 2013 — seven weeks into the ledger's public history — and funded with 50,000 XRP by an OpenCoin account that had itself been activated by Ripple's own genesis account the day before.
Ten months later, on 1 January 2014 at 13:28:30 UTC, it submitted an OfferCreate in ledger #4,191,772: offering 1 XRP, asking 1 BTC. The fee was 0.000012 XRP. The transaction is still there.
At the time, that was an absurd price — which is precisely the point. It was never going to fill. It was a statement about where its author thought XRP was heading, written into a permanent public record and left there.
That's a meme coin whose foundational myth is not a story at all. It's a ledger entry, funded one hop from the company that built the chain, and anyone can read it in about a minute.
Most projects invent an origin. This one has a receipt.
The Honest Caveats
Any education section worth trusting includes the parts that aren't flattering.
Concentrated supply. As above — a large portion started with one company and its founders. Escrow made releases predictable, not decentralized.
Validator concentration. UNL-based consensus is fast and efficient, but critics reasonably argue that trusted-validator lists are less permissionless than mining or staking.
Regulation moves. XRP's legal status has been contested and has shifted over time. Anything you read about it — including this page — can go out of date. Check primary sources.
Some Fuzzy figures are verified; others aren't. The issuer address, currency code, issued supply, disabled master key, the FuzzyBear account's activation and funding chain, the January 2014 transaction, and the David Schwartz trust line were all read directly from the XRP Ledger and are independently checkable — every one is linked above. The holder counts and NFT trading volumes come from the project and from marketplace pages; treat those as reported rather than verified.
None of this is investment advice. Understanding how a technology works tells you nothing about what an asset will be worth. Those are unrelated questions, and conflating them is how people get hurt.
Quick Reference
| Ledger launched | 2012 |
| Consensus | Trusted validator (UNL), no mining |
| Fault tolerance | Up to 20% of validators |
| Base transaction cost | 10 drops (0.00001 XRP), destroyed |
| Base account reserve | 1 XRP |
| Owner reserve | 0.2 XRP per object |
| Total supply created | 100 billion, at genesis |
| Placed in escrow (2017) | 55 billion (55 × 1B, monthly) |
| Total supply direction | Decreasing (fees burned, no issuance) |
| Circulating supply direction | Increasing as escrow unlocks |
| Native DEX | Yes, since 2012 |
| Native AMM | Yes (XLS-30, live 2024) |
| Native NFTs | Yes (XLS-20, live 2022) |
| NFTs per storage page | Up to 32 |
| NFT transfer fee range | 0%–50%, fixed at mint |
| Public ledger history from | Ledger 32570, January 2013 |
Sources: XRPL.org documentation — What is XRP, Transaction Cost, Reserves, Consensus Protocol, NFTs. Figures current as of August 2026 and subject to change by validator vote.