About
An independent field guide to Pearl.
Pearl Codex explains Pearl from the bottom up: what the bytes are, what the math does, and why. It is written for curious people with no crypto background, and checked like a reference.
What this is
Think of it as learnmeabitcoin.com, but for Pearl (PRL). A beginner guide tells the story in plain English. The codex then goes byte by byte: keys, hashes, transactions, the 108-byte header, and the matrix multiplication that mines each block. Tools and the arcade let you poke at all of it.
Independence
Pearl Codex is independent and not affiliated with Pearl Research Labs, the company that builds Pearl's reference software. Nobody paid for it, and it holds no position on price. It is educational content only; nothing here is financial advice.
How pages are verified
Every Pearl-specific claim was checked against Pearl's source code at v1.5.2
(commit 024e475) and against the live chain, on 2026-10-20. Where the whitepaper and the
code disagree, the code wins, and the page says so.
- Numbers come from one file of facts, so a value changes in one place.
- Byte views decode real mainnet blocks and transactions with the same parsers the tools use, and check their own hashes at build time.
- Every page lists its sources and the exact source files that implement it, linked at the verified tag.
- Toy numbers are always labeled as toy or scenario.
Live figures
Pages show a dated snapshot of the chain (block 130,827, Pearl Blockbook and PRLScan, 2026-10-20). After a page loads, your browser asks PRLScan once for the latest figures. That is the only request the site makes to anyone else. If it fails, the snapshot stays.
Privacy
No accounts, no cookies, no analytics, no tracking. Your theme, reduce-motion choice, finished pages and quiz scores are kept in your own browser's storage and never sent anywhere.
Report a mistake
Found something wrong or out of date? Every page has a “Report a mistake” link that opens a prefilled issue, or you can email corrections@pearlcodex.com. Please include the page, what looks wrong and, if you have one, a source. Corrections are checked against the code before they go in.