Topic: Pollard's kangaroo ECDLP solver - page 74. (Read 60698 times)
https://i.imgur.com/vEUcFv8l.jpg
How expensive for buy one?
Are you AI. research or AI. Developer?
most people use high-end CUDA card work on AI. Training
buy one for use personal?
Quote
Oh it says what the keyspace size is when you start the program but it must be wrong, I didn't actually calculate it myself
It does tell you the range width (keyspace search size) and the expected operations. The range width is spot on, the expected operations is a guesstimated "expected" amount of operations to perform to solve the key.
I dunno man, so far I've gathered about 20,000 pubkeys to addresses that still have over 6 btc on them. I'm going to run them in the pollard kangaroo program in the keyspace 1 - 2^69 ( ͡° ͜ʖ ͡°) and possibly will find a private key in the low bit range! But the chances that anyone is legitimately using a private key in a keyspace less than 2^128 is pretty slim..
If you still want to go along with this then I suggest not letting it run for more than a day, because you're looking for private keys with 59 leading zero bits in them. Chances are if these addresses have a seed phrase associated with them, neither it's master private key or any of its child keys were derived in a way such that there are several zero bits at the beginning.
Maybe use a random prefix that has a mixture of 1s and 0s which is more likely to hit than all zeros.
Yeah I gave up on that after an hour lol
Here's an interesting random fact about puzzle address #120, in one whole day a Tesla V100 GPU can search 0.00000001% of the keyspace using the pollard kangaroo software. That is equal to approx. 2^93..
But here is match for V100; it checks (by jumping) 138,240,000,000,000 points(keys) for a distinguished bit, per day. 1600 Mkey/s * 60*60*24 .
2^93 = 9,903,520,314,283,042,199,192,993,792
Oh it says what the keyspace size is when you start the program but it must be wrong, I didn't actually calculate it myself
Yeah I gave up on that after an hour lol
Here's an interesting random fact about puzzle address #120, in one whole day a Tesla V100 GPU can search 0.00000001% of the keyspace using the pollard kangaroo software. That is equal to approx. 2^93..
How long need for puzzle #120 address?
I will try you method tonight with 8 hour for check result test
I dunno man, so far I've gathered about 20,000 pubkeys to addresses that still have over 6 btc on them. I'm going to run them in the pollard kangaroo program in the keyspace 1 - 2^69 ( ͡° ͜ʖ ͡°) and possibly will find a private key in the low bit range! But the chances that anyone is legitimately using a private key in a keyspace less than 2^128 is pretty slim..
If you still want to go along with this then I suggest not letting it run for more than a day, because you're looking for private keys with 59 leading zero bits in them. Chances are if these addresses have a seed phrase associated with them, neither it's master private key or any of its child keys were derived in a way such that there are several zero bits at the beginning.
Maybe use a random prefix that has a mixture of 1s and 0s which is more likely to hit than all zeros.
Yeah I gave up on that after an hour lol
Here's an interesting random fact about puzzle address #120, in one whole day a Tesla V100 GPU can search 0.00000001% of the keyspace using the pollard kangaroo software. That is equal to approx. 2^93..
But here is match for V100; it checks (by jumping) 138,240,000,000,000 points(keys) for a distinguished bit, per day. 1600 Mkey/s * 60*60*24 .
2^93 = 9,903,520,314,283,042,199,192,993,792
Y'all already know all the other keys are in 2^128, thinking otherwise is a waste of time.
may be can see Pollard's kangaroo ECDLP solver + plus new technic or mix other algorithm to solve brute-forcing betterThat would be the next step then.
Y'all already know all the other keys are in 2^128, thinking otherwise is a waste of time.
I think human create bitcoin. (bitcoin create by human, not god) so human can possible crack bitcoin. possible in future (but now for now)
science, research project will be not give up (if can solve bitcoin, they will be got bit-name and famous right) PhD etc.
some part will be continue crack bitcoin and give some news to surprise when crack it done
it not waste of time.
I believe bitcoin just starter and on early stats or just proof of concept on first generation. (so next generation bitcoin will be perfect and powerful more than now)
money can not destroy bitcoin and bitcoin value never zero
only way can destroy bitcoin is crack private key
some government possible to try crack bitcoin (may be)
I think future bitcoin original will be upgrade or change network when quantum computer is coming
of Course bitcoin may be change to quantum bitcoin or gigabit bitcoin or high enough can not crack for 50 year
sorry for of topic
may be can see Pollard's kangaroo ECDLP solver + plus new technic or mix other algorithm to solve brute-forcing better
Y'all already know all the other keys are in 2^128, thinking otherwise is a waste of time.
I think only puzzle that easy to crack because puzzle create by using low bit with allow to crack
Reference bitcoin version 0.1 or alpha version start to use key 256 bit from first-time
That possible to not easy to crack it
Yeah I gave up on that after an hour lol
Here's an interesting random fact about puzzle address #120, in one whole day a Tesla V100 GPU can search 0.00000001% of the keyspace using the pollard kangaroo software. That is equal to approx. 2^93..
How long need for puzzle #120 address?
I will try you method tonight with 8 hour for check result test
I dunno man, so far I've gathered about 20,000 pubkeys to addresses that still have over 6 btc on them. I'm going to run them in the pollard kangaroo program in the keyspace 1 - 2^69 ( ͡° ͜ʖ ͡°) and possibly will find a private key in the low bit range! But the chances that anyone is legitimately using a private key in a keyspace less than 2^128 is pretty slim..
If you still want to go along with this then I suggest not letting it run for more than a day, because you're looking for private keys with 59 leading zero bits in them. Chances are if these addresses have a seed phrase associated with them, neither it's master private key or any of its child keys were derived in a way such that there are several zero bits at the beginning.
Maybe use a random prefix that has a mixture of 1s and 0s which is more likely to hit than all zeros.
Yeah I gave up on that after an hour lol
Here's an interesting random fact about puzzle address #120, in one whole day a Tesla V100 GPU can search 0.00000001% of the keyspace using the pollard kangaroo software. That is equal to approx. 2^93..
I dunno man, so far I've gathered about 20,000 pubkeys to addresses that still have over 6 btc on them. I'm going to run them in the pollard kangaroo program in the keyspace 1 - 2^69 ( ͡° ͜ʖ ͡°) and possibly will find a private key in the low bit range! But the chances that anyone is legitimately using a private key in a keyspace less than 2^128 is pretty slim..
If you still want to go along with this then I suggest not letting it run for more than a day, because you're looking for private keys with 59 leading zero bits in them. Chances are if these addresses have a seed phrase associated with them, neither it's master private key or any of its child keys were derived in a way such that there are several zero bits at the beginning.
Maybe use a random prefix that has a mixture of 1s and 0s which is more likely to hit than all zeros.
Yep I updated my program so that it saves all the public keys to a txt file
And I've been running it all day with no limits from blockchain.com so I think for that specific api call there are no limits, but I could be wrong!
Thank you
Script it is work as well, I try already.
problem Pollard's kangaroo ECDLP solver can use with only public key
and public key have only bitcoin address that have transaction
people know about this already, people smart to move bitcoin to new address that not have any transaction
and use new bitcoin address (segwit) not show public key , it have legacy only show public key
I dunno man, so far I've gathered about 20,000 pubkeys to addresses that still have over 6 btc on them. I'm going to run them in the pollard kangaroo program in the keyspace 1 - 2^69 ( ͡° ͜ʖ ͡°) and possibly will find a private key in the low bit range! But the chances that anyone is legitimately using a private key in a keyspace less than 2^128 is pretty slim..
Yep I updated my program so that it saves all the public keys to a txt file
And I've been running it all day with no limits from blockchain.com so I think for that specific api call there are no limits, but I could be wrong!
Thank you
Script it is work as well, I try already.
problem Pollard's kangaroo ECDLP solver can use with only public key
and public key have only bitcoin address that have transaction
people know about this already, people smart to move bitcoin to new address that not have any transaction
and use new bitcoin address (segwit) not show public key , it have legacy only show public key
I pushed my little public key gathering script to github if anybody wants it!
https://github.com/GonzoTheDev/BitcoinPublicKeyGrabber
https://github.com/GonzoTheDev/BitcoinPublicKeyGrabber
Could you help to write script to save output to csv collect?
Can blockchain.info use for get data massive over 100k address without get ban ip address?
Yep I updated my program so that it saves all the public keys to a txt file
And I've been running it all day with no limits from blockchain.com so I think for that specific api call there are no limits, but I could be wrong!
I pushed my little public key gathering script to github if anybody wants it!
https://github.com/GonzoTheDev/BitcoinPublicKeyGrabber
https://github.com/GonzoTheDev/BitcoinPublicKeyGrabber
Could you help to write script to save output to csv collect?
Can blockchain.info use for get data massive over 100k address without get ban ip address?
I pushed my little public key gathering script to github if anybody wants it!
https://github.com/GonzoTheDev/BitcoinPublicKeyGrabber
https://github.com/GonzoTheDev/BitcoinPublicKeyGrabber
Is it actually stealing though?
Cracking addresses that were meant to be cracked such as the puzzle transactions is not sealing of course. But if I were you, in the hypothetical event you managed to find the private key for some random address, I would leave them alone and not ever share the results with anyone. It may be that the owner intentionally left the bitcoins stowed away to use many years later e.g Hal's children.
I guess that is a good point. I doubt anyone will ever crack one of the wallets I posted though lol
Is it actually stealing though?
Cracking addresses that were meant to be cracked such as the puzzle transactions is not sealing of course. But if I were you, in the hypothetical event you managed to find the private key for some random address, I would leave them alone and not ever share the results with anyone. It may be that the owner intentionally left the bitcoins stowed away to use many years later e.g Hal's children.
Jump to: