Live data from Hacker News

All Bitcoin private keys are on this website

playxo.com

211–220 of 398 posts

Re: All Bitcoin private keys are on this website

#212
What if my utxo is a taproot output? The page only shows base52 addresses. What if they are additionally locked with hash like Lightning channels are?

The checker is bound to be unexhaustive because even with Bitcoins limited scripting, there are too many scripts to check. And with taproot it has gotten even cheaper to use complicated locking schemes.

Re: All Bitcoin private keys are on this website

#213

> Finding an active wallet is hard, but not impossible. Every time you open a random page, you have a chance of finding someone else's fortune. Good to know I have a 1/2^256 chance to find a bitcoin billionaire's wallet. This feels only slightly more ludicrous than the guy who lost his bitcoin in a hard drive and went looking for it in a dumpster.

I have had a crappy life, abused sexually and physically when a child, but trust me whenever I re-hear about that guy losing his hard drive with BTC in it, I am like, yikes.

Re: All Bitcoin private keys are on this website

#214
post #204

Earlier quoted context omitted.

And then, when you "hit the jackpot", will you become a thief? Or will you just feel like you picked a lock, smile and pull the door back shut.

Why a thief? Bitcoin is a silly idea based on scarcity that doesn't exist. If someone generated the right numbers by chance and had luck, I wouldn't say they'd be doing anything wrong getting whatever is there. It's not the same as stealing data, and is not the same as hacking into a banking system. It's decentralized, and there isn't the concept of real scarcity. It's not even hacking. https://henvic.dev/posts/bitco…

Because whether or not Bitcoin is silly, someone else paid their hard earned money for the coins, usually we say that makes someone the owner.

What do you usually call someone who takes a thing from its owner without permission?

Re: All Bitcoin private keys are on this website

#215

Earlier quoted context omitted.

I think you are missing how this would work. The scammer wouldn't scoop up the proceeds if it was a small account you were looking up, only if it was a whale. This is to prevent someone from figuring out it was a scam with a small account and only gain a few dollars from the scam.

I think you are missing something. If you have a wallet with very little or no money attached to it. And the you check for the correspoinding private key. If you find it - you "know" it works and then _might_ be inclined to try the key for a more serious wallet. But if not, then you know this site doesn't work and would have no inclination to try another key. If you enter important passwords or keys into random websi…

No, I am not. Follow along:

I check my $100 dollar wallet.

It's there, doesn't get emptied.

Cool, I think! Next day I check my $1000000 wallet.

It gets immediately emptied.

Alternatively:

I check my $100 dollar wallet. It gets emptied.

SCAMMER I scream on HN and Twitter.

Site gets shutdown. Silly person doesn't check their $1000000 wallet.

Re: All Bitcoin private keys are on this website

#216
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…

Ignoring the prospects, this is a neat case to explain sharing memory in multiprocessing. You're reading the file in every process, this needs mem x N for N processes. If you first read in the file, create the set, and then use multiprocessing, you will get forked processes sharing the parent's memory, i.e. only need 1 x N the memory.

I haven't grokked shared memory in python yet to implement it (https://docs.python.org/3/library/multiprocessing.shared_mem...). Apparently there is also a known bug? (https://stackoverflow.com/questions/14124588/shared-memory-i...), but an improvement I'd like to learn and implement. Though the file I have is just over 1GB, so it's not prohibitive yet.

Funny thing is even though it's throwaway code, ensuring everything worked as expected felt really high-stake since a bug would mean a found key would be lost!

Edit: Also not sure if shared memory would be slower in python3 (or if it was, whether it would matter in this use-case), but an interesting thing to profile.

Re: All Bitcoin private keys are on this website

#217

Soo what happens if you're incredibly lucky and stumble across the private key for an active wallet? If you transfer the funds out, isn't that just theft? Is "guessing" a private key any different from guessing someone's bank details?

The problem would be getting the money out without revealing your identity

If you end up stealing from the mob or well known exchanges it's a problem but for everyone else does it really make any difference?

How do they prove they were the previous owner and that it wasn't a legit transaction?

Re: All Bitcoin private keys are on this website

#219
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".

I would say "it can solve very big sudokus way too fast"

Re: All Bitcoin private keys are on this website

#220
post #204

Earlier quoted context omitted.

And then, when you "hit the jackpot", will you become a thief? Or will you just feel like you picked a lock, smile and pull the door back shut.

Why a thief? Bitcoin is a silly idea based on scarcity that doesn't exist. If someone generated the right numbers by chance and had luck, I wouldn't say they'd be doing anything wrong getting whatever is there. It's not the same as stealing data, and is not the same as hacking into a banking system. It's decentralized, and there isn't the concept of real scarcity. It's not even hacking. https://henvic.dev/posts/bitco…

Causing demonstrable harm or damage by taking something is sufficient to be considered a thief.
Post reply on HN