alevlaslo
|
 |
October 16, 2020, 11:34:00 AM |
|
the private key can be calculated in a million years on a single processor or in 2 years one of the 590000 keys from addresses with a balance of more than 1 bitcoin https://github.com/traxm/Bitcoin-Micro-Collider/@alevlaslo, generally when you see coins on addresses that look like this: 1xxxxxxxxxxxxxxxxxxxxxxxxxy1kmdGr, they are gone forever. If we ever find a way to get the private key for that address (if there is any), we will face much more worse problems than those you can imagine. Stupid, in my opinion. Nobody can ever spend that money. Let the stupid ones burn their bitcoins. They make them more valuable without knowing it.  Yes, from these addresses, the signature does not fit on the graphic code or even in the text buffer
|
Sale the first NFT of the first foto
|
|
|
|
nullius
|
 |
October 16, 2020, 02:29:55 PM |
|
Baloney. Well, have fun trying, as I said.
Good link ( forum thread), but it needs the public key. It will not work with a Bitcoin address. Also, if you think that it will crack public keys in a reasonable time—as I said, have fun trying!
|
|
|
|
bigvito19
|
 |
October 16, 2020, 02:35:50 PM |
|
Baloney. Well, have fun trying, as I said.
Good link ( forum thread), but it needs the public key. It will not work with a Bitcoin address. Also, if you think that it will crack public keys in a reasonable time—as I said, have fun trying! Who cares what you said, I said it wouldn't take a million years. I never said it it would crack in a reasonable time!
|
|
|
|
alevlaslo
|
 |
October 16, 2020, 03:22:45 PM |
|
it takes a million years to select one address, but 2 years is enough to select one of 590 thousands 1+ BTC addresses
however, 12000 keys per second is very small on the processor, how much will the video card give if you write the same program?
|
Sale the first NFT of the first foto
|
|
|
bigvito19
|
 |
October 16, 2020, 03:48:47 PM |
|
it takes a million years to select one address, but 2 years is enough to select one of 590 thousands 1+ BTC addresses
however, 12000 keys per second is very small on the processor, how much will the video card give if you write the same program?
At 12000 keys per second, you're not hitting no address at that speed. Depends on where the program searching at. How did you come up with 2 years for 590k address because that's not enough addresses to check for in a big space. And you do know 1+ btc addresses is no different than 100+ btc addresses.
|
|
|
|
alevlaslo
|
 |
October 16, 2020, 04:36:44 PM |
|
for an average video card, it takes a million years for one address, I thought that my i5 processor is not much inferior to this video card
|
Sale the first NFT of the first foto
|
|
|
nullius
|
 |
October 16, 2020, 05:24:41 PM |
|
it takes a million years to select one address, but 2 years is enough to select one of 590 thousands 1+ BTC addresses
however, 12000 keys per second is very small on the processor, how much will the video card give if you write the same program? [blah] This discussion is off-topic on the Vanitygen thread; but I feel a need to stick a spike in what is essentially idiot-FUD over Bitcoin’s security. To be clear, you are full of shit.- 2160 search space of Hash160s
- 12000 trials per second
- 590000 Bitcoin addresses with ≥ 1 BTC (assuming that your information is correct; I can’t be bothered to investigate, when it cannot make any appreciable difference)
- 86400 seconds per day, 365.2425 days per year
Ignoring the question of how different script types are handled: On average, what is the expected number of years for you to hit any one of the desired addresses? $ bc -l ((2^160 / 590000) / 12000) / (86400 * 365.2425) 6541404408567194639988331071041.54191444061112656733
Well, have fun trying, as I said.
|
|
|
|
LoyceV
Legendary
Offline
Activity: 3584
Merit: 18203
Thick-Skinned Gang Leader and Golden Feather 2021
|
 |
October 16, 2020, 06:34:34 PM |
|
590000 Bitcoin addresses with ≥ 1 BTC (assuming that your information is correct; I can’t be bothered to investigate, when it cannot make any appreciable difference) Let's see: I count 815446 Bitcoin addresses ≥ 1 BTC.
If you want to take a shot to find the private key of a rich wallet, try those: address balance 35hK24tcLEWcgNA4JxpvbkNkoAcDGqQPsP 22750211349798 37XuVSEpWW4trkfmvWzegTHQt7BdktSKUs 9450583134507 34EiJfy4jGF32M37aQ2ZobupwiRQWa1Siy 9285724546987 1FeexV6bAHb8ybZjqQMjJrcCrHGW9sb6uF 7995720489764 3Kzh9qAqVWQhEsfQz7zEQL1EuSx5tyNLNS 7429382157655 34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo 7343627940660 1HQ3Go3ggs8pFnXuHVHRytPCq5fGG8Hbhx 6937022461903 37tRFZw7n94Jddq6TfVs3MbCXmDX6eMfeY 6810156631276 3JurbUwpsAPqvUkwLM5CtwnEWrNnUKJNoD 6523671378350 bc1qgdjqv0av3q56jvd82tkdjpy7gdp9ut8tlqmgrpmv24sq90ecnvqqjwvw97 6350099542777 1P5ZEDWTKTFGxQjZphgWPQUpe554WKDfHQ 5882565501662 385cR5DM96n1HvBDMzLHPYcw89fZAXULJP 5580189332845 1LdRcdxfbSnmCYYNdeYpUnztiYzVfBEQeC 5388005997485 386eAUqL3ZNZPmHeABXLo658DTQuJeLzUR 5228631583003 1AC4fMwgY8j9onSbXEWeH6Zan8QGMSdmtA 5183035806607 1LruNZjwamWJXThX2Y8C2d47QqhAkkc5os 4400007825417 38UmuUqPCrFmQo4khkomQwZ4VbY2nZMJ67 4323343648365 bc1q5shngj24323nsrmxv99st02na6srekfctt30ch 4000032739903 3D8qAoMkZ8F1b42btt2Mn5TyN7sWfa434A 3999991875357 1BX5MXZ95rMiQJBH9yKpcmbAt9VcfyAfHE 3748301367714 17hf5H8D6Yc4B7zHEg3orAtKn7Jhme7Adx 3600000232699 3LCGsSmfr24demGvriN4e3ft8wEcDuHFqh 3420039122238 13JQwoSLLR3ffXwswe2HCTK9oq4i8MWK3q 3101001173650 12ib7dApVFvg82TXKycWBNpN8kFyiAN1dr 3100006932578 12tkqA9xSoowkzoERHMWNKsTey55YEBqkv 2815105678199 3H5JTt42K7RmZtromfTSefcMEFMMe18pMD 2653231784217 3Pja5FPK1wFB9LkWWJai8XYL1qjbqqT9Ye 2616701098509 1NH8vuaJaMXbtj4Qx6iFaQY8btdVcAn9iz 2449535094560 1ANjYHibCQ6FzagLfeXubC8SQYDfUS5wAJ 2396900026383 1AnwDVbwsLBVwRfqN2x9Eo4YEJSPXo2cwG 2322761527043 1932eKraQ3Ad9MeNBHb14WFQbNrLaKeEpT 2289999034779 14eQD1QQb8QFVG8YFwGz7skyzsvBLWLwJS 2221116586406 3EcoyfYvsBXBwdbdf4SY6DAU84kqS6mNLs 2170000479732 1aXzEKiDJKzkPxTZy9zGc3y1nCDwDPub2 2120481013155 3HroDXv8hmzKRtaSfBffRgedKpru8fgy6M 2012449485992 17rm2dvb439dZqyMe2d4D6AQJSgg6yeNRn 2000800083113 1HEWtVTNHApfVsK923gYYAuLUzzwweQGWj 2000100106691 1PeizMg76Cf96nUQrYg8xuoZWLQozU5zGW 1941442998326 19iqYbeATe4RxghQZJnYVFU4mjUUu76EA6 1858662993936 3JPauiFhP4K3AevmgNMFfMSN7pLZbuADJQ 1800100011082 3JSssZCJ3PHEdgNv7hzNE26EEzzvYNjZLy 1700100006032 3EiEN1JJCudBgAwL7c6ajqnPzx9LrK1VT6 1688134484379 1GR9qNz7zgtaW5HwwVpEJWMnGWhsbsieCG 1574555580702 3BMEXqGpG4FxBA1KWhRFufXfSTRgzfDBhJ 1556323781534 3N9an8wv4SYi3FVXs3xR5k2AqXeNZiw2mf 1549989103483 38Md7BghVmV7XUUT1Vt9CvVcc5ssMD6ojt 1503326226463 1KUr81aewyTFUfnq4ZrpePZqXixd59ToNn 1499999858633 3DwVjwVeJa9Z5Pu15WHNfKcDxY5tFUGfdx 1450000014976 3FrM1He2ZDbsSKmYpEZQNGjFTLMgCZZkaf 1400001439816 1BZaYtmXka1y3Byi2yvXCDG92Tjz7ecwYj 1400000055945 1U3d67BaLpwudFEZRtDDAm7bTCQkygUcV 1388237690339 Good luck 
|
| | Peach BTC bitcoin | │ | Buy and Sell Bitcoin P2P | │ | . .
▄▄███████▄▄ ▄██████████████▄ ▄███████████████████▄ ▄█████████████████████▄ ▄███████████████████████▄ █████████████████████████ █████████████████████████ █████████████████████████ ▀███████████████████████▀ ▀█████████████████████▀ ▀███████████████████▀ ▀███████████████▀ ▀▀███████▀▀
▀▀▀▀███████▀▀▀▀ | | EUROPE | AFRICA LATIN AMERICA | | | ▄▀▀▀ █ █ █ █ █ █ █ █ █ █ █ ▀▄▄▄ |
███████▄█ ███████▀ ██▄▄▄▄▄░▄▄▄▄▄ █████████████▀ ▐███████████▌ ▐███████████▌ █████████████▄ ██████████████ ███▀███▀▀███▀ | . Download on the App Store | ▀▀▀▄ █ █ █ █ █ █ █ █ █ █ █ ▄▄▄▀ | ▄▀▀▀ █ █ █ █ █ █ █ █ █ █ █ ▀▄▄▄ |
▄██▄ ██████▄ █████████▄ ████████████▄ ███████████████ ████████████▀ █████████▀ ██████▀ ▀██▀ | . GET IT ON Google Play | ▀▀▀▄ █ █ █ █ █ █ █ █ █ █ █ ▄▄▄▀ |
|
|
|
mikeywith
Legendary
Offline
Activity: 2506
Merit: 6705
be constructive or S.T.F.U
|
 |
October 17, 2020, 01:29:10 AM Last edit: October 17, 2020, 12:19:12 PM by mikeywith Merited by ABCbits (2), joniboini (2) |
|
if it takes a million years for 1 video card to search, then a million video cards will be found in 1 year. Unlike mining, when it is extracted regularly for a little bit, the process of searching for keys takes a long time, but the reward is more significant.
The average video card would cost you about $200, so that's $200,000,000 in cards alone, it's safe to assume that you will need 30% of that in other pieces of equipment (apparently a GPU isn't a stand-alone device) so that is another $,60,000,000. You will also need a few million dollars in labor and shit. The average GPU would consume about 120w per hour to do the "guessing" job, that will be 2.9kwh a day, the average electricity cost is 5 cents per kWh, so you will pay $0.145*1,000,000 = $145,000 daily, in other words, $52,925,000 a year. A million GPUs would need 120 megawatts of power, and perhaps another 10MW to cool that down, you will need to get your own transformers and build your own infrastructure to attempt that kind of shit, you will be looking at close to 1 billion dollars in total by the end of the year including all the other expenses, that is close to 0.5% of the total value of bitcoin, you will spend a 100,000 BTC in an "attempt" to hit a collision of some type, only to realize that those funds were moved to a thousand different addresses, or at best case scenario, whatever you may have found isn't worth a 100,000 BTC anyway. On the other hand, if you use those 1M GPUs for mining you make $620,000 in profit (after the power bill of 5 cents per kWh), so in a year you make 1/4 of a billion-dollar that is clean money without the chance of actually "stealing" some else's bitcoin. One-way hash functions are built in a way that makes them economically less incentive compared to when you harness the same resources to make money else way, so if profit is the only "goal" it makes no sense to attempt that unless you want to gamble.
|
|
|
|
alevlaslo
|
 |
October 17, 2020, 05:10:37 AM |
|
it takes a million years to select one address, but 2 years is enough to select one of 590 thousands 1+ BTC addresses
however, 12000 keys per second is very small on the processor, how much will the video card give if you write the same program? [blah] This discussion is off-topic on the Vanitygen thread; but I feel a need to stick a spike in what is essentially idiot-FUD over Bitcoin’s security. To be clear, you are full of shit.- 2160 search space of Hash160s
- 12000 trials per second
- 590000 Bitcoin addresses with ≥ 1 BTC (assuming that your information is correct; I can’t be bothered to investigate, when it cannot make any appreciable difference)
- 86400 seconds per day, 365.2425 days per year
Ignoring the question of how different script types are handled: On average, what is the expected number of years for you to hit any one of the desired addresses? $ bc -l ((2^160 / 590000) / 12000) / (86400 * 365.2425) 6541404408567194639988331071041.54191444061112656733
Well, have fun trying, as I said. you forgot to divide the result by 2^96 because there are so many private keys for each address
|
Sale the first NFT of the first foto
|
|
|
nullius
|
[...] To be clear, you are full of shit.- 2160 search space of Hash160s
- [...]
[...] you forgot to divide the result by 2^96 because there are so many private keys for each address I forgot nothing. The 2 96 is divided out of (slightly less than) 2 256 valid private/public keypairs, for the 2 160 search space that I stated. You clearly have no fucking idea what you are talking about. Also, you are a spammer peddling a scam program with posts that are off-topic on the Vanitygen thread.
|
|
|
|
alevlaslo
|
 |
October 18, 2020, 06:32:47 AM Last edit: October 18, 2020, 06:49:58 AM by alevlaslo |
|
there is no difference between 1 and 580000 addresses, the speed is limited by the random number generator
why can't I set more than 19 characters to Vanitygen64, in case I get lucky and the whole address is generated quickly? Probably the fact is that this is a calculation and not a random generation, faster than the estimated time calculation is impossible, unlike random generenation in another program
|
Sale the first NFT of the first foto
|
|
|
bigvito19
|
 |
October 18, 2020, 10:04:42 AM |
|
there is no difference between 1 and 580000 addresses, the speed is limited by the random number generator
why can't I set more than 19 characters to Vanitygen64, in case I get lucky and the whole address is generated quickly? Probably the fact is that this is a calculation and not a random generation, faster than the estimated time calculation is impossible, unlike random generenation in another program
This one you can put in the whole address https://bitcointalk.org/index.php?topic=5112311.0https://github.com/JeanLucPons/VanitySearch
|
|
|
|
BlackHatCoiner
Legendary
Offline
Activity: 1792
Merit: 8651
|
 |
October 18, 2020, 10:22:29 AM |
|
I just did a small research about how difficult it is to guess a bitcoin address. All private keys are 2256 but the total addresses aren't that many. They are 2160 as @nullius said.
Now let's compare 2160 with another huge number:
14,615,016,400,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 (2160) 133,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 (Total atoms that exist on our planet) That answer comes from an estimation of the number of atoms in each of Earth's elements, like Iron, Oxygen, Silicon, Magnesium, Sulfur … etc
It's scary to think how many different combinations of addresses can exist. Imagine that one water drop contains about 5 sextillion atoms. (5.01 x 1021)
Imagine picking one atom randomly from the earth and expecting someone to guess it. When your computer generates an address is like picking one atom from ~10,000 different Earths.
You can't brute force a bitcoin address. You just can't.
|
|
|
|
bigvito19
|
 |
October 18, 2020, 11:12:55 AM |
|
I just did a small research about how difficult it is to guess a bitcoin address. All private keys are 2256 but the total addresses aren't that many. They are 2160 as @nullius said.
Now let's compare 2160 with another huge number:
14,615,016,400,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 (2160) 133,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 (Total atoms that exist on our planet) That answer comes from an estimation of the number of atoms in each of Earth's elements, like Iron, Oxygen, Silicon, Magnesium, Sulfur … etc
It's scary to think how many different combinations of addresses can exist. Imagine that one water drop contains about 5 sextillion atoms. (5.01 x 1021)
Imagine picking one atom randomly from the earth and expecting someone to guess it. When your computer generates an address is like picking one atom from ~10,000 different Earths.
You can't brute force a bitcoin address. You just can't.
That's where y'all get it wrong at, y'all keep trying to brute force the whole space. You have to know exactly where the range of the address is in then brute force that.
|
|
|
|
alevlaslo
|
 |
October 18, 2020, 11:13:42 AM |
|
low probability is not a hindrance, there is a person who won the lottery twice on the same combination, just adjust your thoughts correctly, and the result will attract
|
Sale the first NFT of the first foto
|
|
|
alevlaslo
|
 |
October 18, 2020, 11:15:35 AM |
|
there is no difference between 1 and 580000 addresses, the speed is limited by the random number generator
why can't I set more than 19 characters to Vanitygen64, in case I get lucky and the whole address is generated quickly? Probably the fact is that this is a calculation and not a random generation, faster than the estimated time calculation is impossible, unlike random generenation in another program
This one you can put in the whole address https://bitcointalk.org/index.php?topic=5112311.0https://github.com/JeanLucPons/VanitySearchthank you!
|
Sale the first NFT of the first foto
|
|
|
BlackHatCoiner
Legendary
Offline
Activity: 1792
Merit: 8651
|
 |
October 18, 2020, 11:16:12 AM |
|
That's where y'all get it wrong at, y'all keep trying to brute force the whole space. You have to know exactly where the range of the address is in then brute force that. But you can't know within what range was the private key of the address once it was chosen. Can you explain it a little more? I'm not an expert.
|
|
|
|
bigvito19
|
 |
October 18, 2020, 01:12:39 PM |
|
That's where y'all get it wrong at, y'all keep trying to brute force the whole space. You have to know exactly where the range of the address is in then brute force that. But you can't know within what range was the private key of the address once it was chosen. Can you explain it a little more? I'm not an expert. First of all you should be going after addresses with its public key already exposed. That's 2^128 search range right there. You should be generating addresses/keys from the desired public key. The next step would be to find a partial collision of the key and brute force the remaining of the key or half 2^128 to 2^64.
|
|
|
|
|