Topic: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED== - page 41. (Read 56094 times)
September 26, 2021, 02:40:59 PM
enfarktus, uses only 1 processor core?
August 03, 2021, 11:15:51 AM
IMO this thread should have been self-moderated so we can put a local rule "obnoxious dumps of keys and bytes should be done on Github Gist or Pastebin", the sheer volume of data being passed around on this thread is hard to keep track of and makes following actual discussions hard. 
August 03, 2021, 11:14:58 AM
i have one question....!!!!!!!!!! is this challenge true....?
i mean, is it serous..?
i just smell like scammers here..?
because ...why no body till now cracked #64..although it is 16 digits length.
i will make more clear :
challenges 61,62,63 and 64 are same length = 16 digits.
how they cracked 61+62+63 and no one can crack 64 since july 2019...(last time they cracked #63)..?
Because 64 is two times larger keyspace than 63, digits do no matter here.i mean, is it serous..?
i just smell like scammers here..?
because ...why no body till now cracked #64..although it is 16 digits length.
i will make more clear :
challenges 61,62,63 and 64 are same length = 16 digits.
how they cracked 61+62+63 and no one can crack 64 since july 2019...(last time they cracked #63)..?
61 = 1
62 = 2, 3
63 = 4, 5, 6, 7
64 = 8, 9 , a, b, c, d, e, f
It's just a huge keyspace.
yes, you are absolutely right..
thanks for the reply.
i was just asking in two years no one claimed this damn challenge(#64).
how some one will solve #66 and up..?
August 03, 2021, 09:51:34 AM
i have one question....!!!!!!!!!! is this challenge true....?
i mean, is it serous..?
i just smell like scammers here..?
because ...why no body till now cracked #64..although it is 16 digits length.
i will make more clear :
challenges 61,62,63 and 64 are same length = 16 digits.
how they cracked 61+62+63 and no one can crack 64 since july 2019...(last time they cracked #63)..?
Because 64 is two times larger keyspace than 63, digits do no matter here.i mean, is it serous..?
i just smell like scammers here..?
because ...why no body till now cracked #64..although it is 16 digits length.
i will make more clear :
challenges 61,62,63 and 64 are same length = 16 digits.
how they cracked 61+62+63 and no one can crack 64 since july 2019...(last time they cracked #63)..?
61 = 1
62 = 2, 3
63 = 4, 5, 6, 7
64 = 8, 9 , a, b, c, d, e, f
It's just a huge keyspace.
yes, you are absolutely right..
thanks for the reply.
i was just asking in two years no one claimed this damn challenge(#64).
how some one will solve #66 and up..?
August 03, 2021, 08:59:51 AM
i have one question....!!!!!!!!!! is this challenge true....?
i mean, is it serous..?
i just smell like scammers here..?
because ...why no body till now cracked #64..although it is 16 digits length.
i will make more clear :
challenges 61,62,63 and 64 are same length = 16 digits.
how they cracked 61+62+63 and no one can crack 64 since july 2019...(last time they cracked #63)..?
Because 64 is two times larger keyspace than 63, digits do no matter here.i mean, is it serous..?
i just smell like scammers here..?
because ...why no body till now cracked #64..although it is 16 digits length.
i will make more clear :
challenges 61,62,63 and 64 are same length = 16 digits.
how they cracked 61+62+63 and no one can crack 64 since july 2019...(last time they cracked #63)..?
61 = 1
62 = 2, 3
63 = 4, 5, 6, 7
64 = 8, 9 , a, b, c, d, e, f
It's just a huge keyspace.
August 03, 2021, 08:50:20 AM
i have one question....!!!!!!!!!! is this challenge true....?
i mean, is it serous..?
i just smell like scammers here..?
because ...why no body till now cracked #64..although it is 16 digits length.
i will make more clear :
challenges 61,62,63 and 64 are same length = 16 digits.
how they cracked 61+62+63 and no one can crack 64 since july 2019...(last time they cracked #63)..?
i mean, is it serous..?
i just smell like scammers here..?
because ...why no body till now cracked #64..although it is 16 digits length.
i will make more clear :
challenges 61,62,63 and 64 are same length = 16 digits.
how they cracked 61+62+63 and no one can crack 64 since july 2019...(last time they cracked #63)..?
July 20, 2021, 05:19:38 PM
How much is 1 Yottakeys/s for (Pollard / Rho) ?
For Pollard / Rho you need simple point additions.
Wikipedia: yotta 10^24 = 1000000000000000000000000
1 Yottakeys/s = 10^24 keys/s
To compare it with the Bitcoin network ~100 Ehash/s = 100000000000000000000 hash/s
1 Yottakeys/s = 10000 x more keys than hashes. But hashes are more complicated to calculate.
What would the relation (hash)/(point addition) be for devices?
Or, how many point additions could (if built for this purpose) calculate a miner, that let's say hashes with 1 Thashes/s = 1000000000000 hashes/s?
July 20, 2021, 03:27:09 PM
How much is 1 Yottakeys/s for (Pollard / Rho) ?
For Pollard / Rho you need simple point additions.
Wikipedia: yotta 10^24 = 1000000000000000000000000
1 Yottakeys/s = 10^24 keys/s
July 20, 2021, 08:18:10 AM
if scan all it use a time too much
Depent of your speed, i made some calculations based on the speed, the time is for scan all the range in that bit space:
Code:
Puzzle 120 @ 1 Terakeys/s : 21074771622667996 years
Puzzle 120 @ 1 Petakeys/s : 21074771622667 years
Puzzle 120 @ 1 Exakeys/s : 21074771622 years
Puzzle 120 @ 1 Zettakeys/s : 21074771 years
Puzzle 120 @ 1 Yottakeys/s : 21074 years
Puzzle 160 @ 1 Terakeys/s : 23171956451847141650870193314 years
Puzzle 160 @ 1 Petakeys/s : 23171956451847141650870193 years
Puzzle 160 @ 1 Exakeys/s : 23171956451847141650870 years
Puzzle 160 @ 1 Zettakeys/s : 23171956451847141650 years
Puzzle 160 @ 1 Yottakeys/s : 23171956451847141 years
Puzzle 256 @ 1 Terakeys/s : 1835871531540401373407708412745559168131740612197318060720 years
Puzzle 256 @ 1 Petakeys/s : 1835871531540401373407708412745559168131740612197318060 years
Puzzle 256 @ 1 Exakeys/s : 1835871531540401373407708412745559168131740612197318 years
Puzzle 256 @ 1 Zettakeys/s : 1835871531540401373407708412745559168131740612197 years
Puzzle 256 @ 1 Yottakeys/s : 1835871531540401373407708412745559168131740612 years
Puzzle 120 @ 1 Petakeys/s : 21074771622667 years
Puzzle 120 @ 1 Exakeys/s : 21074771622 years
Puzzle 120 @ 1 Zettakeys/s : 21074771 years
Puzzle 120 @ 1 Yottakeys/s : 21074 years
Puzzle 160 @ 1 Terakeys/s : 23171956451847141650870193314 years
Puzzle 160 @ 1 Petakeys/s : 23171956451847141650870193 years
Puzzle 160 @ 1 Exakeys/s : 23171956451847141650870 years
Puzzle 160 @ 1 Zettakeys/s : 23171956451847141650 years
Puzzle 160 @ 1 Yottakeys/s : 23171956451847141 years
Puzzle 256 @ 1 Terakeys/s : 1835871531540401373407708412745559168131740612197318060720 years
Puzzle 256 @ 1 Petakeys/s : 1835871531540401373407708412745559168131740612197318060 years
Puzzle 256 @ 1 Exakeys/s : 1835871531540401373407708412745559168131740612197318 years
Puzzle 256 @ 1 Zettakeys/s : 1835871531540401373407708412745559168131740612197 years
Puzzle 256 @ 1 Yottakeys/s : 1835871531540401373407708412745559168131740612 years
I know there is no puzzle 256, but that is the exact time for the real wallets.
With Pollard / Rho we calculate:
Code:
Puzzle 120 @ 1 Terakeys/s : ~ 10 days
Puzzle 120 @ 1 Yottakeys/s : < 1 sec
Puzzle 160 @ 1 Terakeys/s : ~ 27107 years
Puzzle 160 @ 1 Yottakeys/s : < 1 sec
Puzzle 256 @ 1 Yottakeys/s : 10790283 years (real addresses)
Puzzle 120 @ 1 Yottakeys/s : < 1 sec
Puzzle 160 @ 1 Terakeys/s : ~ 27107 years
Puzzle 160 @ 1 Yottakeys/s : < 1 sec
Puzzle 256 @ 1 Yottakeys/s : 10790283 years (real addresses)
We can see here, how important a high keyrate is.
How much is 1 Yottakeys/s for (Pollard / Rho) ?
July 19, 2021, 06:47:35 PM
if scan all it use a time too much
Depent of your speed, i made some calculations based on the speed, the time is for scan all the range in that bit space:
Code:
Puzzle 120 @ 1 Terakeys/s : 21074771622667996 years
Puzzle 120 @ 1 Petakeys/s : 21074771622667 years
Puzzle 120 @ 1 Exakeys/s : 21074771622 years
Puzzle 120 @ 1 Zettakeys/s : 21074771 years
Puzzle 120 @ 1 Yottakeys/s : 21074 years
Puzzle 160 @ 1 Terakeys/s : 23171956451847141650870193314 years
Puzzle 160 @ 1 Petakeys/s : 23171956451847141650870193 years
Puzzle 160 @ 1 Exakeys/s : 23171956451847141650870 years
Puzzle 160 @ 1 Zettakeys/s : 23171956451847141650 years
Puzzle 160 @ 1 Yottakeys/s : 23171956451847141 years
Puzzle 256 @ 1 Terakeys/s : 1835871531540401373407708412745559168131740612197318060720 years
Puzzle 256 @ 1 Petakeys/s : 1835871531540401373407708412745559168131740612197318060 years
Puzzle 256 @ 1 Exakeys/s : 1835871531540401373407708412745559168131740612197318 years
Puzzle 256 @ 1 Zettakeys/s : 1835871531540401373407708412745559168131740612197 years
Puzzle 256 @ 1 Yottakeys/s : 1835871531540401373407708412745559168131740612 years
Puzzle 120 @ 1 Petakeys/s : 21074771622667 years
Puzzle 120 @ 1 Exakeys/s : 21074771622 years
Puzzle 120 @ 1 Zettakeys/s : 21074771 years
Puzzle 120 @ 1 Yottakeys/s : 21074 years
Puzzle 160 @ 1 Terakeys/s : 23171956451847141650870193314 years
Puzzle 160 @ 1 Petakeys/s : 23171956451847141650870193 years
Puzzle 160 @ 1 Exakeys/s : 23171956451847141650870 years
Puzzle 160 @ 1 Zettakeys/s : 23171956451847141650 years
Puzzle 160 @ 1 Yottakeys/s : 23171956451847141 years
Puzzle 256 @ 1 Terakeys/s : 1835871531540401373407708412745559168131740612197318060720 years
Puzzle 256 @ 1 Petakeys/s : 1835871531540401373407708412745559168131740612197318060 years
Puzzle 256 @ 1 Exakeys/s : 1835871531540401373407708412745559168131740612197318 years
Puzzle 256 @ 1 Zettakeys/s : 1835871531540401373407708412745559168131740612197 years
Puzzle 256 @ 1 Yottakeys/s : 1835871531540401373407708412745559168131740612 years
I know there is no puzzle 256, but that is the exact time for the real wallets.
With Pollard / Rho we calculate:
Code:
Puzzle 120 @ 1 Terakeys/s : ~ 10 days
Puzzle 120 @ 1 Yottakeys/s : < 1 sec
Puzzle 160 @ 1 Terakeys/s : ~ 27107 years
Puzzle 160 @ 1 Yottakeys/s : < 1 sec
Puzzle 256 @ 1 Yottakeys/s : 10790283 years (real addresses)
Puzzle 120 @ 1 Yottakeys/s : < 1 sec
Puzzle 160 @ 1 Terakeys/s : ~ 27107 years
Puzzle 160 @ 1 Yottakeys/s : < 1 sec
Puzzle 256 @ 1 Yottakeys/s : 10790283 years (real addresses)
We can see here, how important a high keyrate is.
June 20, 2021, 05:14:48 PM
larocfra: please download the application available there from https://www.thegrideon.com/bitcoin-password-recovery.html (whether portable or installer). After running it, you will see the available devices at the bottom of the log window, among which the CU value will be in square brackets next to the GPU. The CU value will be the best value for your card as -b in cuBitCrack, set -t to 512. Now check what effect and show it off. All you need to do now is try to find the best -p value
It's the first time I've seen a third-party (Thegrideon in this case) try to sell a wallet.dat cracker. I also haven't seen many people working on crackers for some time, so I'm a little surprised that their cracker has all these listed features: "mixed, dictionary and brute-force methods", "SSE, AVX optimization", AMD and NVIDIA card support out of the box which implies that the program has both a CUDA and OpenCL kernel.
Consequently, this makes me think they just bundled hashcat in their program with a little .NET wrapper for the GUI, no?
If that's true, it would mean the CU value might also be printed by hashcat proper. I've only paid attention to hashcat speeds, not CUs so I don't remember if they are logged too.
Truth. Hashcat will also give you the CU value, but I suggested it earlier, because getting this value would only involve downloading the program and running it :-) Much earlier I found this option and I already suggested this method to interested people, because it is the simplest, and the value of cu = value -b and better than this setting you won't find.
June 20, 2021, 02:05:51 PM
larocfra: please download the application available there from https://www.thegrideon.com/bitcoin-password-recovery.html (whether portable or installer). After running it, you will see the available devices at the bottom of the log window, among which the CU value will be in square brackets next to the GPU. The CU value will be the best value for your card as -b in cuBitCrack, set -t to 512. Now check what effect and show it off. All you need to do now is try to find the best -p value
It's the first time I've seen a third-party (Thegrideon in this case) try to sell a wallet.dat cracker. I also haven't seen many people working on crackers for some time, so I'm a little surprised that their cracker has all these listed features: "mixed, dictionary and brute-force methods", "SSE, AVX optimization", AMD and NVIDIA card support out of the box which implies that the program has both a CUDA and OpenCL kernel.
Consequently, this makes me think they just bundled hashcat in their program with a little .NET wrapper for the GUI, no?
If that's true, it would mean the CU value might also be printed by hashcat proper. I've only paid attention to hashcat speeds, not CUs so I don't remember if they are logged too.
June 20, 2021, 01:55:29 PM
Thank You for the link, I am under linux not windows. I have compiled the cuBitCrack for linux.
so try "cuBitCrack -l" oraz "cuBitCrack --list" for check CU. Maybe that command show you you ComputeUnits value
June 20, 2021, 01:52:15 PM
Thank You for the link, I am under linux not windows. I have compiled the cuBitCrack for linux.
June 20, 2021, 12:11:00 PM
Third column: bounty wallet address which is officially known from the Blockchain transaction available here: https://www.blockchain.com/btc/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15
Unless you mean the fourth: the upper rank limit. It's simple ... each subsequent rank is 2 ^ n-1 and the result of this equation is the value of the fourth column in DECIMAL
larocfra: please download the application available there from https://www.thegrideon.com/bitcoin-password-recovery.html (whether portable or installer). After running it, you will see the available devices at the bottom of the log window, among which the CU value will be in square brackets next to the GPU. The CU value will be the best value for your card as -b in cuBitCrack, set -t to 512. Now check what effect and show it off. All you need to do now is try to find the best -p value
Unless you mean the fourth: the upper rank limit. It's simple ... each subsequent rank is 2 ^ n-1 and the result of this equation is the value of the fourth column in DECIMAL
larocfra: please download the application available there from https://www.thegrideon.com/bitcoin-password-recovery.html (whether portable or installer). After running it, you will see the available devices at the bottom of the log window, among which the CU value will be in square brackets next to the GPU. The CU value will be the best value for your card as -b in cuBitCrack, set -t to 512. Now check what effect and show it off. All you need to do now is try to find the best -p value
June 19, 2021, 05:23:18 PM
Hi everybody,
I currently trying to solve the number 64 key, I have a Nvidia K80 water cooled and I am running cuBitCrack -b 88 -t 1024 -p 1024 -c -o foundkey.txt --keyspace 8000000000000000:FFFFFFFFFFFFFFFF
I have to run 2 separate session to be able to use both GPU on the card, I am getting 121.36 MKey/s on one target so about 240.00 Mkey/s total.
Do anybody have a setting to get more MKey/s out of the card ?
I currently trying to solve the number 64 key, I have a Nvidia K80 water cooled and I am running cuBitCrack -b 88 -t 1024 -p 1024 -c -o foundkey.txt --keyspace 8000000000000000:FFFFFFFFFFFFFFFF
I have to run 2 separate session to be able to use both GPU on the card, I am getting 121.36 MKey/s on one target so about 240.00 Mkey/s total.
Do anybody have a setting to get more MKey/s out of the card ?
June 18, 2021, 03:08:57 PM
June 18, 2021, 08:31:17 AM
For the last two months - a large part of the text in the main post was invisible because it led to the server that was changed, which, combined with the fact that almost the entire topic is mainly composed of pictures (which I did due to the limitation of the number of characters in the post) - resulted in that's as mentioned above. This problem has already been fixed, and I will revive the topic by the way :-)
May 05, 2021, 09:23:22 PM
120
https://blockchain.info/q/pubkeyaddr/17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT
same just change address and see pubkey, if address had outgoing transaction
https://blockchain.info/q/pubkeyaddr/17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT
same just change address and see pubkey, if address had outgoing transaction
I really wanted it to work with number 64 but it is only possible when there is an exit.
64
https://blockchain.info/q/pubkeyaddr/16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
pubkey is expose when that address make transaction pay out
address 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN not yet use for payout so pubkey not expose
address 17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT already payout to other address is available pubkey expose
other way you can brute-force pubkey but pubkey is long 34 alphanumeric characters no body do this because brute-force to private key directly is better if you do is double work for pubkey and still do with private key again it is waste of time
May 05, 2021, 09:17:45 PM
120
https://blockchain.info/q/pubkeyaddr/17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT
same just change address and see pubkey, if address had outgoing transaction
https://blockchain.info/q/pubkeyaddr/17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT
same just change address and see pubkey, if address had outgoing transaction
I really wanted it to work with number 64 but it is only possible when there is an exit.
64
https://blockchain.info/q/pubkeyaddr/16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
pubkey is expose when that address make transaction pay out
address 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN not yet use for payout so pubkey not expose
address 17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT already payout to other address is available pubkey expose
Jump to: