Collections

Collections

Ten collections on five chains. Each page says what the puzzle was and what the records carry. The facts strip is read off the library when the page builds.

Every collection answers the same calls: get, require, all, solved, unsolved, withPubkey, count, verify, balance. What changes is the puzzle itself. A search over a key range. A brainwallet passphrase. An image with a seed hashed into it. A script that pays for a hash collision. A thread explains those once and a dataset forgets them. So each page here writes them down next to the numbers.

CollectionKeyChainsPuzzlesWhat it is
Bitcoin puzzle transactionb1000bitcoin256Keys of 1 to 256 bits, one address each, since 2015
RushWallet contestrushwalletbitcoin30Brainwallets from a 2014 contest
Zden's puzzleszdenbitcoin, ethereum, litecoin, decred15Visual puzzles, 2016 to 2024
Arweave bountiesarweavearweave, ethereum12Tiamat's weave puzzles
WarpWallet challengeswarpbitcoin6Keybase's scrypt brainwallet, 2013 to 2016
Hash collision bountieshash_collisionbitcoin6Peter Todd's P2SH scripts
Ballet walletsballetbitcoin3BIP38 keys on physical wallets
Bitimagebitimagebitcoin2Seeds hashed from photographs
Bitaps mnemonic challengebitapsbitcoin1A 3 of 5 secret sharing scheme
GSMG.io puzzlegsmgbitcoin1A multi phase image puzzle

What every page says

  • The facts strip at the top is read off the collection in the build. The counts and prize sums can't drift from the records.
  • The prose says what the puzzle asks, what's known about its keys, and how the records are written. One record is quoted the way it sits on disk.
  • Quirks get named. A status that needs explaining, a prize that shrank, a passphrase nobody has. The page says so instead of leaving it to the thread.

@agntn/puzzles·MIT license· Public data about public puzzles. Balances come from the chains' explorers through the worker, cached for five minutes. Every key here was public before it landed in a record.