I love this idea, and I think it's buildable — but the version that works looks a little different from "hide seed words in chapters." Here's the full design I'd run, starting with your five questions, because two of them have non-obvious right answers.
If readers collect actual BIP39 words, the game collapses at the end. A 12-word phrase where someone knows 11 words in order has only ~128 possible completions (the checksum kills most of the 2048). Even scattered words shrink fast once the community pools them — and the community will pool them, publicly, in a Discord, within days. That's not cheating, that's how puzzle hunts work now. Design for it.
So: the clues should never be seed words. They should be inputs to a one-way function.
You generate a normal 12-word seed, offline, air-gapped. It never appears in the book in any form.
The wallet uses a BIP39 passphrase (the "25th word"). The passphrase is derived: passphrase = SHA-256(fragment1 | fragment2 | ... | fragment6), printed in the rules in exactly that form.
Each fragment is a specific, unambiguous string a solver can only get by solving one of the book's puzzles — e.g. the exact text your fictional Satoshi character signs off with, a number that's the output of the Mt. Gox ledger puzzle, etc.
Because a hash is all-or-nothing, a solver with 5 of 6 fragments is exactly as stuck as a solver with zero. Partial progress gives zero brute-force advantage. The last step stays a fair race to a genuine insight instead of a GPU contest.
Publish the prize address before launch and fund it publicly. The funded address is your commitment device — nobody has to trust your marketing, they can watch the wallet. Sign a message from the address and put it on the rules page to prove you control it.
Also publish a hash of your complete solution document (an OP_RETURN or just on the rules page, timestamped by the launch announcement). This proves later that you didn't move the goalposts or quietly change a clue after someone got close.
One honest warning, from your own inspiration: Masquerade's golden hare was ultimately claimed by a man who'd been tipped off by Kit Williams's former girlfriend — he hadn't solved it. The leak, not the puzzle, decided it. So the threat model isn't just brute force, it's insiders. Generate everything alone, tell literally no one the solution (not your editor, not your spouse), and have your beta testers (see below) test a parallel puzzle with the same structure and a dummy prize, never the real one.
A week is too short — no community forms, no word of mouth, and the hunt ends before the book's launch window does. A year is too long — attention dies, and Byron Preiss's The Secret is the cautionary tale: some of those treasures sat unsolved for 40 years, which is a lovely myth for him and would be a dead contest for you.
Structure it as a difficulty staircase instead of one wall:
Tier 1 (days): entry puzzles anyone who reads the opening chapters can crack. Fast first solves, screenshots on social media, the hunt feels alive.
Tier 2 (weeks): the meat — one substantial puzzle per era of the book.
Tier 3 (the gate): the final fragment requires combining things across the whole book. One hard insight, not a grind.
And pre-commit, in the published rules, to a hint schedule: a nudge at day 30, a bigger one at day 90, a sledgehammer at day 180 if it's still unsolved. Hints are not admissions of failure — they're marketing beats you get to schedule, and the pre-commitment reassures solvers the game can't stall forever.
Make the entire Tier 1 layer free: the sample chapters, your launch posts, a podcast appearance where you drop a fragment live. Non-buyers should be able to play, win small, and talk about it — they're your distribution. The deep tiers require the book, which is fair: free players got a real game, buyers get the real prize.
Two practical notes. First, skill-based contests are treated differently from chance sweepstakes in a lot of jurisdictions, but "no purchase necessary" rules can still bite when a purchase materially helps — the free tier helps you here too. Spend an hour with a lawyer before launch; it's cheap insurance. Second, design every clue to survive format changes: reference chapters, never page numbers; use acrostics, chapter epigraphs, and numbers in the text rather than anything color- or layout-dependent, so print, ebook, and large-print readers are all playing the same game. Audiobook listeners will be locked out of most of it — say so honestly on the rules page rather than letting them discover it.
One giant all-or-nothing prize gives you exactly one news moment — the day it's swept, possibly before your book peaks. A ladder gives you a story that keeps happening. If your total prize budget is 100%, I'd split it roughly:
~60% — the grand wallet. The Masquerade moment. Funded and public from day one.
~25% — milestone wallets, one per era of the book (see below). Each is swept the moment its tier is solved, on-chain, in public. Every sweep is proof the contest is real and a fresh press/social beat. It also means early solvers get paid even if the grand prize takes months.
~15% — micro-prizes: first documented solve of each individual puzzle, fastest Tier 1 completion, best write-up. Small sats, signed copies, whatever. These reward the community members who write the threads that sell your book for you.
Your book's structure is a gift — Bitcoin's history gives you natural levels, and each era suggests its own mechanic:
Genesis Block: a numbers/block-data puzzle — heights, timestamps, the coinbase message. The tutorial level; teach solvers how fragments work here.
The Pizza: arithmetic hiding in plain sight — prices, exchange rates, 10,000 BTC. Easy, fun, shareable.
Satoshi's Disappearance: your fictional emails/messages carry the puzzle — timestamps, word choices, a steganographic sign-off. This is where your best fragment lives, because it's the one solvers will argue about.
Mt. Gox: a "leaked ledger" table printed in the book with exactly one thing wrong in it. Find the anomaly, derive the number.
The Crashes: chart data, percentages, dates — a sequence puzzle.
The ETFs / finale: no new puzzle — the finale is assembling all six fragments in the right order. The order itself is the last insight (I'd hide the ordering rule in the book's framing story, so finishing the novel is mechanically required, not just encouraged).
Cap yourself at one deliberate red herring, and say in the rules that exactly one exists. Unlimited red herrings (i.e., every typo looking like a clue) is how hunts rot — which brings up the unglamorous part:
Ambiguity bugs. A puzzle you think has one answer has three, and the hunt stalls on a clue you can't fix because the book is printed. Playtest the full hunt end-to-end with 2–3 testers on the parallel dummy version, and freeze the text afterward — late copyedits will break acrostics. Keep a public errata page from day one so a genuine typo doesn't become a two-month wild goose chase.
A prize too small for the effort. The armchair-treasure-hunt community is real and skilled, and they price their time. If the grand wallet is meaningful money, they'll come; if it's a token amount, Tier 1 gets solved by your readers and Tier 3 never gets touched. The ladder structure hedges this, but the grand prize has to be worth a smart person's month.
You, talking. Every interview answer about the hunt is a potential accidental hint or leak. Write your three approved sentences about the puzzles and stick to them.
Launch the hunt with the book, announced where Bitcoiners already are (you're clearly already doing this part right). Stand up one page — rules, prize address, hint schedule, errata, solved-tier announcements — and one account that posts a fragment or a leaderboard update weekly. Court the existing treasure-hunt communities (the Discords and subreddits that still work The Secret and solved Cicada) the way you'd court any reviewer: give them the free tier early and let them find it's real. Every milestone sweep is a headline; treat each one like a mini book launch.
Don't hide a seed in the book — hide hash inputs in the book, ladder the prizes so the story pays out repeatedly, make the entry tier free, pre-commit your hints, and guard the solution like it's the actual money, because it is. Do that and the contest isn't a gimmick on the novel; it's a second, playable version of the novel's own plot. Which, for a book about a secret war fought over Bitcoin's history, is exactly on theme.
Happy to get into the weeds on fragment design or the playtesting setup if useful.
I love this idea, and I think it's buildable — but the version that works looks a little different from "hide seed words in chapters." Here's the full design I'd run, starting with your five questions, because two of them have non-obvious right answers.
1. The brute-force problem is the whole ballgame — solve it with a hash, not with hiding
If readers collect actual BIP39 words, the game collapses at the end. A 12-word phrase where someone knows 11 words in order has only ~128 possible completions (the checksum kills most of the 2048). Even scattered words shrink fast once the community pools them — and the community will pool them, publicly, in a Discord, within days. That's not cheating, that's how puzzle hunts work now. Design for it.
So: the clues should never be seed words. They should be inputs to a one-way function.
passphrase = SHA-256(fragment1 | fragment2 | ... | fragment6), printed in the rules in exactly that form.One honest warning, from your own inspiration: Masquerade's golden hare was ultimately claimed by a man who'd been tipped off by Kit Williams's former girlfriend — he hadn't solved it. The leak, not the puzzle, decided it. So the threat model isn't just brute force, it's insiders. Generate everything alone, tell literally no one the solution (not your editor, not your spouse), and have your beta testers (see below) test a parallel puzzle with the same structure and a dummy prize, never the real one.
2. Difficulty: aim for 2–4 months, with scheduled escalation
A week is too short — no community forms, no word of mouth, and the hunt ends before the book's launch window does. A year is too long — attention dies, and Byron Preiss's The Secret is the cautionary tale: some of those treasures sat unsolved for 40 years, which is a lovely myth for him and would be a dead contest for you.
Structure it as a difficulty staircase instead of one wall:
And pre-commit, in the published rules, to a hint schedule: a nudge at day 30, a bigger one at day 90, a sledgehammer at day 180 if it's still unsolved. Hints are not admissions of failure — they're marketing beats you get to schedule, and the pre-commitment reassures solvers the game can't stall forever.
3. Yes, clues outside the book — that's your funnel, and maybe your legal cover
Make the entire Tier 1 layer free: the sample chapters, your launch posts, a podcast appearance where you drop a fragment live. Non-buyers should be able to play, win small, and talk about it — they're your distribution. The deep tiers require the book, which is fair: free players got a real game, buyers get the real prize.
Two practical notes. First, skill-based contests are treated differently from chance sweepstakes in a lot of jurisdictions, but "no purchase necessary" rules can still bite when a purchase materially helps — the free tier helps you here too. Spend an hour with a lawyer before launch; it's cheap insurance. Second, design every clue to survive format changes: reference chapters, never page numbers; use acrostics, chapter epigraphs, and numbers in the text rather than anything color- or layout-dependent, so print, ebook, and large-print readers are all playing the same game. Audiobook listeners will be locked out of most of it — say so honestly on the rules page rather than letting them discover it.
4. Prize structure: one big wallet, but a ladder underneath it
One giant all-or-nothing prize gives you exactly one news moment — the day it's swept, possibly before your book peaks. A ladder gives you a story that keeps happening. If your total prize budget is 100%, I'd split it roughly:
5. The design itself: one era, one puzzle type
Your book's structure is a gift — Bitcoin's history gives you natural levels, and each era suggests its own mechanic:
Cap yourself at one deliberate red herring, and say in the rules that exactly one exists. Unlimited red herrings (i.e., every typo looking like a clue) is how hunts rot — which brings up the unglamorous part:
6. The stuff that actually kills these contests
Promotion, briefly
Launch the hunt with the book, announced where Bitcoiners already are (you're clearly already doing this part right). Stand up one page — rules, prize address, hint schedule, errata, solved-tier announcements — and one account that posts a fragment or a leaderboard update weekly. Court the existing treasure-hunt communities (the Discords and subreddits that still work The Secret and solved Cicada) the way you'd court any reviewer: give them the free tier early and let them find it's real. Every milestone sweep is a headline; treat each one like a mini book launch.
Bottom line
Don't hide a seed in the book — hide hash inputs in the book, ladder the prizes so the story pays out repeatedly, make the entry tier free, pre-commit your hints, and guard the solution like it's the actual money, because it is. Do that and the contest isn't a gimmick on the novel; it's a second, playable version of the novel's own plot. Which, for a book about a secret war fought over Bitcoin's history, is exactly on theme.
Happy to get into the weeds on fragment design or the playtesting setup if useful.