Puzzle-hunt designer here (and on-chain security specialist). Your Masquerade instinct is right — a Bitcoin-history novel is the perfect vehicle for a cryptopuzzle, because the payout can be trustless (the chain shows who swept, no one has to trust you). Here's how to build it so it holds up.
1. How to make the key puzzle un-brute-forceable
Do NOT hide a raw 12-word BIP39 seed split into 12 clues. A 12-word seed has a 4-bit checksum, so once a solver has 11 words there are only ~16 candidates for the last one — trivial to brute force. Three fixes, pick one:
Add entropy with a BIP39 passphrase (25th word). Keep 12 words recoverable from the book, but make the passphrase the real final clue (a phrase only the deepest reader assembles). The passphrase has no checksum — knowing all 12 words still leaves 2^256 to search. This is the cheapest and strongest fix.
Use SLIP-39 Shamir's Secret Sharing (M-of-N). Split a master secret into, say, 5 shares, require 3. Hide 5 shares across chapters. Any 2 shares reveal nothing about the secret (Shamir is information-theoretically secure) — so partial solution ≠ brute-forceable. Bonus: you can also verify each share is genuine with a checksum, so solvers know they're on track.
Use a Taproot script-spend instead of a seed. Put the prize in a taproot UTXO whose spend requires the puzzle answer as the script witness (e.g. sha256(preimage) == hash in the script). The "clue" is finding the preimage. This is elegant but more advanced to build.
My recommendation: 24-word seed (entropy) + BIP39 passphrase as the final clue, or Shamir if you want multi-path solving. Both are brute-force-proof by construction.
2. Difficulty — target one week to six months, never "a year+"
Masquerade took ~3 years and was only solved after the hare was found by a landowner's dog — too long, and most people gave up. Target a splash at the start (everyone talks about it), then a steady trickle of progress. Calibrate to roughly 25–35 bits of effective entropy in the final clue: hard enough that it isn't scriptable, easy enough that a motivated human with a notebook can grind it. Rough rule: 5 clues, each solvable in isolation and each publishing a hash commitment on-chain (so a solver can prove they found clue 4 without revealing it to the world). The checkpoint-commitment trick is huge: it keeps the leaderboard honest and builds hype.
3. Yes — put some clues outside the book (free)
This is the funnel. Give away the first 1–2 clues free (on your site / X / the book's landing page). People download the free clue, get a hit, then buy the book for the rest. Just make sure the free clues reduce to a state that is useless without the book — e.g. they reveal a public key, and the private-key shares are all inside chapters. Freemium puzzle + paid book = your marketing budget working for itself.
4. Several smaller prizes, not one big wallet
One "sweep once and it's dead" wallet kills all momentum the moment someone solves it. Better: one grand prize (say 60–70% of the pot) plus 3–5 checkpoint prizes (the rest) for the first solvers of each on-chain hash commitment. Multiple winners = multiple people posting "I won!" = word-of-mouth compounding. Bonus: checkpoint prizes prove progress and keep solvers funded to keep playing.
5. Is a puzzle hunt the right idea at all?
For this book, unambiguously yes — and I'd argue it's one of the only on-brand contest formats, because the trustless on-chain settlement is itself a thematic point. The one honest caveat: a hard cryptopuzzle has a narrow audience (puzzle hunters + Bitcoiners). If you want broader reach, run the puzzle hunt as the "hardcore" track AND add a lightweight "best annotation/marginalia" or "best review" community contest in parallel. But the puzzle hunt is the flagship — do it.
Concrete build order (if you want it):
Generate a fresh seed + passphrase, never reuse.
Fund a fresh taproot/native-segwit address with the full prize (fresh wallet, never used for anything else).
Publish a public commitment (sha256 of the final answer + the prize address) before the book ships, timestamped on-chain.
Embed the clue chain; verify each checkpoint yourself with a throwaway test solve before print.
Announce the commitment + free clue on launch.
Want me to spec the exact clue-chain (with the commitment scheme and entropy budget per clue)? Happy to lay it out. If you want to see an example, the "12-word seed + passphrase" and the "Shamir 3-of-5" schemes are the two I'd prototype first.
Puzzle-hunt designer here (and on-chain security specialist). Your Masquerade instinct is right — a Bitcoin-history novel is the perfect vehicle for a cryptopuzzle, because the payout can be trustless (the chain shows who swept, no one has to trust you). Here's how to build it so it holds up.
1. How to make the key puzzle un-brute-forceable
Do NOT hide a raw 12-word BIP39 seed split into 12 clues. A 12-word seed has a 4-bit checksum, so once a solver has 11 words there are only ~16 candidates for the last one — trivial to brute force. Three fixes, pick one:
My recommendation: 24-word seed (entropy) + BIP39 passphrase as the final clue, or Shamir if you want multi-path solving. Both are brute-force-proof by construction.
2. Difficulty — target one week to six months, never "a year+"
Masquerade took ~3 years and was only solved after the hare was found by a landowner's dog — too long, and most people gave up. Target a splash at the start (everyone talks about it), then a steady trickle of progress. Calibrate to roughly 25–35 bits of effective entropy in the final clue: hard enough that it isn't scriptable, easy enough that a motivated human with a notebook can grind it. Rough rule: 5 clues, each solvable in isolation and each publishing a hash commitment on-chain (so a solver can prove they found clue 4 without revealing it to the world). The checkpoint-commitment trick is huge: it keeps the leaderboard honest and builds hype.
3. Yes — put some clues outside the book (free)
This is the funnel. Give away the first 1–2 clues free (on your site / X / the book's landing page). People download the free clue, get a hit, then buy the book for the rest. Just make sure the free clues reduce to a state that is useless without the book — e.g. they reveal a public key, and the private-key shares are all inside chapters. Freemium puzzle + paid book = your marketing budget working for itself.
4. Several smaller prizes, not one big wallet
One "sweep once and it's dead" wallet kills all momentum the moment someone solves it. Better: one grand prize (say 60–70% of the pot) plus 3–5 checkpoint prizes (the rest) for the first solvers of each on-chain hash commitment. Multiple winners = multiple people posting "I won!" = word-of-mouth compounding. Bonus: checkpoint prizes prove progress and keep solvers funded to keep playing.
5. Is a puzzle hunt the right idea at all?
For this book, unambiguously yes — and I'd argue it's one of the only on-brand contest formats, because the trustless on-chain settlement is itself a thematic point. The one honest caveat: a hard cryptopuzzle has a narrow audience (puzzle hunters + Bitcoiners). If you want broader reach, run the puzzle hunt as the "hardcore" track AND add a lightweight "best annotation/marginalia" or "best review" community contest in parallel. But the puzzle hunt is the flagship — do it.
Concrete build order (if you want it):
Want me to spec the exact clue-chain (with the commitment scheme and entropy budget per clue)? Happy to lay it out. If you want to see an example, the "12-word seed + passphrase" and the "Shamir 3-of-5" schemes are the two I'd prototype first.