Zero-trust · at-home self-custody
Plebum Dominium
(PLAY-boom doh-MIN-ee-oom)
Absolute Ownership by the Common People
You obtain sovereignty with Bitcoin only by owning the keys. This guide will show you how to safely and privately create those keys.
They are born on Tails OS — The Amnesic Incognito Live System, a free, open-source USB Linux you download yourself. It boots, runs with the network off, and forgets the session on shutdown.
Casino dice. A 2-of-3 native SegWit wallet. Titanium plates in three places. Hardware signers are optional later — and only as multi-vendor tools, never as the birth of the key. Built so no company, firmware, or factory has to outlive you.
One minute
Keys on your own terms
A quiet introduction. Play it at home. Then open the presentation when you are ready to work.
This site is online
House rules
- No photos of seeds, plates, or word-bearing screens.
- No seed on a machine that had a network up in that session.
- Never load two seeds in one Tails OS boot.
- Do not create or unlock Persistent Storage on the Tails USB.
- If a hash or signature fails, stop. Do not improvise.
- Do not write words, xpubs, or txids on the print packet.
- Hardware later is optional. If used, different vendors.
The custody stack
A key generated with sufficient entropy on Tails OS — the airgap — is the foundation. After that key exists, you may export it onto a trusted hardware wallet for signing.
Bench sheets
The presentation teaches the why. These sheets are what you take to a closed-door table.
03
Home setup checklist
What to buy and prepare. Session flow from first dice roll through geographic split.
04
Tails airgap sheet
Two-machine rule. Tails with networking off. Optional: radio-less laptop.
05
Multi-tool verification
Official downloads. Hash + signature. Sparrow vs Electrum vs Ian Coleman.
06
Dice entropy + recording grid
Unbiased 1–4 mapping. Convert and cross-check 24 words. Printable shake sheet.
07
Sparrow on Tails
Launch verified Sparrow from Tails. Four commands, typed exactly.
08
2-of-3 spend path
Online unsigned PSBT → Tails Seed 1 → shutdown → Tails Seed 2 → broadcast.
09
Metal backup and split
Why titanium. How to stamp and read back. Plate A / B / C and yearly dust drill.
How to use the kit
- 01
Read this overview, then watch the 25-slide Plebum Dominium presentation.
- 02
Print the packet (or the individual sheets) for the closed-door table.
- 03
On a trusted online computer, download official Tails OS, Sparrow, Electrum, and Ian Coleman BIP39. Verify hashes and signatures. Copy only verified files to a clean data USB.
- 04
Verify bip39_dice_converter.py against VERIFY.md before you run it. If the hash differs, stop.
- 05
Work the checklist in order, with Tails OS networking off whenever a seed is in memory.
- 06
Test with dust in and dust out. Move savings only after both rehearsals succeed.
- 07
Stamp plates, restore at least one seed from metal, then split locations. Log places — never the words.
Download originals
- 00_Project_Overview.pdfTeam sheet. Scan the QR for the live site.
- 01_Slides.pptxThe original Plebum Dominium presentation.
- 02_Print_Packet.pdfTitle, contents, and all handouts. One staple.
- Handouts_No_Cover.pdfBench sheets without the cover.
- 03_Checklist.pdfBuy, prepare, and work in order.
- 04_Airgap.pdfTwo-machine rule. Networking off.
- 05_Verify.pdfHashes, signatures, rule of two.
- 06_Dice.pdfUnbiased 1–4 mapping. Print extras.
- 07_Sparrow.pdfLaunch offline. Sign one PSBT.
- 08_Signing.pdfWatch-only → two Tails sessions → broadcast.
- 09_Titanium.pdfStamp, read back, three locations.
- 10_Recovery.xlsxPlaces and rehearsal dates. Never seed words.
- bip39_dice_converter.pyOffline only. Hash against VERIFY.md first.
- VERIFY.mdPublished SHA-256 and dummy-bits test.
- README.mdProject map and house rules.
Support
Donate with Lightning
Scan the code or open it in a wallet. Any amount. This address stays up, so there is no invoice to refresh.
musthavemoresats@speed.app