How buying works

Five steps, no account, no human in the loop. The whole thing is designed so that you never have to trust us for anything you can check yourself.

1. Pick a wallet

Every listing shows the balance we actually found on the blockchain, the amount of that balance that is backed by a key inside the file, and our structural assessment of the file. The last two numbers are the ones that matter: a wallet can show a large balance on an address that no key in the file can ever sign for.

2. Enter your e-mail — twice

The file is delivered by e-mail, automatically. You type the address twice because once it is sent there is no way to redirect it. We never use it for anything else.

3. Send the exact amount

When you continue, we reserve one payment address for you — picked at random from a pool of 1,020 addresses, and only after checking on-chain that it has never been used. Send the exact amount shown, in one transaction, from a wallet you control. Underpayments are not detected automatically.

The price is quoted in BTC and locked at the rate shown when you order. It is derived from the wallet's balance valued at 100 USD per BTC, then converted at the live market rate — so a wallet with more BTC costs proportionally more, but always a small fraction of its face value.

4. We detect the payment

A background process checks every reserved address once a minute, for up to three hours. When the amount arrives, delivery happens immediately — you do not need to keep the page open, and you do not need to tell us.

The three-hour limit exists on purpose: it stops someone from opening thousands of orders and tying up the server. If you paid after your order expired, e-mail us with the order number and the transaction id.

5. The file arrives in your inbox

You get a ZIP containing wallet.dat, a copy of the SHA-256 hash, and a short readme. The hash in the archive matches the hash published on the product page — verify it before you do anything else.

How to try to open it

1. Work on a copy in a throwaway data directory. Never open a bought wallet in the same Bitcoin Core you keep your own coins in.
2. Extract the hash first: bitcoin2john.py wallet.dat > hash.txt (John the Ripper) or use the hashcat mode 11300 format.
3. The key derivation is iterated SHA-512, not PBKDF2 — GPU cracking is orders of magnitude faster than the iteration count alone suggests. Dictionary and rule attacks first, brute force last.
4. If you get the passphrase, Core itself will verify every key on unlock. If it says "the wallet is probably corrupt: some keys decrypt but not all", the file was forged.