/biz/ - Business & Finance

>>11016832
how does "until the heat death of the universe" sound", buddy?

>>11016832
A few hundred years or so

You know of any libraries for json parsing in c? The OP of the last thread told that there are none.

>>11016846
This

>>11016832
what's your CPU? Also what does the script do? Is it in Python or Bash?

>>11016846
>>11016863
If hes lucky

>>11016862
https://zserge.com/jsmn.html

>>11016862
Why the fuck would you do anything beyond kernel programming in C?

>>11016873
The only thing I could think of is speed optimization.

I've been running scripts like those for much longer. The answer is "it takes less time to take whatever steps might be necessary to have the owner of whatever wallet you want (even the richest one) not only hand the private key to you but also let you fuck his wife and daughter.

No seriously. This is purely luck based. You could find something within 1 day. You could not find anything in the amount of time it will take for this planet to disappear

>>11016864
It's a python script some anon posted here
The code is small, any brainlet can audit it

https://github.com/Isaacdelly/Plutus

>>11016924
did you ever find anything?

>>11016931
This will never work.

OP if you're running this at the very least you should set the cores = to the number of cores on the system and run it on like an EC2 instance with 32 cores.

>>11016931
By the way, if anyone has any ideas on how to have this work faster, let us know. The odds are so low if it works 10k times faster for all of us it will still hardly harm anyone.

>>11016943
Nada and I couldn't expect to. I put this into perspective though...

You need to be lucky enough to win the lottery many, many times over. However lottery tickets cost money. Not saying the script doesn't (utilizes your CPU or GPU and your internet connection) but it's close to free in comparison with any lottery. And you put in there bajillions of entries, not just 1 or 10.

The concern is, lottery is still more legal. On the extremely rare chance that you find balance, what are you gonna do? Steal a bit? Steal a lot? Lose that one in 37 lifetimes chance? That's the thing. I don't want to risk prison or a Hitman. I just want a chance at cash.

>>11016978
The issue with that is that you get timed out rather quickly.

>>11017074
Are you getting time out from requests to bitcoinlegacy?

>>11017112
Yep, if using multicore with just 4 cores.

With blockchain.info I can use 6 without timeouts. I guess there would be a way to do it locally but unfortunately I don't own a spare 256gb SSD where I could put that gigantic database.

>>11017146
Where can I get the database? I have a 2 tb SSD so I can do it locally. In regards to the timing out, I'll mess around with this script and see if I can dynamically change the request source per request. That should solve that problem.

Business & Finance

You might as well just fucking mine Monero lads

>>11017168
Keep in mind I have no idea how to utilize this kind of script with it, but you can generate a database by downloading the entire blockchain with the Bitcoin wallet client, which can take a good amount of hours, and generate that database with some Python script called Abe.

There is also another bruteforce script available that is compatible with that local database, but it does dictionary attacks from provided .txt dictionaries, which for most passwords and common words is pointless because that has been tried years ago (still good to check that it does work, at least).

You just need to sync a BTC node, same as any other blockchain. If you only want to do it for this reason don't even bother though, you're better off using your CPU to mine BTC.

>>11017209
>>11017247
It's a different thing anyways. One is an approach that could probably give you money in a few hours if you happen to be the luckiest person alive. The other is an approach you would take if you can afford to wait but is a guaranteed 0% chance of quickly getting some dosh.

>>11017246
It would be a lot of work, but the best way to do it would be to build a "learning box" with like 32 cores, 1080TI SLI. Download blockchain into some SQLDB like Postgres (which is one that Abe is built off). Run the Postgres DB on a local server and just query it from there. Totally doable though.

>>11016846

It would take a computer the size of the moon billions of years.

https://www.eetimes.com/document.asp?doc_id=1279619

There are I believe ca. 3 million wallets with BTC balance, so that simply means the odds of getting a collision is 3 million times higher than to crack a single targeted wallet. That means it would take 50 billion years to crack an AES 128 bit key, using a supercomputer. The problem is that BTC is AES 256 bits, it would take a computer the size of the moon 1 trillion * trillion * trillion * trillion * trillion * trillion * trillion * trillion years.

And no I'm not exaggerating, there's a reason despite all the FUD and misinformation not one knowledgeable person has ever questioned the security of BTC wallets. As in even the people who hate BTC concede that it is impossible to steal someones BTC from collisions.

>inb4 that one faggot posts the LBC trophies page

I honestly am skeptical of the legitimacy of that page, I've looked into it and can't find any real source of it having actually found those BTC from collisions, since the numbers don't add up and numbers don't lie. Even then it was like 8 collisions in about 5 years.

>>11017554
Yeah but it's not cracking the wallet. It's spoofing a random private key for a given wallet and checking it's balance.

>>11017597

You don't understand, these are actually the same processes, it's just how they're presented to you makes it an illusion where it seems like the answer is 'there on a page'.

Think of it this way, imagine you were trying to guess a 10 letter password to an account, typing each set in, then I give you a thick book with every 10 letter combination and say the password is one of those combinations, have I functionally changed any aspect of the process?

Even if you argue that the keys.lol directories are faster because they display 20 keys at a time, youre simply making the process 20x faster (you aren't for reasons I won't get into), but thats like going from 10^60 years to 10^59 years, it's such a drop in the water.

Like do people not realise there is no difference functionally between going through the gazillions of pages in the key directory and trying gazillions of combinations individually? We've established that an optimised supercomputer designed solely for this purpose would take trillions of years. God I hate normies who can't into logic and maths.

>>11017049
maybe instead of checking website download the actual blockhain and check there?

>>11016832
ud be better off trying to phish private keys from the bogs. stealing is stealing. if ur going to be a thief, at least try something plausable.

>>11017652
Fucking normies!

While it is microscopic, there actually IS a chance that someone discovers your private key by pure luck and steals all your money. And there's nothing you can do about it. lmfao at this being a fiat replacement

>>11017652
I do understand just fine. They are different processes. 'Cracking a wallet' would be an attack directed at a single wallet. That's not what's happening here.

Trying to crack the a single wallet could in theory take as much time as generating every private key for the entire blockchain wallet. Assuming you don't know the balance of any wallet, this method is more time effective.

In other words, n = time to generate all private keys.

It would take you n time to crack a wallet. It would also take you n time to look up the balance of every wallet via it's private key. Obviously you cover more ground doing it the latter way.

brainlet here, how do i run this?

Chink bugmen and pajeets have endless warehouses packed with peasants, sleeping and shitting next to their station waiting to crack a wallet. And they get it done.

>>11017783
that also applies for traditional banking systems

>>11017724
Kek. Everyone knows the bogs cannot be phished!

>>11017831
Not really. You need physical objects to do so, and in addition to that you need security information. Here you can just anonymously guess. Just imagine everyone on earth using crypto. There WILL be someone who guesses someone else's number at some point.

>>11016842

>>11017806

Of course, which is why in my previous step I explained that there are 3 million wallets containing BTC.

In other words your odds of getting a collision is 3*10^6 times more likely than getting a collision with a specific wallet.

The most powerful computer in the world in China is 55 petaflops. This is the equivalent of roughly 6000 overclocked GTX 1080s working in tandem.

Now collisions are FLOPs, so just to be safe lets assume 1 FLOP = 1,000 keys per second testing. So 55 PFLOPs = 55 * million * trillion keys per second.

That equals 55 * 10^6 * 10^12 = 5.5 * 10^19 keys per second.

There are roughly 10^7 seconds in a billion years, so in a billion years you've gone through 10^26 keys.

BUT instead of there being 10^26 keys, remember you only need 1 out of 3 million keys, so we can multiply the effective number of keys tested by 3 million, hell lets make the odds more in your favour so we can keep with base 10 and make it 10 million.

That 10^6, so 10^6 * 10^26 = 10^32. The problem is you need to hit 10^77. That's a difference of 45 zeros.

So to put that into perspective in a billion years with a super computer you have less than a 0.00000000000000000000000000000000000000001% chance of getting something.

>>11018322

*collisions are NOT flops, so in converting one measure of power into another I was excessively generous just to make my point.

>>11018322
You're forgetting some details
Private keys are 32 bit in size, while addresses are only 20 bit in size.On average there are about 2^96 private keys for each bitcoin address.
The LBC team has already found a few wallets by brute-forcing: https://lbc.cryptoguru.org/

>>11016842
fpbp
try another octodecillion years op

>>11016909
Not really with modern compilers.

>>11017783
>While it is microscopic, there actually IS a chance that someone discovers your private key by pure luck and steals all your money. And there's nothing you can do about it. lmfao at this being a fiat replacement
There's also a chance of fiat collapsing to 0.

And let's say that all energy on earth was dedicated solely to cracking a single bitcoin wallet 24/7, it would still be infinitely more likely that fiat collapses to 0 than that a single bitcoin wallet gets cracked.

Good luck cracking my wallet that only contain 34 sats.

>>11018322
Listen here little autist, I never made any claims as to how likely or unlikely cracking a wallet was. Clearly, you aren't from a computer science background. My original comment was contending that the script is "cracking a wallet". If you look at the script, it clearly shows what it's doing, which is spoofing a private key (which is associated with an address) and then accessing the BTC amount from that given address.

This is a completely different programmatic process than cracking a single wallet. Which is what I'm saying here:
>>11017806
>I do understand just fine. They are different processes. 'Cracking a wallet' would be an attack directed at a single wallet. That's not what's happening here.

I encourage you, click my post ID and show me where I said anything regarding the 'likelihood' of cracking a given wallet. On top of that, your analysis of the likelihood of cracking a wallet isn't even right. If we were to look at this in a Bayesian way, there is a lot of apriori information which could definitely improve the speed and narrow down the potential key targets which would improve your p-value.

You sound like some undergrad who took a basic stats class and has become enamored with his hubris. Relax a bit

>>11017935
>115792089237316195423570985008687907853269984665640564039457584007913129639936 bitcoin private keys
>he thinks a few billion people would be enough to cause a problem
KEK

>>11016832
You're retarded if you honestly think you can find a private key with funds when theres 2^256 different private keys out there

>>11017193
>This board is for the discussion of topics related to business, economics, financial markets, securities, currencies (including cryptocurrencies), commodities, etc -- as well as topics relating to starting and running a business.
>(including cryptocurrencies)
this is cryptocurrency related you absolute newfag

>>11017935
lmao you really don't understand it do you

>>11017554
What about eth wallets? Im scared for my Links

>SHA256 can never be cracked!
>It would take super computers 60 trillion years!

Yeah yeah. Just wait a few years. None of this stupid "looking for a wallet" shit will matter.

>>11017554
>The problem is that BTC is AES 256 bits, it would take a computer the size of the moon 1 trillion * trillion * trillion * trillion * trillion * trillion * trillion * trillion years.
but 256 is just twice as large as 128. How is this possible?

>>11017663
but then how do you get the priv key?

yall have a lot to learn

You'd get more if you used your CPU to mine bitcoin instead.

I did the math last year, mining brings in 50x-100x more than trying to bruteforce a wallet, statistically

>>11020331
Do you also think 1000 is twice as much as 10

Some of you morons need to pick up a calculator and run 2x2x2.... 256 times or however long until you get bored and/or realize pulling this shit off is functionally impossible.

>>11017783
Multisig

>>11016832
How do you manage to assemble the molecules in your brain to write a script but can’t put one equation into a calculator???

>>11016832
came back to see that OP is still mining wallets

>>11017783
You literally have a higher chance to self combust.

https://youtu.be/ObiqJzfyACM

14:20 if you want to know how big 52! Is. You people are legit retarded for even trying.

>>11021137

YOU WILL NEVER FIND A KEY.

2^256=1.1579209e+77
52! = 8.0658175e+67

>>11020331
256 bits not 256 singular units (like our traditional numbers). That means each of the 256 bits can have one of two values so there are 2^256 possible values for the entire key vs. 2^128. So instead of doubling it once, you're actually doubling it 128 times.

>>11020406
>>11021109
>>11021128
>>11021137
These threads are hilarious

>>11016832
>2 days

You will have to run that script for at least 10 days. 40 days at most.

>>11016832
there are 904625697166532776746648320380374280100293470930272690489102837043110636675 PAGES of eth wallets you dumb nigger. Multiply that number by ~100 to find the number of eth wallets there are
You're more likely to win the lottery 10x in a row than finding one btc address with any amount at all

>>11016832
there's a running project that has multiple people join "mining" pools to mine these addresses.

They generate like 25 trillion keys a day, and have generated 32 Quadrillion keys and found a total of 3 bitcoin or so.

>>11020331
Its bits, so it's computer storage terms, each additional bit doubles the amount of storage.

So 129 bits is twice as large as 128 bits. And 130 bits is twice as large as 129, and so on.

double for each additional bit.

>>11021255
You mean 40 days at most because at that point you're definitely not lucky or blessed enough to have this, right?

Also, let's say, hypothetically, in the rare event that you get access to one of these quintigorillion addresses, what would you do?

I mean you could steal it but fuck man I don't know. It's stealing. It ain't matter if you can't be traced. It's karma kicking your ass for the rest of your days if you take a huge enough amount. Like some nigga got 10k BTC and you're going to take how many? 5? 10? 100? You're just going to leave it there?

Imagine if someone got access to the richest address, and dumped the private key in here. Oh lord. That'd be stupidly funny.

>>11021603
Even speculating on this event is retarded. That’s exactly how IMPROBABLE IT IS. A bunch of “what if-ers”. What if you die on your commute to work? Have you thought about what your going to do with your current holdings? Probably not. Seriously how low is the IQ on these boards.

>>11016832

The Sun will probably burn out before you find one.

>>11016832
2^160 combinations
0.5 tries a second.
Hahahahaha