#53
SolvedKey exposedThe private key to this puzzle is public and the balance has been swept. Everything below was re-derived with secp256k1 and confirmed to match the address — never take a copied value on trust.
0x10000000000000 ~ 0x1fffffffffffff
2^52 = 4.5×10^15
0.00000000 BTC · 3 tx
snapshot from 2026-08-23
020faaf5f3afe58300a335874c80681cf66933e2a7aeb28387c0d28bb048bc6349
Exposed on 31 May 2019, when the creator withdrew 1,000 satoshis from this address. This is the value BSGS and Kangaroo take as input.
00000000000000000000000000000000000000000000000000180788e47e326c
The balance is zero. This value is useful for verification and learning only — import it into a wallet and you will find nothing there.
How to actually run this puzzle
The public key is known, so the discrete logarithm is solved directly. The work drops from 2^52 to around 2^26.
git clone https://github.com/JeanLucPons/Kangaroo cd Kangaroo make gpu=1 ccap=86 # ccap is your GPU's compute capability (4090=89, 3090=86, 1060=61) # On Windows open VC_CUDA102/Kangaroo.sln in Visual Studio. macOS and AMD are not supported.
cat > in53.txt <<'EOF' 10000000000000 1FFFFFFFFFFFFF 020FAAF5F3AFE58300A335874C80681CF66933E2A7AEB28387C0D28BB048BC6349 EOF
./kangaroo -t 8 -gpu -gpuId 0 -w save53.work -wi 300 -o found-53.txt in53.txt
- Order matters in the input file — range start, range end, public key. Get it wrong and it finds nothing.
- -d is the distinguished-point bit count. Leave it out and it picks one; only touch it when distributing.
- -w and -wi save progress every five minutes. On a job that runs for days this is not optional.
- To combine machines use -s (server) / -c (client) mode. It is more efficient than splitting the range.
CPU only. Handles both addresses and public keys, and is the easiest to install — good for learning and for checking your setup.
Address brute force. The de facto standard for puzzles with no public key, and the only one that runs on AMD.
The public key is known, so brute-forcing addresses is a waste. Kangaroo needs 2^26 operations where BitCrack runs 2^52.
This one is already solved. The commands above are for learning — knowing the answer makes it a good way to confirm your tool actually works.