Amount: <0.3 tBTC>
Address: <tb1qnn6mhy7cx8f2q5cud8hkmzpq77v4nrenwk69fr>
Project: <a BRC20 and ERC20 bridge>

Thanks a lot man!

I put up a website listing all the bitcoin addresses with balances, sorted from the most to the least,

https://bitkeys.work

You can see, the top address has 122K BTC in it. You can try to vanitygen your addresses by targeting those address, and good luck in some years.

I know it's an old post, but in case someone is still looking for all bitcoin address with balance, I made a website to list all of them.

https://bitkeys.work

Last update: May 15, totally 24,373,540 addresses with balance.

The private key is randomly generated, in a slim hope that you can find a collision - a private key what has Bitcoin balance in its corresponding public key (address). Each time the page is loaded, the private keys are randomly generated.

Hopefully someone will find it useful.

Database updated May 7, 2019

Address in total: 24,065,464 addresses that have Bitcoin balance.

You don't need to go through the same steps of generating an address, since you know the public key space is 160 bit long, you just need to search 160 bit long private key space, in a hope to find a collision.

Example: If I know you are mapping a value in the space of one trillion, 2^40, to a space of 2^4 (0-F in hexdecimal), I just need to try all 2^4 numbers to see which one collides, I don't need to know or compute the original number in the range of 2^4.

Bitcoin is mapping 256 bit key space to 160 bit space, actually the public key space is 2^96 times smaller than its private key space, - much more shrinking of co-domain than the above example 2^40 to 2^4 (only 2^36 times smaller) 

I agree 2^80 is a huge number, actually the world's fastest computer can do 200K trillion flops, that's close to 2^58, to generate 2^80 keys, that machine will need 2^22 seconds, which is 46 days. Then you will have about 50% that there exist collided keys inside this huge list of 2^80 keys. I see 2^80 is the magic number that will put Bitcoin on the brink of collapsing, sure we are not quite there yet, but are we too far from it? Considering the rate the computers/GPU's/ASIC's are produced, I don't think the scenario is too remote. 

For those who want to crack the most valuable BTC addresses, I've put up a sorted list on this website:

https://bitkeys.work

The top 50 addresses are on the 1st page, next top 50 addresses on the 2nd page, and so on...

You can see the #1 address has 125,804 BTC in it.

Good luck cracking. 

If you are interested in any address, you can click it to blockchain.com page, there you can have a better view of the transaction details of any address, if transactions happened before.

I can build a relational DB and provide the same view as blockchain.com, but I just feel they already did a good job and there is no point of repeating it.

My primary goal is to provide the whole list of BTC address with balance, which I can't find elsewhere.

For the record, no. I don't check it sneakily. In fact, each address generated is automatically linked to blockchain.com, it's a bit cumbersome but you do have the means to verify the balance on a 3rd party website.

I parsed the blockchain, extracted all ~24 million addresses with unspent transaction output (UTXO), and dump them into DB table, you divide 24 million by 50 (per page), you get this gigantic pagination. But they are actually all in a local DB server, not generated on the fly.

The random private keys and their compressed and uncompressed addresses, are generated on the fly, on each page load.

Of course you don't search private keys by flipping web pages, it'd be too slow, so this project is just for fun. For professional searchers/hackers, you run parallel programs that use all your CPU cores and GPU ALU's, better written in Pony language, or C/C++/Cuda, for a slim hope to find a collision. And yes I agree, 2^80 is a huge number. And even when you produce 2^80 private keys, the probability that there exist collision among the 2^80 keys, is 50%. But when you possess this monster computational power, 2^80, I see Bitcoin is on the brink of collapsing.

This is an explanation of Bitcoin's compressed and uncompressed versions of address.

https://github.com/OmniLayer/omniwallet/wiki/Converting-between-Compressed-and-Uncompressed-Addresses-and-Private-Keys

The takeaway is: each private key can generate 2 versions of Bitcoin address, compressed and uncompressed. When you stare at a Bitcoin address, you CAN'T tell whether it is compressed or not, so you have to check the balance of both versions for a single private key.

OK, I will tweak the UI, font size, search box etc.

Thanks for the feedback so far...

I couldn't find a complete list of all bitcoin address with balance on the web, so I decide to put up one myself, and I plan to update the list weekly.

https://bitkeys.work

I hope it's useful for someone who do casual research on Bitcoin address, to add a "fun" flavor, random private keys are generated to the right, with the slim hope that someone is lucky enough to find a collision.

As of May 7 2019, there are 24,065,464 Bitcoin addresses with balance, the top address has 124K bitcoins in it.

The serious part is: I have a little doubt on the viability of RIPEMD160, by the curse of "birthday paradox", approaching 2^80 computation doesn't seem to be too remote. It's just not economical (profitable). At present, the whole network can do 2^66 hashes per second, it takes 2^14 seconds - less than 1/4 day, to reach 2^80 computation. And remember, that is 2 times SHA256 on a block. ASIC's that are computing one-time random SHA256 should cost less and do more.

Looking ahead the expected long life span of Bitcoin, the exponential increase of mining difficulty, the flat/constant difficulty of generating SHA256 private keys, we may see the equation changed to favor private key searching than mining.

I welcome anyone to correct my math, better not to look like an idiot.  

One more thing, to help those who do intensive private key searching, I can send you the whole list as long as I can, so PM me. My last parsing on April 30 2019 returned 23+ million addresses, as you can see from the website, the top address has 125,805 BTC, all the way down to many addresses with only 1 satoshi in them...

Right now the file is in CSV, format is:

base58-address, balance-in-satoshi

Thanks again, I look forward to your comments, and corrections.

It's now May 1 2019, anybody still hunting BTC private keys?