#83

Unsolved8.3 BTC

Still unsolved, and the public key is not known either — so the only approach is generating keys through the interval one at a time and comparing addresses. There are 2⁸² keys in the interval, so sweeping all of it costs that many attempts (on average, half).

Address

14MdEb4eFcT3MVG5sPFG4jGLuHJSnt1Dk2

mempool.space

Key range (hex)

0x400000000000000000000 ~ 0x7ffffffffffffffffffff

Interval size

2^82 = 4.8×10^24

Balance

8.30002046 BTC · 5 tx

snapshot from 2026-08-23

Method of attack

Address brute force

work ≈ 4.8×10^24 (2^82)

Browser (JS, 1 thread)the search tool on this site8.5×10^12 years — 617× the age of the universe

CPU · keyhunt, 8 threads1.9×10^10 years — 1.4× the age of the universe

CPU · keyhunt, 16 threads9.6×10^9 years

GTX 10607.7×10^8 years

RTX 30701.9×10^8 years

RTX 30901.0×10^8 years

RTX 409061,293,676 years

RTX 509038,308,548 years

RTX 4090 × 106,129,368 years

RTX 4090 × 100612,937 years

RTX 4090 × 1,000the scale of a large pool61,294 years

All approximate. Implementation, clocks and target count move these by multiples, so read the order of magnitude and nothing finer. The calculator lets you put your own rate in.

Finding it is not the same as keeping it

A transaction moving puzzle funds carries the public key and the signature. The moment it reaches the mempool, bots take the same coins with a higher fee. That is exactly how #66 and #69 were lost. How to prevent it

Doing it

How to actually run this puzzle

Recommended: BitCrack (GPU)

With no public key there is nothing to do but generate addresses one at a time and compare. BitCrack does that on the GPU. On NVIDIA that means the CUDA build, cuBitCrack.

0. Build (Linux · CUDA)

git clone https://github.com/brichard19/BitCrack
cd BitCrack
make BUILD_CUDA=1
# On Windows, open BitCrack.sln in Visual Studio and build the cuKeyFinder project
# to get cuBitCrack.exe. macOS is not supported.

Run

./cuBitCrack -d 0 -b 288 -t 256 -p 1024 -c --keyspace 400000000000000000000:7ffffffffffffffffffff --continue progress-83.txt -o found-83.txt 14MdEb4eFcT3MVG5sPFG4jGLuHJSnt1Dk2

Watch out for

The best values for -b/-t/-p differ per GPU. Run it once at the defaults, look at the rate, then adjust.
Always include --continue. It keeps your position across restarts.
To split across machines, turn on “split the work” above. --share divides the range without overlap.
This shard covers 400000000000000000000 ~ 7ffffffffffffffffffff.

Other options

keyhuntCPU

CPU only. Handles both addresses and public keys, and is the easiest to install — good for learning and for checking your setup.

Kangaroonot usable

This puzzle's public key is not exposed. There is no discrete logarithm to solve.

A reality check

On a single RTX 4090 this takes 61,293,676 years. That is not “eventually”; in most cases it means “no”. Doing it anyway means accumulating GPUs or joining a pool.

Build it with your own options Start from installation

#82

unsolved · 8.2 BTC · half the difficulty

#84

unsolved · 8.4 BTC · twice the difficulty