Live data from Hacker News

All Bitcoin private keys are on this website

playxo.com

51–60 of 398 posts

Re: All Bitcoin private keys are on this website

#51
Reminds me pretty popular torrent from old times named something similar to "List of all IPv4 addresses - every hacker must have". Sadly I am not able to remember exact name and find it anymore.

Backstory is that ~15 years ago when upload ratio was important some person decided to generate a list and upload a torrent with such click bait name just to increase his/her ratio. It worked well.

Re: All Bitcoin private keys are on this website

#52
post #13

Earlier quoted context omitted.

its like asking if you had a rocketship that traveled at the speed of light, how long until you find earth given you're on some random galaxy

Not really because if you are travelling at the speed of light time isn't passing...

does that technical mistake hinder the point of my comment?

Re: All Bitcoin private keys are on this website

#53
post #26

It's like passively playing the world's worst lottery in terms of odds, but hundreds of thousands of times every second. It's fun but the odds are astronomically low. I have a script[1] that generates a pub+private key and checks against a massive file of addresses with BTC[2]. The list of addresses is loaded in memory as a python `set` so checking is O(1), but I feel like optimisations at increasing the rate are fut…

That's what mining is too, basically. It's just that a mining rig can "buy a lot more tickets".

Re: All Bitcoin private keys are on this website

#56

Earlier quoted context omitted.

With every supercomputer working for 100 years, you can have 0.01% of all accounts, maybe.

... not even close. 2^256 is a very large number. If you could build a computer that required a single atom, and could test the balance of a single account in a single nanosecond, and then converted the entirety of the earth into such computers, it would take ~2.8 million years for you to check 0.01% of all accounts. Brute-forcing modern cryptography isn't something that can happen. The magnitude of 2^256 is close to…

This reminds me of a discussion a few years ago where someone was extremely adamant that you'd have to handle the chance of a key collision in a random 256-bit key for the system to be secure :)

Re: All Bitcoin private keys are on this website

#57
post #26

It's like passively playing the world's worst lottery in terms of odds, but hundreds of thousands of times every second. It's fun but the odds are astronomically low. I have a script[1] that generates a pub+private key and checks against a massive file of addresses with BTC[2]. The list of addresses is loaded in memory as a python `set` so checking is O(1), but I feel like optimisations at increasing the rate are fut…

That's what mining is too, basically. It's just that a mining rig can "buy a lot more tickets".

Solo mining yeah definitely, but with pool mining one can at least generate some fraction of a BTC.

Re: All Bitcoin private keys are on this website

#58
post #26

It's like passively playing the world's worst lottery in terms of odds, but hundreds of thousands of times every second. It's fun but the odds are astronomically low. I have a script[1] that generates a pub+private key and checks against a massive file of addresses with BTC[2]. The list of addresses is loaded in memory as a python `set` so checking is O(1), but I feel like optimisations at increasing the rate are fut…

Luabase has SQL access to this type of data. It’s in beta but email mike@luabase.com if you’d like to check it out.

Re: All Bitcoin private keys are on this website

#59
post #13

Earlier quoted context omitted.

its like asking if you had a rocketship that traveled at the speed of light, how long until you find earth given you're on some random galaxy

Not really because if you are travelling at the speed of light time isn't passing...

Not a physicist, but I don’t imagine you can turn while going light speed

Re: All Bitcoin private keys are on this website

#60
post #34

Earlier quoted context omitted.

They're the trivial wallet addresses (close to the beginning and end of the search space). I would expect them to be used for debugging and testing in the early days.

What makes them trivial, how are they generated?

> A private key is basically just a number between 1 and 2^256

It's like saying "I'm gonna pick a random number between 1 and a trillion", and then picking 999,999,999,995. Probably not a smart idea given that you don't want anyone else to be able to guess your number.

Post reply on HN