With Lesson 1
The stick-figure story.
This long walk goes with Lesson 1. It does not replace the numbered path. If you are just starting, open Lesson 1 first.
Table of contents
The daily sky memo.
A memo is a small note attached to an XRP Ledger transaction. Once that transaction is validated, the note is public and permanent. #XRPEducationMonth
Each day, Live Sky writes a compact snapshot of the sky at 0h UT (midnight Universal Time) as a memo of type astrobear/ephemeris/v1. The memo holds the date and the packed planet positions, to the arc minute. A memo has a tight size limit, so this is a compact record, not a full chart file. It holds no personal data and nothing about anyone's birth.
Why it matters: that memo is a tamper-proof, timestamped public record. Anyone can open the transaction, read the memo, and compare those numbers with the decoded day page on Live Sky. This is the first daily ephemeris on the XRP Ledger. It shows how the ledger can work as a notary, a way to anchor a public record, not only a way to send payments.
How to verify the first one yourself:
- 1
Open the first mainnet transaction on XRPScan.
- 2
Find the memo. Check the date and the packed sky record.
- 3
Open the matching day on Live Sky and compare the positions.
Mainnet is used only for this daily ephemeris memo. Learners practice writing memos on testnet, in the Lesson 3 and the arcade. The Sky lab also shows a practice snapshot whose second memo is a SHA-256 hash, so you can confirm the text was not altered.
Hello, traveler.
Before we open the notebook, meet your guides, and the bear who asked them to give you a tour.
What this walk is
The XRP Ledger is a shared, public ledger. It keeps track of balances and the transactions that change them, without one person being in charge of the book.
This page is a fan-made story, created for #XRPEducationMonth 2026. We'll use plain words, then give you comics and games if you want to go deeper.
Every fact here is written to match xrpl.org. We won't talk about prices, trading tips, or where to buy anything.
That's Astro Bear, popping in for a cameo. The stick figures are your main guides. The bear just likes a good story, and a good riddle.
A notebook everyone shares.
A ledger is just a careful record. The XRP Ledger is one the whole network can check together.
Ledger versions
Each finished page is called a ledger version, or just a ledger. It holds three things: the current state (like balances), the transactions that were applied to the previous ledger to get here, and some metadata, including a number called the ledger index, and a fingerprint of the page's contents.
The shared rules are the great architect of this notebook. They shape every page, and no one person is in charge of the book.
Ledgers are numbered in a line, each one building on the one before it, all the way back to the start. When the network agrees a page is right, that ledger is validated. Then it is final. Nobody can quietly rewrite it later.
Unlike some blockchains, each new ledger carries the current state with it. You don't have to collect every old page just to know what's true right now.
How they all agree.
If nobody is the teacher, who says the page is finished? Validators do it by coming to consensus.
Consensus, in plain words
The XRP Ledger does not use mining, and nobody is paid a prize for finishing a page. Validators propose, compare, and revise until they share the same result.
On this ledger, everyone meets on the level and parts on the square: the same rules apply to every account and every validator. Nobody gets a private shortcut.
A little trust goes a long way: each server chooses a list of validators it expects to behave honestly most of the time, and that shouldn't all cheat in the same way. If too many of them are missing or misbehaving, the network waits instead of writing down something wrong.
The design puts correctness and agreement first, then forward progress. A paused notebook is safer than a messy one.
Try it: help them agree
Tap each validator so they raise a hand. When all five agree, the next ledger can close. In real life, servers need about 80% of their trusted validators to agree, not all of them.
A validator watching the network.
0 of 5 validators have raised a hand. Tap the rest so they can agree.
The fee that vanishes.
If sending a note is easy, what stops a prankster from filling the notebook with junk?
The transaction cost
Every signed transaction has to say how much XRP to destroy as its transaction cost. The XRP is irrevocably destroyed. It is not paid to validators or to any other party.
The network's minimum can increase when load is high, which makes it very expensive to overload the ledger on purpose, or by accident. That cost is a square deal: the same rule, checked the same way, for every transaction.
The ledger does exactly what the signed transaction says, including the fee. That's why the amount in the Fee field is the amount that disappears.
Try it: watch a fee vanish
Tap the spark. It stands in for a tiny XRP fee.
Your locker on the ledger.
An account is a place that can hold XRP and other things. It needs a small reserved amount to exist.
Reserves, gently
You can't send the reserved XRP away to someone else, but it can be used to pay those tiny transaction costs. One way to look at it: the reserve pre-funds your locker so it can keep paying fees.
A level and a plumb are quiet reminders: every locker is measured by the same reserve rules, on the level, no matter who it belongs to.
If an account goes below its reserve, it still exists. It just can't send XRP to others, or add new items that would raise the reserve, until it holds enough again.
Reserve amounts can change over time when validators vote on fee settings. The numbers above are today's Mainnet values, as documented on xrpl.org.
LOCKER 589
Ticket numbers in a line.
How do you stop the same payment from happening twice? You take a number, and you use it only once.
Sequences are picky, on purpose
A transaction from an account is only valid if its Sequence is exactly 1 greater than the last one that account sent. (There's a special tool called a Ticket for some advanced cases, but the everyday rule is "next number, please.")
Together with consensus putting transactions in a final order, sequence numbers help the ledger solve the double-spend problem without a central cashier.
The fee, the reserve, and the sequence number are the ledger's working tools. They keep the book in order.
A proposed transaction starts as a rough ashlar: a stone that isn't finished yet. When the network agrees and the ledger is validated, it becomes a perfect ashlar: measured, placed, and unchangeable.
A riddle from the bakery line
I go up by one, and never twice. Skip me and the line won't move. What am I?
A sequence number. Your next transaction has to take the very next ticket: no doubles, no skipping.
A new page, every few seconds.
The notebook doesn't wait around. New ledger versions usually close about every 3 to 5 seconds.
Watch the pages turn
Why "a few seconds" matters
Because the whole network has to agree on each page, the XRP Ledger is built for steady, shared progress, not for rushing faster than consensus can be careful.
When a ledger is validated, its contents can never change. The validated ledgers before it are history. The network is already considering transactions for the next one.
Tokens and trust lines.
XRP lives in the ledger itself. Other tokens work a little differently: they sit on trust lines.
Issued tokens, carefully
Anyone can issue a token with a currency code they choose. That's why the issuer matters, and why the ledger tracks tokens on trust lines instead of mixing them all together.
A trust line is a bit like a cable tow: you choose how far you're willing to go with an issuer, by setting a limit on how much of that token you're willing to hold.
XRP itself does not use a trust line. It is the ledger's native asset, and it can be sent directly from account to account.
This walk won't send you toward any particular token or issuer. We're only explaining how the tool works.
A marketplace built into the notebook.
The XRP Ledger has a decentralized exchange in the protocol itself, not a shop we're sending you to.
The built-in DEX, at a high level
Yes. An offer is a limit order recorded on the ledger. If a matching offer already exists at a good enough rate, it can be filled right away. If not, the leftover offer can sit in the ledger until a later page matches it, or until it's canceled. Offers match on the level: the same matching rules, for everyone.
Because offers only settle when a ledger closes (about every 3 to 5 seconds), the design is meant for careful matching, not for racing the clock.
We're showing you that this tool exists in the protocol. We are not asking you to use it, and we won't point you to any particular token, project, or venue.
Did it stick?
Three quick questions. No grades, no pressure: just a chance to see what you caught.