>At one spin per millisecond (faster than this app runs), you'd expect a hit roughly once per 1.7 × 10⁶² years — about 10⁵² times the current age of the universe. The heat death of the universe occurs first
Alright! Now there’s only the heat death of the universe standing between me and massive wealth? I like these odds.
I'm not opposed to LLM-generated code at all, but the such obviously LLM-written README is annoying. The style is so easy to spot. At least try to figure out how to prompt it to not write so obviously like an LLM. (And no, I'm not even referring to the em dashes.)
I made a similar concept, but it wasn't self hosted. I never made the front page though! Congrats. Could you add a video of the experience to GitHub. Without that I wasn't willing to download and give it a go
No reason to--no one will hit.
You have much much much chance at guessing a random number that solves the next bitcoin block and mining the old fashioned way.
I got a couple of hits by pressing command-R _really_, _really_ fast. But transferring from Nakamoto's wallet feels a bit like fucking with the first bootprints in the lunar regolith.
Once these coins as much as budge, price will crater before the transaction has enough confirmations to settle the deposit on any exchange with enough liquidity. Any second on exchange and the hacker is exposed to having his account frozen.
Nobody would buy OTC as they're tainted and it would be basically throwing away their money for something that is traceable and everyone is watching and reacting to further moves
Then the blockchain could be effectively forked to before the attack, invalidating the heist
51% attack on bitcoin doesn't let you remove coins from someones wallet it allows you to change which transaction history is considered the real one. So you could send someone bitcoin then do a 51% attack to make the chain without that transaction longest so you get to keep your bitcoin but you can't use it to just take money out of someone elses wallet.
51% attack allows you to undo a recent transaction (as if it never happened). It does not allow you to change the destination of a transaction or arbitrarily move bitcoins around.
If you actually won this amount of money it would effectively ruin your life. You and your family would never be safe from a wrench attack - from criminals or a nation-state.
Let's see...2^241 or so possible 256 bit numbers, so that's 256 * 2^241, so that's....10^50 yottabytes. Obviously we're gonna need cloud storage for all this, so let's say that's about 2 cents per gigabyte/month, so that's...2.2614 × 10^63 dollars per month?
Actually, why does the site list the odds as ~1 in 5.27 × 10⁷²? That's 2^241, but it's picking random 256 bit numbers. Is it because there are so many valid hits?
Why wouldn't the host just send themselves the key first and then have everyone pull slot machine for them. If you do win it, you are not seeing a penny if you roll from that site.
Generally agree that most services like this would at a minimum log a matching key w/ alert. I'm not going to audit the code but maybe OP has good intentions.
Alright! Now there’s only the heat death of the universe standing between me and massive wealth? I like these odds.
Email it to me and I'll safely dispose of it for you at a responsible E-waste site.
So if I win, I won't be able to actually claim the Mooney's?
I don't think it'll ever show for reals
Estimated cost of a 51% attack on Bitcoin, if no one is cooperating, is $6 billion to $10 billion.
Surely the cost goes down if they get some big players to cooperate.
And the reward is... $83 billion. Basically 10x your money.
I mean, this is the kind of thing that we could sell bonds for, to raise the $6 to $10 billion needed.
Other than the fact that you'd be de-legitimizing BTC, the very thing you're trying to steal. Or morals - them, too. Other than that?
Nobody would buy OTC as they're tainted and it would be basically throwing away their money for something that is traceable and everyone is watching and reacting to further moves
Then the blockchain could be effectively forked to before the attack, invalidating the heist
Actually, why does the site list the odds as ~1 in 5.27 × 10⁷²? That's 2^241, but it's picking random 256 bit numbers. Is it because there are so many valid hits?
This kind of fun thing's exactly why I'm on the internet. Thanks for sharing! :D