Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 156. (Read 215539 times)
Is there anyone here who owns or can rent h100 gpu? I would like to know the performance of tools such as Bitcrack on this GPU.
Just info.
Think in your own way and your own point of view about this WIF range
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q Yjgd9aFJuCJDo5F6Jm7 # 40
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q Yjgd9gCD9CBomewdcUD # 41
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q Yjgd9zzYEemjCVJ3vo9 # 42
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjgdB23bP5LsYN8Krv7 # 43
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjgdCpdGyxm7PWoNQdr # 44
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjgdDrgx63tbte4scLA # 45
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjgdLwb42sQhwTBJDnG # 46
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjgdcLTenJYVVVTRzxN # 47
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjgdtUGWxHzvDi28MfR # 48
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjgejcjwprJ4MAYLw8e # 49
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjgfXBMYdNVA4EjUMzg # 50
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q Yjgm9fa43QnU2CpULaK # 51
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjguYJTZsntce5oQQrh # 52
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q Yjh5SmqrUoK2mhwSYFV # 53
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjhHvuTMSDchRp5hktc # 54
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjidyYKE5NcJQZYvknA # 55
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q Yjjb65nDHeqyjiBaJXv # 56
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YjqtiAvYTJzYEmqup7b # 57
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q Yjv2kTamEYQT9BNC7o1 # 58
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YkHpsTBP19HvTFqiU6i # 59
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YkzijLsc5qE43yZ5eLV # 60
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YmLDHsih379uP9zbHSD # 61
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q YpCemuaUp7NigjvtJug # 62
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q Yv5Z9J7hv7VYYN3XL3Y # 63
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q Z6FxoaD5r1kYegmtbaT # 64
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q ZM21gaY8WN2CdwnTG57 # 65
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 66
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 67
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 68
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 69
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q t5RQNhFCn1r58in2E78 # 70
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 71
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 72
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 73
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 74
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3y HuxB7NfERRuDTNy2kbr # 75
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 76
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 77
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 78
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q # 79
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi APRB6KvN7FnKsw69PP7vW # 80
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi # 81
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi # 82
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi # 83
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi # 84
KwDiBf89QgGbjEhKnhXJuH7LrciVrZ kCnRjpBspr8M5K8YnUtDNa # 85
KwDiBf89QgGbjEhKnhXJuH7LrciVrZ # 86
KwDiBf89QgGbjEhKnhXJuH7LrciVrZ # 87
KwDiBf89QgGbjEhKnhXJuH7LrciVrZ # 88
KwDiBf89QgGbjEhKnhXJuH7LrciVrZ # 89
KwDiBf89QgGbjEhKnhXJuH7LrciVr bEiEhLWVU4Yn1RCfnX51KrT # 90
KwDiBf89QgGbjEhKnhXJuH7LrciVr # 91
KwDiBf89QgGbjEhKnhXJuH7LrciVr # 92
KwDiBf89QgGbjEhKnhXJuH7LrciVr # 93
KwDiBf89QgGbjEhKnhXJuH7LrciVr # 94
KwDiBf89QgGbjEhKnhXJuH7LrciV sLfMYB8ydZ3QXMqEra1sapfT # 95
KwDiBf89QgGbjEhKnhXJuH7LrciV # 96
KwDiBf89QgGbjEhKnhXJuH7LrciV # 97
KwDiBf89QgGbjEhKnhXJuH7LrciV # 98
KwDiBf89QgGbjEhKnhXJuH7LrciV # 99
KwDiBf89QgGbjEhKnhXJuH7Lrci WJvjTPYdp4sSLwstc63avmfRA # 100
KwDiBf89QgGbjEhKnhXJuH7Lrci # 101
KwDiBf89QgGbjEhKnhXJuH7Lrci # 102
KwDiBf89QgGbjEhKnhXJuH7Lrci # 103
KwDiBf89QgGbjEhKnhXJuH7Lrci # 104
KwDiBf89QgGbjEhKnhXJuH7Lrci m5eBMkFQwQtRbW6wxT1ajoNqE # 105
KwDiBf89QgGbjEhKnhXJuH7Lrci # 106
KwDiBf89QgGbjEhKnhXJuH7Lrci # 107
KwDiBf89QgGbjEhKnhXJuH7Lrci # 108
KwDiBf89QgGbjEhKnhXJuH7Lrci # 109
KwDiBf89QgGbjEhKnhXJuH7Lrc tLcZtumiizzSmSckgpxQu6ieu6 # 110
KwDiBf89QgGbjEhKnhXJuH7Lrc # 111
KwDiBf89QgGbjEhKnhXJuH7Lrc # 112
KwDiBf89QgGbjEhKnhXJuH7Lrc # 113
KwDiBf89QgGbjEhKnhXJuH7Lrc # 114
KwDiBf89QgGbjEhKnhXJuH7Lr hcVkatbczm7Y9ZaB56U1jLNU2Xh # 115
KwDiBf89QgGbjEhKnhXJuH7Lr # 116
KwDiBf89QgGbjEhKnhXJuH7Lr # 117
KwDiBf89QgGbjEhKnhXJuH7Lr # 118
KwDiBf89QgGbjEhKnhXJuH7Lr # 119
Think in your own way and your own point of view about this WIF range
Pollard Kangaroo approach is for the know private key range and for the best, within 125 bit range and of course since you have the Multibit wallet handy all you have to do is "Once you located the files, if you have access to an old multibit app on you computer you need to import the wallet and export the private keys to a new wallet. If you do not have a copy of Multibit, you can use OpenSSL together with your password to decrypt the files and recover the keys."
You need the password to export them. I still have the wallet open every single day since then.
I just keep looking at what value i've missed out on
I'm confused, do you have the wallet or you don't? How come the wallet is lost and you have it open?
Maybe I'm missing something here?
All info can be found on github here
https://github.com/gurnec/btcrecover/issues/212
I've also posted the hash if anyone wants to take a shot at it, i offer a 5BTC reward.
Code:
from sympy import mod_inverse
import secp256k1 as ice
pub=ice.pub2upub('0433709eb11e0d4439a729f21c2c443dedb727528229713f0065721ba8fa46f00e2a1c304a39a77775d3579d077b6ee5e4d26fd3ec36f52ad674a9b47fdd999c48')
N=0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141
k=mod_inverse(2,N)
neg1=ice.point_negation(ice.scalar_multiplication(1))
def ters(Qx,Scalar):
ScalarBin = str(bin(Scalar))[2:]
le=len(ScalarBin)
for i in range (1,le+1):
if ScalarBin[le-i] == "0":
Qx=ice.point_multiplication(k,Qx)
else:
Qx=ice.point_addition(Qx,neg1)
Qx=ice.point_multiplication(k,Qx)
return ice.point_to_cpub(Qx)
for x in range(1,65536):
print(ters(pub,x))
hi members!
I have a multibit classic wallet that currently holds 17BTC
Somewhere in 2014/2015 i lost my wallet password.
Many attempts have been tried to bruteforce the wallet password, without any success.
KeychainX, dave bitcoin, everyone already tried to guess or break my password.
Would you asume there is a possibility to use software to try and recover my wallet using the Pollard approach?
Can someone point me in the right direction on what sofware and settings i should be using?
I still have access to the Multibit wallet, only the password is missing.
I have my wallet address and it's public key.
Maybe this could come in handy to extract certain transaction data?
Thank you
What I would do in your case is find out what version of multibit you had when you created the wallet, the type of encryption that the software used at that time and inquire about a bug on that date, the language of your computer keyboard, maybe you used an unusual character that those who tried to help you with brute force did not enter, there may be a character in your password that is not included in their tools, a simple space key, or any other, as well as the type of format of plain text of the file, salt, etc...I have a multibit classic wallet that currently holds 17BTC
Somewhere in 2014/2015 i lost my wallet password.
Many attempts have been tried to bruteforce the wallet password, without any success.
KeychainX, dave bitcoin, everyone already tried to guess or break my password.
Would you asume there is a possibility to use software to try and recover my wallet using the Pollard approach?
Can someone point me in the right direction on what sofware and settings i should be using?
I still have access to the Multibit wallet, only the password is missing.
I have my wallet address and it's public key.
Maybe this could come in handy to extract certain transaction data?
Thank you
In short, I would make a code replicating the source environment to avoid errors in brute force.
I have experience working with multibit wallets. Maybe I can help.
The wallet itself is lost. Dave Bitcoin has been working on it since early 2014, bruteforce of the entire range up to 10 characters has been attempted.
At one point, KeychainX found a false positive using the words i gave him, but it was just that - a false positive.
My only remaining options at this point are to handle this like solving the puzzles, but with my own wallet
Pollard Kangaroo approach is for the know private key range and for the best, within 125 bit range and of course since you have the Multibit wallet handy all you have to do is "Once you located the files, if you have access to an old multibit app on you computer you need to import the wallet and export the private keys to a new wallet. If you do not have a copy of Multibit, you can use OpenSSL together with your password to decrypt the files and recover the keys."
You need the password to export them. I still have the wallet open every single day since then.
I just keep looking at what value i've missed out on
maybe it's an encryption problem, some software have had problems logging in when updates are applied, or special characters that are interpreted differently.
Have you tried hashcat yet?
Wish you find your coins, good luck.
I've spent close to 250k since 2014 on this, so, yes.
Bruteforcing is no option.
Dave succesfully recovered a wallet holding +- 1800BTC around the same time (lost all passwords the same day), so i know he's a capable guy.
If he tells me after almost ten years it's impossible using the bruteforce technique, then i trust him.
I guess i'll wait it out until our technology evolves.
I have heard and read about Dave's work, seems legit and secure to give him wallet hash, best way to crack a wallet's password without giving him access to the wallet if he can crack it.
But password recovery and elliptic curve operations are different, however a 256 bit key is not possible to solve currently.
Just a friendly advice, never spend money on recovery before calculating everything scientifically, always ask experts for precise calculations of success, time, odds, probability etc.😉
Pollard Kangaroo approach is for the know private key range and for the best, within 125 bit range and of course since you have the Multibit wallet handy all you have to do is "Once you located the files, if you have access to an old multibit app on you computer you need to import the wallet and export the private keys to a new wallet. If you do not have a copy of Multibit, you can use OpenSSL together with your password to decrypt the files and recover the keys."
You need the password to export them. I still have the wallet open every single day since then.
I just keep looking at what value i've missed out on
I'm confused, do you have the wallet or you don't? How come the wallet is lost and you have it open?
Maybe I'm missing something here?
Have you tried hashcat yet?
Wish you find your coins, good luck.
I've spent close to 250k since 2014 on this, so, yes.
Bruteforcing is no option.
Dave succesfully recovered a wallet holding +- 1800BTC around the same time (lost all passwords the same day), so i know he's a capable guy.
If he tells me after almost ten years it's impossible using the bruteforce technique, then i trust him.
I guess i'll wait it out until our technology evolves.
I guess he must be very conversant with the password utils more than the private keys utils that we are handy with. But we will definitely say you should never let your gourd down because you still have hopes and you could just have a dream and remember what your forgotten password was... but unlike the private key operation, you can wake up from a dream remembering all 64 hexadecimal character private key or 51/52 compressed or uncompressed format of your private key... except you wrote it down somewhere or backed it up somehow.
Best we leave this for Dave to handle and maybe someday when we have the private keys backed up with passwords for stronger security against theft when the EC curve has been defeated... maybe until then will we be able to ask for Dave's assistance but right now... 66 bits is slapping our faces mercilessly that we don't know a way to tackle it...
Have you tried hashcat yet?
Wish you find your coins, good luck.
I've spent close to 250k since 2014 on this, so, yes.
Bruteforcing is no option.
Dave succesfully recovered a wallet holding +- 1800BTC around the same time (lost all passwords the same day), so i know he's a capable guy.
If he tells me after almost ten years it's impossible using the bruteforce technique, then i trust him.
I guess i'll wait it out until our technology evolves.
Pollard Kangaroo approach is for the know private key range and for the best, within 125 bit range and of course since you have the Multibit wallet handy all you have to do is "Once you located the files, if you have access to an old multibit app on you computer you need to import the wallet and export the private keys to a new wallet. If you do not have a copy of Multibit, you can use OpenSSL together with your password to decrypt the files and recover the keys."
You need the password to export them. I still have the wallet open every single day since then.
I just keep looking at what value I've missed out on
The difference between your case and the puzzle is that we can't know the specific bit range just by looking at the public key and transactions from your pubkeys can't tell us what range the private key would be or else all of Satoshi wallets with exposed pubkeys would have been emptied by now. The best we would need to do is scan from first bit all the way to the end of the 256 bit range which of course would be like trying to scan for the wallets of Satoshi with the 50 bitcoins from the early mining... wouldn't pay off stilleven if you are able to scan for 1 wallet successfully, you'd need funds from 10 of those wallets to scan for just 1
Speaking of spamming the topic with unimportant content!
When you guys realize that in order to find a key based on address alone, first you'd need to break rmd160, then sha256 to get the public key and then find the private key based on the public key, since only public key and private key are directly related mathematically.
What you should do instead now that you are using your time, you should find any relation between similar addresses and their public/ private keys with their sha256 hashes, at least this way you are one step closer to solving 66 etc, because you won't have to face rmd160.
However, trying to do that will require more power and time than solving the puzzle #160.
So don't waste your time on something that difficult, try finding ways to go around the EC rules and break/ bend them either completely or partially.
For example, this is a method to partially break EC :
Divide a point by e.g, 5, then divide n by 5, and then add the result of p/5 to n/5, if your point is not divisible by 5 depending on the last digit of the private key, the division result differs.
Demonstration :
823 / 5 = 164.6
Now all you need is to extract 0.6 of n in secp256k1 and keep it for next operation, then after dividing 823 by 5, you just divide n by 5 and add the result of 823/5 to n/5 + 6/10 of n = 164
But what happens if we divide 822 / 5 = 164.4, just follow the previous steps this time extract 4/10 of n to add to your second result.
We just broke EC by simple math operations, though when your key is large and unknown, the fraction could be any percentage of n, but if you divide by 2 up to 9, since any key can only have 0 up to 9 on it's last digit, 1 out of 10 division + n/th + n/remainder will work.
I could never find these things out if I was still working on addresses and hashes.😉
You can use key subtracter by alberto, https://bitcointalksearch.org/topic/keysubtracter-test-development-requests-bug-reports-5360656
You could use a known public key and use -a - s with -r 0:f -n 30 to have 15 + and -15 of your known public key, however use -z and -x to have only x coordinates, then you can convert them all to decimal.
When you guys realize that in order to find a key based on address alone, first you'd need to break rmd160, then sha256 to get the public key and then find the private key based on the public key, since only public key and private key are directly related mathematically.
What you should do instead now that you are using your time, you should find any relation between similar addresses and their public/ private keys with their sha256 hashes, at least this way you are one step closer to solving 66 etc, because you won't have to face rmd160.
However, trying to do that will require more power and time than solving the puzzle #160.
So don't waste your time on something that difficult, try finding ways to go around the EC rules and break/ bend them either completely or partially.
For example, this is a method to partially break EC :
Divide a point by e.g, 5, then divide n by 5, and then add the result of p/5 to n/5, if your point is not divisible by 5 depending on the last digit of the private key, the division result differs.
Demonstration :
823 / 5 = 164.6
Now all you need is to extract 0.6 of n in secp256k1 and keep it for next operation, then after dividing 823 by 5, you just divide n by 5 and add the result of 823/5 to n/5 + 6/10 of n = 164
But what happens if we divide 822 / 5 = 164.4, just follow the previous steps this time extract 4/10 of n to add to your second result.
We just broke EC by simple math operations, though when your key is large and unknown, the fraction could be any percentage of n, but if you divide by 2 up to 9, since any key can only have 0 up to 9 on it's last digit, 1 out of 10 division + n/th + n/remainder will work.
I could never find these things out if I was still working on addresses and hashes.😉
Quote
what I need to know is, how to get the checkpoints for the puzzle 130 and how many checkpoints do i need their x coordinates in the checkpoints? Also will the code print the target public key's equivalent private key or will it save it to a file? Thanks as we all learning...
You can use key subtracter by alberto, https://bitcointalksearch.org/topic/keysubtracter-test-development-requests-bug-reports-5360656
You could use a known public key and use -a - s with -r 0:f -n 30 to have 15 + and -15 of your known public key, however use -z and -x to have only x coordinates, then you can convert them all to decimal.
Simply the best idea I've seen in days, truly ingenious. I will run some tests and check some calculations, thank you very much!!
hi members!
I have a multibit classic wallet that currently holds 17BTC
Somewhere in 2014/2015 i lost my wallet password.
Many attempts have been tried to bruteforce the wallet password, without any success.
KeychainX, dave bitcoin, everyone already tried to guess or break my password.
Would you asume there is a possibility to use software to try and recover my wallet using the Pollard approach?
Can someone point me in the right direction on what sofware and settings i should be using?
I still have access to the Multibit wallet, only the password is missing.
I have my wallet address and it's public key.
Maybe this could come in handy to extract certain transaction data?
Thank you
In here we are aliens with passwords, we only work with public keys, you could post it here so we could check it out ( not making any difference, because we are stuck with keys smaller than 160 bit ).I have a multibit classic wallet that currently holds 17BTC
Somewhere in 2014/2015 i lost my wallet password.
Many attempts have been tried to bruteforce the wallet password, without any success.
KeychainX, dave bitcoin, everyone already tried to guess or break my password.
Would you asume there is a possibility to use software to try and recover my wallet using the Pollard approach?
Can someone point me in the right direction on what sofware and settings i should be using?
I still have access to the Multibit wallet, only the password is missing.
I have my wallet address and it's public key.
Maybe this could come in handy to extract certain transaction data?
Thank you
Have you tried hashcat yet?
Regarding pollard's method aka kangaroo, you could divide your public key by 2 but before that either add 1G or subtract 1G then you'll have 2 public keys, original and it's +1, you could divide them both by 2 four times in a row, then add 1G to each result and divide all of them by 2, at the end you will have millions of keys, which would be impossible to do the division and addition manually you'd need a program to do that which doesn't exist, but if you could do that then for example you could divide n of secpk1 by 2 as many times as you divided your public key and input those millions/ billions of offsets into kangaroo and then use n/2, n/4, n/8 etc as your start range, you could subtract an estimated number from your n/2 and use it as start and add that estimated number to n/2 and use it as end range, I'd imagine you'll have to try at least 200 start/end ranges one by one and spend at least 6 hours for each search.
Wish you find your coins, good luck.
I have experience working with multibit wallets. Maybe I can help.
The wallet itself is lost. Dave Bitcoin has been working on it since early 2014, bruteforce of the entire range up to 10 characters has been attempted.
At one point, KeychainX found a false positive using the words i gave him, but it was just that - a false positive.
My only remaining options at this point are to handle this like solving the puzzles, but with my own wallet
Pollard Kangaroo approach is for the know private key range and for the best, within 125 bit range and of course since you have the Multibit wallet handy all you have to do is "Once you located the files, if you have access to an old multibit app on you computer you need to import the wallet and export the private keys to a new wallet. If you do not have a copy of Multibit, you can use OpenSSL together with your password to decrypt the files and recover the keys."
You need the password to export them. I still have the wallet open every single day since then.
I just keep looking at what value i've missed out on
hi members!
I have a multibit classic wallet that currently holds 17BTC
Somewhere in 2014/2015 i lost my wallet password.
Many attempts have been tried to bruteforce the wallet password, without any success.
KeychainX, dave bitcoin, everyone already tried to guess or break my password.
Would you asume there is a possibility to use software to try and recover my wallet using the Pollard approach?
Can someone point me in the right direction on what sofware and settings i should be using?
I still have access to the Multibit wallet, only the password is missing.
I have my wallet address and it's public key.
Maybe this could come in handy to extract certain transaction data?
Thank you
I have a multibit classic wallet that currently holds 17BTC
Somewhere in 2014/2015 i lost my wallet password.
Many attempts have been tried to bruteforce the wallet password, without any success.
KeychainX, dave bitcoin, everyone already tried to guess or break my password.
Would you asume there is a possibility to use software to try and recover my wallet using the Pollard approach?
Can someone point me in the right direction on what sofware and settings i should be using?
I still have access to the Multibit wallet, only the password is missing.
I have my wallet address and it's public key.
Maybe this could come in handy to extract certain transaction data?
Thank you
Pollard Kangaroo approach is for the know private key range and for the best, within 125 bit range and of course since you have the Multibit wallet handy all you have to do is "Once you located the files, if you have access to an old multibit app on you computer you need to import the wallet and export the private keys to a new wallet. If you do not have a copy of Multibit, you can use OpenSSL together with your password to decrypt the files and recover the keys."
hi members!
I have a multibit classic wallet that currently holds 17BTC
Somewhere in 2014/2015 i lost my wallet password.
Many attempts have been tried to bruteforce the wallet password, without any success.
KeychainX, dave bitcoin, everyone already tried to guess or break my password.
Would you asume there is a possibility to use software to try and recover my wallet using the Pollard approach?
Can someone point me in the right direction on what sofware and settings i should be using?
I still have access to the Multibit wallet, only the password is missing.
I have my wallet address and it's public key.
Maybe this could come in handy to extract certain transaction data?
Thank you
I have a multibit classic wallet that currently holds 17BTC
Somewhere in 2014/2015 i lost my wallet password.
Many attempts have been tried to bruteforce the wallet password, without any success.
KeychainX, dave bitcoin, everyone already tried to guess or break my password.
Would you asume there is a possibility to use software to try and recover my wallet using the Pollard approach?
Can someone point me in the right direction on what sofware and settings i should be using?
I still have access to the Multibit wallet, only the password is missing.
I have my wallet address and it's public key.
Maybe this could come in handy to extract certain transaction data?
Thank you
I have experience working with multibit wallets. Maybe I can help.
hi members!
I have a multibit classic wallet that currently holds 17BTC
Somewhere in 2014/2015 i lost my wallet password.
Many attempts have been tried to bruteforce the wallet password, without any success.
KeychainX, dave bitcoin, everyone already tried to guess or break my password.
Would you asume there is a possibility to use software to try and recover my wallet using the Pollard approach?
Can someone point me in the right direction on what sofware and settings i should be using?
I still have access to the Multibit wallet, only the password is missing.
I have my wallet address and it's public key.
Maybe this could come in handy to extract certain transaction data?
Thank you
I have a multibit classic wallet that currently holds 17BTC
Somewhere in 2014/2015 i lost my wallet password.
Many attempts have been tried to bruteforce the wallet password, without any success.
KeychainX, dave bitcoin, everyone already tried to guess or break my password.
Would you asume there is a possibility to use software to try and recover my wallet using the Pollard approach?
Can someone point me in the right direction on what sofware and settings i should be using?
I still have access to the Multibit wallet, only the password is missing.
I have my wallet address and it's public key.
Maybe this could come in handy to extract certain transaction data?
Thank you
It will certainly be touching the checkpoint BUT WHEN NO BODY CAN TELL FOR CERTAIN!
I saw someone commented on my script saying how script generated checkpoints and stuff,, please study pub key generation before using this script
Certainly!!!
I did comment but never said script generated checkpoint. I said I generated the checkpoint randomly myself between the range of 130 bits so i saved it in the checkpoints.txt file. but I was eventually advised how I could get the key subtractor from albertobsd but I couldn't compile the code so I downloaded the windows version from WanderingPhilosopher and it worked like magic.
I tried it with generating 1000 keys for a test and I thought of how I could derive the decimal representations of the public keys of so many numbers most especially if we are working with billions of numbers. now I wrote this code that takes arguments for -f for the file you got from your key extractor and -o for the output you want to save the decimal representation of the public keys for the x coordinates as advised, which in my case I always used the checkpoints.txt as my -o as it makes it more easy because it's all in the same directory
code is below
Code:
import argparse
def extract_x_coordinate(compressed_key):
# Remove the prefix (02 or 03) and extract x-coordinate
x_coord_hex = compressed_key[2:]
x_coord_decimal = int(x_coord_hex, 16)
return x_coord_decimal
def main():
parser = argparse.ArgumentParser(description='Extract x-coordinates of compressed public keys and save as decimals')
parser.add_argument('-f', '--input-file', required=True, help='Path to the input file containing compressed public keys')
parser.add_argument('-o', '--output-file', required=True, help='Path to the output file to save decimal x-coordinates')
args = parser.parse_args()
try:
with open(args.input_file, 'r') as input_file:
lines = input_file.readlines()
decimal_coordinates = []
for line in lines:
compressed_key = line.split()[0] # Extract only the public key part
decimal_x_coord = extract_x_coordinate(compressed_key)
decimal_coordinates.append(str(decimal_x_coord))
with open(args.output_file, 'w') as output_file:
output_file.write('\n'.join(decimal_coordinates))
print(f"Decimal x-coordinates saved to {args.output_file}")
except Exception as e:
print(f"An error occurred: {e}")
if __name__ == "__main__":
main()
def extract_x_coordinate(compressed_key):
# Remove the prefix (02 or 03) and extract x-coordinate
x_coord_hex = compressed_key[2:]
x_coord_decimal = int(x_coord_hex, 16)
return x_coord_decimal
def main():
parser = argparse.ArgumentParser(description='Extract x-coordinates of compressed public keys and save as decimals')
parser.add_argument('-f', '--input-file', required=True, help='Path to the input file containing compressed public keys')
parser.add_argument('-o', '--output-file', required=True, help='Path to the output file to save decimal x-coordinates')
args = parser.parse_args()
try:
with open(args.input_file, 'r') as input_file:
lines = input_file.readlines()
decimal_coordinates = []
for line in lines:
compressed_key = line.split()[0] # Extract only the public key part
decimal_x_coord = extract_x_coordinate(compressed_key)
decimal_coordinates.append(str(decimal_x_coord))
with open(args.output_file, 'w') as output_file:
output_file.write('\n'.join(decimal_coordinates))
print(f"Decimal x-coordinates saved to {args.output_file}")
except Exception as e:
print(f"An error occurred: {e}")
if __name__ == "__main__":
main()
I am still testing your code out @unpluggedcoin
I see something different and it's something good
let me fully understand how the code works
thanks
let me fully understand how the code works
thanks
Just for clarification purposes and better understanding of the works of the code, let me provide the tests I just carried out and the result
Code:
I had the private key: 0000000000000000000000000000000000000000000000000000000000000fff
Public key hex: 029c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af88
uncompressed pubkey: 049c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af888637496c8eddff12f9dd414636565e0fefddf5cd52d484550ec9fb2d8dd0914a
Decimal X coordinate: 70620163506976111171066173961856210080659139929929089024144375783710733217672
Decimal Y coordinate: 60707605052923732375620988065125934494722916954686011896369305439279242056010
bot in the xy.txt
my checkpoints.txt x coordinates in decimal is below:
48534083396712420011161436556403147439265879225492303623124868600374192125513
113877090530951511693952929019428549049897440102965425133344510169891671188214
54703663425791593299627451355291558428018142888690298046450063544492403022202
35695519954865045812664034136944711038213290511429728516075604875860252135936
4377758882192617438073703099513664472199842035925839546423515265326631629185
81438813890211960163838804516478989860247194598335673558809549067405651523639
38691014678829756200842582202414712487786539326456194623982039889948932988919
34209530101981187896671676793789826085284188147541725074418631248878730074163
63759668502957471302068547000633741991437373340461175426601087253499295081839
67189090958477772831500862816583578870907213977274273861176457448640950298883
pubkey extracted below:
036b4d515687d6b0793df366326fe6977cb93e6569667971966c16c495be4e3649 # + 354
03fbc4262e32abf91382bbeeb138d589e2eccb0b0490becbc4e444803228a922f6 # + 357
0278f12d2070d8bcb400267cbbbff637f165ffb09895f5734e3551bcbc09a5597a # + 35a
024eeaf2c5af8ab327dae931895cbba89cff2ce7566da1304bb0ced9e704559200 # + 35d
0309adb945b876313bac9c290d47c1e6aa1f3f3c9ae8c6777061512c2bbd703181 # + 360
02b40cbc35dcd4eecf13580ac710f474788d8ee3eff1b60956dd79be8a0c5eb837 # + a65
02558a56983b03c6c6717db862e59dd075b39f9ba2ca01b0ac95a69cec1f3a5ff7 # + a68
034ba1e86aa9f8b3570ba0903140ad1bb0602a0c567cc397dbff69fed66619d833 # + a6b
028cf6b189c50519566a94e1f5ab5e9530d459a93504cb13eb349fac3eade8a56f # + a6e
02948bad866c3e2c2602d4616352be20ae30a652e34a29936104766eb798b3e903 # + bb8
029c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af88 # target
how do I calculate my target private key from the result I got below
X coordinate decimal: 70620163506976111171066173961856210080659139929929089024144375783710733217672
Y coordinate decimal: 60707605052923732375620988065125934494722916954686011896369305439279242056010 0
uncompressed pubkey from result: 049c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af888637496c8eddff12f9dd414636565e0fefddf5cd52d484550ec9fb2d8dd0914a
compressed pubkey from result: 029c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af88
that was because the target's x coordinate pubkey was also in the checkpoints.txtPublic key hex: 029c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af88
uncompressed pubkey: 049c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af888637496c8eddff12f9dd414636565e0fefddf5cd52d484550ec9fb2d8dd0914a
Decimal X coordinate: 70620163506976111171066173961856210080659139929929089024144375783710733217672
Decimal Y coordinate: 60707605052923732375620988065125934494722916954686011896369305439279242056010
bot in the xy.txt
my checkpoints.txt x coordinates in decimal is below:
48534083396712420011161436556403147439265879225492303623124868600374192125513
113877090530951511693952929019428549049897440102965425133344510169891671188214
54703663425791593299627451355291558428018142888690298046450063544492403022202
35695519954865045812664034136944711038213290511429728516075604875860252135936
4377758882192617438073703099513664472199842035925839546423515265326631629185
81438813890211960163838804516478989860247194598335673558809549067405651523639
38691014678829756200842582202414712487786539326456194623982039889948932988919
34209530101981187896671676793789826085284188147541725074418631248878730074163
63759668502957471302068547000633741991437373340461175426601087253499295081839
67189090958477772831500862816583578870907213977274273861176457448640950298883
pubkey extracted below:
036b4d515687d6b0793df366326fe6977cb93e6569667971966c16c495be4e3649 # + 354
03fbc4262e32abf91382bbeeb138d589e2eccb0b0490becbc4e444803228a922f6 # + 357
0278f12d2070d8bcb400267cbbbff637f165ffb09895f5734e3551bcbc09a5597a # + 35a
024eeaf2c5af8ab327dae931895cbba89cff2ce7566da1304bb0ced9e704559200 # + 35d
0309adb945b876313bac9c290d47c1e6aa1f3f3c9ae8c6777061512c2bbd703181 # + 360
02b40cbc35dcd4eecf13580ac710f474788d8ee3eff1b60956dd79be8a0c5eb837 # + a65
02558a56983b03c6c6717db862e59dd075b39f9ba2ca01b0ac95a69cec1f3a5ff7 # + a68
034ba1e86aa9f8b3570ba0903140ad1bb0602a0c567cc397dbff69fed66619d833 # + a6b
028cf6b189c50519566a94e1f5ab5e9530d459a93504cb13eb349fac3eade8a56f # + a6e
02948bad866c3e2c2602d4616352be20ae30a652e34a29936104766eb798b3e903 # + bb8
029c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af88 # target
how do I calculate my target private key from the result I got below
X coordinate decimal: 70620163506976111171066173961856210080659139929929089024144375783710733217672
Y coordinate decimal: 60707605052923732375620988065125934494722916954686011896369305439279242056010 0
uncompressed pubkey from result: 049c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af888637496c8eddff12f9dd414636565e0fefddf5cd52d484550ec9fb2d8dd0914a
compressed pubkey from result: 029c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af88
but I have excluded the target's pubkey from the checkpoints now it's still searching. will let you know what the result is
Code:
[quote author=bestie1549 link=topic=1306983.msg62709951#msg62709951 date=1692290267]
[quote author=bestie1549 link=topic=1306983.msg62709740#msg62709740 date=1692287706]
[quote author=unpluggedcoin link=topic=1306983.msg62709645#msg62709645 date=1692286633]
how do I calculate my target private key from the result I got below
X coordinate decimal: 70620163506976111171066173961856210080659139929929089024144375783710733217672
Y coordinate decimal: 60707605052923732375620988065125934494722916954686011896369305439279242056010 0
uncompressed pubkey from result: 049c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af888637496c8eddff12f9dd414636565e0fefddf5cd52d484550ec9fb2d8dd0914a
compressed pubkey from result: 029c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af88
that was because the target's x coordinate pubkey was also in the checkpoints.txt[quote author=bestie1549 link=topic=1306983.msg62709740#msg62709740 date=1692287706]
[quote author=unpluggedcoin link=topic=1306983.msg62709645#msg62709645 date=1692286633]
how do I calculate my target private key from the result I got below
X coordinate decimal: 70620163506976111171066173961856210080659139929929089024144375783710733217672
Y coordinate decimal: 60707605052923732375620988065125934494722916954686011896369305439279242056010 0
uncompressed pubkey from result: 049c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af888637496c8eddff12f9dd414636565e0fefddf5cd52d484550ec9fb2d8dd0914a
compressed pubkey from result: 029c2198986d202467c055c7347355750506105b3e2874dbf28f7f0c3966e1af88
but I have excluded the target's pubkey from the checkpoints now it's still searching. will let you know what the result is
[/quote]
I am about to hit it for puzzle 130... I need 5TB hard disk space, I just need to calculate the result from my search and I will fully understand how it works. if you can please explain 1 last time with this result.
I would really appreciate it. I am still very new with the key extraction and I am definitely learning very fast
thanks
Code:
[quote author=bestie1549 link=topic=1306983.msg62709951#msg62709951 date=1692290267]
[quote author=bestie1549 link=topic=1306983.msg62709740#msg62709740 date=1692287706]
[quote author=unpluggedcoin link=topic=1306983.msg62709645#msg62709645 date=1692286633]
how do I calculate my target private key from the result I got below
X coordinate decimal: 70620163506976111171066173961856210080659139929929089024144375783710733217672
Y coordinate decimal: 60707605052923732375620988065125934494722916954686011896369305439279242056010 0
I would really appreciate it. I am still very new with the key extraction and I am definitely learning very fast
thanks
[/quote]
Bro i am very confused with the results.txt
All i get is the same result in the xy.txt then 0 at the end of it in the results.txt
what do I do now? I am testing the code with much smaller bits because I need to know how it really works
please kindly explain to me like a dummy... sometimes it sticks faster that way
[quote author=bestie1549 link=topic=1306983.msg62709740#msg62709740 date=1692287706]
[quote author=unpluggedcoin link=topic=1306983.msg62709645#msg62709645 date=1692286633]
how do I calculate my target private key from the result I got below
X coordinate decimal: 70620163506976111171066173961856210080659139929929089024144375783710733217672
Y coordinate decimal: 60707605052923732375620988065125934494722916954686011896369305439279242056010 0
I would really appreciate it. I am still very new with the key extraction and I am definitely learning very fast
thanks
[/quote]
Bro i am very confused with the results.txt
All i get is the same result in the xy.txt then 0 at the end of it in the results.txt
what do I do now? I am testing the code with much smaller bits because I need to know how it really works
please kindly explain to me like a dummy... sometimes it sticks faster that way
Code:
[quote author=bestie1549 link=topic=1306983.msg62709951#msg62709951 date=1692290267]
[quote author=bestie1549 link=topic=1306983.msg62709740#msg62709740 date=1692287706]
[quote author=unpluggedcoin link=topic=1306983.msg62709645#msg62709645 date=1692286633]
how do I calculate my target private key from the result I got below
X coordinate decimal: 70620163506976111171066173961856210080659139929929089024144375783710733217672
Y coordinate decimal: 60707605052923732375620988065125934494722916954686011896369305439279242056010 0
I would really appreciate it. I am still very new with the key extraction and I am definitely learning very fast
thanks
[/quote]
Bro i am very confused with the results.txt
All i get is the same result in the xy.txt then 0 at the end of it in the results.txt
what do I do now? I am testing the code with much smaller bits because I need to know how it really works
please kindly explain to me like a dummy... sometimes it sticks faster that way
[quote author=bestie1549 link=topic=1306983.msg62709740#msg62709740 date=1692287706]
[quote author=unpluggedcoin link=topic=1306983.msg62709645#msg62709645 date=1692286633]
how do I calculate my target private key from the result I got below
X coordinate decimal: 70620163506976111171066173961856210080659139929929089024144375783710733217672
Y coordinate decimal: 60707605052923732375620988065125934494722916954686011896369305439279242056010 0
I would really appreciate it. I am still very new with the key extraction and I am definitely learning very fast
thanks
[/quote]
Bro i am very confused with the results.txt
All i get is the same result in the xy.txt then 0 at the end of it in the results.txt
what do I do now? I am testing the code with much smaller bits because I need to know how it really works
please kindly explain to me like a dummy... sometimes it sticks faster that way
With 20 TB RAM and 5 TB SSD we can break 130 tonight if only I know how to calculate the found result from the extracted pubkeys from this code from @unpluggedcoin
important basic information.:
You can not only subtract points or divide them, there is also addition and multiplication, dont get complicated with floats or negative numbers by subtracting or dividing too much from a pubkey.
if you are looking for the
pk=1000
use as cap 1500
Now explore with addition and multiplication.
if you find 1500, subtract your addition or multiplication and you will get pk.
You can not only subtract points or divide them, there is also addition and multiplication, dont get complicated with floats or negative numbers by subtracting or dividing too much from a pubkey.
if you are looking for the
pk=1000
use as cap 1500
Now explore with addition and multiplication.
if you find 1500, subtract your addition or multiplication and you will get pk.
Jump to: