So any update on the progress of finding this key?
First offset = 03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710
Half of above =
0291001b0dc6e5a2628cb4698eb00a6fb7dbd276dc2b214795f2fe52e61243aa9b
Half of 130?
0337374e00a32eaf009e9946035c0e69085627b60a844637d2b958dd83bcfa4383
The following is the subtracted key from #130
Second offset =
03d99bb89e8db75d20b882f13f8086fb39221858fa211de0346c926a93ae259b3a
Half of above?
03a3dc00bf5f7e7eec691569c7f67a15d3cdbb3a9994c9a5ec1430cffdb622cf9f
Now subtract half of first offset from half of #130 to get half of second offset.
Second offset is known, we need to work on first offset's half, use -1 divide by 2 script to reduce 18 bits from it, you'll have millions of new offsets and one of them is the target, now divide the #130 range by 2, subtract 18 bits from it and use the new range as your search range, input those millions offset keys and search the range.
Don't just try blind searching.😉
Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 149. (Read 215539 times)
I have no idea why so many are so obsessed about this adding and subtracting public key thingy. Maybe I know nothing much about it and makes me think that way. This adding/subtracting method in my opinion are totally different from Pollard Kangaroo idea or BSGS. From my understanding, by adding/subtracting public key, you can generate a bunch of valid public key, nothing wrong about it. But if 1 private key matching only 1 public key(of course it does), then where is the difference between adding/subtracting and private key bruteforcing? IMHO, it doesn't eliminate any possible private key combination at all. Please correct me if I am wrong.
because if you look for pk=1361129467683753853853498429727072845823
subtracting...
Code:
import secp256k1 as ice
target_public_key = "03e067911ebf6bacf87a8088ab9344c95843aed80b070eed09f9d947c98dfc0249"
target = ice.pub2upub(target_public_key)
num = 136114 # number of times.
sustract= 10000000000000000000000000000000000 #amount to subtract each time.
sustract_pub= ice.scalar_multiplication(sustract)
res= ice.point_loop_subtraction(num, target, sustract_pub)
for t in range (num+1):
h= (res[t*65:t*65+65]).hex()
hc= ice.to_cpub(h)
data = open("data-base.txt","a")
data.write(str(hc)+"\n")
data.close()
one of the pub in the result will be:target_public_key = "03e067911ebf6bacf87a8088ab9344c95843aed80b070eed09f9d947c98dfc0249"
target = ice.pub2upub(target_public_key)
num = 136114 # number of times.
sustract= 10000000000000000000000000000000000 #amount to subtract each time.
sustract_pub= ice.scalar_multiplication(sustract)
res= ice.point_loop_subtraction(num, target, sustract_pub)
for t in range (num+1):
h= (res[t*65:t*65+65]).hex()
hc= ice.to_cpub(h)
data = open("data-base.txt","a")
data.write(str(hc)+"\n")
data.close()
pk=9467683753853853498429727072845823
and looking for this 1361129467683753853853498429727072845823
is not the same as this 9467683753853853498429727072845823
@digaran indeed,, im about to breake puzzle 130 
----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong of course we split 13 btc
if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong
of course we split 13 btc if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
89-90 bits 20000000000000000000000:3ffffffffffffffffffffff
ok, I'm through, range scan done. Nothing found. Whats next?
where is the proof of the work §.?
@digaran indeed,, im about to breake puzzle 130
----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong of course we split 13 btc
if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong
of course we split 13 btc if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
89-90 bits 20000000000000000000000:3ffffffffffffffffffffff
ok, I'm through, range scan done. Nothing found. Whats next?
@digaran indeed,, im about to breake puzzle 130
----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong of course we split 13 btc
if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong
of course we split 13 btc if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
89-90 bits 20000000000000000000000:3ffffffffffffffffffffff
Here is the solution for partnering with muscles ( those with hardware to scan ranges ) , before scanning, the one asking for the scan should give all his information to an escrow and then the one doing the scan should provide the key he has found to the escrow so that the escrow does the final key extraction and divide the prize according to contract.
Person who asks for the scan provides the key which was subtracted from puzzle key and also the offset which the muscle is going to search for, escrow can verify the authenticity of the keys by doing the subtraction himself. 😉
Person who asks for the scan provides the key which was subtracted from puzzle key and also the offset which the muscle is going to search for, escrow can verify the authenticity of the keys by doing the subtraction himself. 😉
@digaran indeed,, im about to breake puzzle 130
----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong of course we split 13 btc
if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
So you want others to search for you, if the key was found you split the prize that easy? Son, what happens if they say they have found the key and you go rent some GPUs to get it yourself and keep the prize? You see why nobody would search that range for you, unless they are willingly trying to help you.----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong
of course we split 13 btc if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
Also there is no explanation about why you think that key is in that specific range. Should we be waiting for 587 other such ranges from you asking people to scan them for you? Lol.
Here is my 50satoshis, before attempting to search for a key, make sure it's in range.
you have concluded this ? and you judge me ?
no im not sure but at least im trying to solve it instead of doing nothing like you; you just reply like you know everything and you dont do nothing;; im helping here if i find the 130 i will leave tips for everyone even you
so please dont judge like thisps/ im the first one here in this thread who shared the gpu rent website; if im searching and want for my self i didint post the link;; i posted then 120 andd 125 cracked;; i have no probleme and im happy who will crack this puzzle;
@digaran indeed,, im about to breake puzzle 130
----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong of course we split 13 btc
if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
So you want others to search for you, if the key was found you split the prize that easy? Son, what happens if they say they have found the key and you go rent some GPUs to get it yourself and keep the prize? You see why nobody would search that range for you, unless they are willingly trying to help you.----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong
of course we split 13 btc if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
Also there is no explanation about why you think that key is in that specific range. Should we be waiting for 587 other such ranges from you asking people to scan them for you? Lol.
Here is my 50satoshis, before attempting to search for a key, make sure it's in range.
@digaran indeed,, im about to breake puzzle 130
----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong of course we split 13 btc
if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
----------------------------------------------------------------------------------------------------
Need someone to scan 89bit to 90
03982a5a42895a5cfe4b9b98e49f9389ebf9b3bf91c2289f1c5db3d944f46ec710 # +
range
10005df8cf4d0f152b26859:49fd5df8cf4d0f152b26859
its easy range anyone have gpu can scan this in 15 min, we try this why not maybe im not wrong
of course we split 13 btc if im correct and we found that pk of this adress,, yes @digaran you can call me master of crypto
Maybe I know too little information about it. I think I have some idea now, not sure if I am correct about it. By subtracting known 130 public key to lower bits to find the lower bits private key, once gotten that private key you do an inverse of lower bit private key back to 130 bits. Am I right?
Yes that is correct if you have some case like this:
Code:
P130 - PA = X
P130 - PB = Y
P130 - PC = Z
...
P130 - PM = N
P130 - PB = Y
P130 - PC = Z
...
P130 - PM = N
if you found the privatekey of any X, Y, Z or N you only need to apply the inverse process to get the Private key of P130, you only need to be aware of what are the values of PA,PB PC and PM
the same appy for other operations like addition, multiplication and division
Regards!
Thanks. Maybe will try it later. More focusing on 66 now. If my idea and approach works and able to solve 66, then 67 and 68 should be also solvable in short period of time.
Maybe I know too little information about it. I think I have some idea now, not sure if I am correct about it. By subtracting known 130 public key to lower bits to find the lower bits private key, once gotten that private key you do an inverse of lower bit private key back to 130 bits. Am I right?
Yes that is correct if you have some case like this:
Code:
P130 - PA = X
P130 - PB = Y
P130 - PC = Z
...
P130 - PM = N
P130 - PB = Y
P130 - PC = Z
...
P130 - PM = N
if you found the privatekey of any X, Y, Z or N you only need to apply the inverse process to get the Private key of P130, you only need to be aware of what are the values of PA,PB PC and PM
the same appy for other operations like addition, multiplication and division
Regards!
I have no idea why so many are so obsessed about this adding and subtracting public key thingy. Maybe I know nothing much about it and makes me think that way. This adding/subtracting method in my opinion are totally different from Pollard Kangaroo idea or BSGS. From my understanding, by adding/subtracting public key, you can generate a bunch of valid public key, nothing wrong about it. But if 1 private key matching only 1 public key(of course it does), then where is the difference between adding/subtracting and private key bruteforcing? IMHO, it doesn't eliminate any possible private key combination at all. Please correct me if I am wrong.
try this
https://github.com/WanderingPhilosopher/Windows-KeySubtractor
and you will understand
with substraction, we can minimise the search range from 130bit to lower range, you could fild a private key of generated substracted public key in lower range exemple 100bit or even lower so that will be easy to crack 130 bit..
Actually I saw your previous post quite some time ago and did try on the python script on that closed thread many months ago. After generating millions of public key, I found out it doesn't help much after trying an hour or so, immediately I gave up. LoL. Maybe I know too little information about it. I think I have some idea now, not sure if I am correct about it. By subtracting known 130 public key to lower bits to find the lower bits private key, once gotten that private key you do an inverse of lower bit private key back to 130 bits. Am I right?
Hello everyone What happens when dividing a scalar from a point (vector/scalar) on the secp256k1 calculator from Mr.maxwell. How can I find out what result it gives when using known points for an example, can you show an example?!.I still don't understand how division works here, I can't find the right result in any way.
Note the last digit of your private key in decimal, for example if you are dividing a key ending with 8 by 3, you need to separately divide 8 by 3 and subtract the result from your first result which is your key ending with 8 divided by 3, then you will have the correct result.
Also note that when you are subtracting, the greater key must be on the left slot, otherwise you'll get -n result starting with a lot of fs. When you see that though you could either change the keys slot or just subtract the result from n to have your result.
Here is a trick, if you are dividing a key by 2 digits number, then the previous method won't work, e.g, dividing a key ending with 8 by 25 won't work if you divide "8" by 25 and subtract both results, instead you'd need to know the last 2 digits of your key, example : if your key ends in 58, then you'd need to divide "58" by 25 separately then do the previous steps. ( might not work with all numbers ).
Here is another trick, if you are dividing by 25, try dividing n by 7 and compare both results.
Most of what I said won't make sense now, but in the future you'd come back to check this post again.😉
Ps, if you want advanced tricks, ask the master of cryptography aka kalos. I hear he is about to break rmd160 hash function by finding a collision.
I have no idea why so many are so obsessed about this adding and subtracting public key thingy. Maybe I know nothing much about it and makes me think that way. This adding/subtracting method in my opinion are totally different from Pollard Kangaroo idea or BSGS. From my understanding, by adding/subtracting public key, you can generate a bunch of valid public key, nothing wrong about it. But if 1 private key matching only 1 public key(of course it does), then where is the difference between adding/subtracting and private key bruteforcing? IMHO, it doesn't eliminate any possible private key combination at all. Please correct me if I am wrong.
try this
https://github.com/WanderingPhilosopher/Windows-KeySubtractor
and you will understand
with substraction, we can minimise the search range from 130bit to lower range, you could fild a private key of generated substracted public key in lower range exemple 100bit or even lower so that will be easy to crack 130 bit..
I have no idea why so many are so obsessed about this adding and subtracting public key thingy. Maybe I know nothing much about it and makes me think that way. This adding/subtracting method in my opinion are totally different from Pollard Kangaroo idea or BSGS. From my understanding, by adding/subtracting public key, you can generate a bunch of valid public key, nothing wrong about it. But if 1 private key matching only 1 public key(of course it does), then where is the difference between adding/subtracting and private key bruteforcing? IMHO, it doesn't eliminate any possible private key combination at all. Please correct me if I am wrong.
Code:
import secp256k1 as ice
target_public_key = "023d62d9d64a7164a2ae6f0561f7e8317e69b4a1ee61048fe768a1316b39b1d3a7"
target = ice.pub2upub(target_public_key)
num = 100 # number of times.
sustract= 1 #amount to subtract each time.
sustract_pub= ice.scalar_multiplication(sustract)
res= ice.point_loop_subtraction(num, target, sustract_pub)
for t in range (num+1):
h= res[t*65:t*65+65]
data = open("data-base.txt","a")
data.write(str(h.hex())+"\n")
data.close()
Is it possible to make it possible to specify an unlimited number in num?
If set num = 1000000000
That throws an error:
Traceback (most recent call last):
File "D :\PubSub\PubSub.py", line 8, in
res= ice.point_loop_subtraction(num, target, sustract_pub).hex()
File "D :\PubSub\secp256k1.py", line 504, in point_loop_subtraction
res = _point_loop_subtraction(num, pubkey1_bytes, pubkey2_bytes)
File "D :\PubSub\secp256k1.py", line 497, in _point_loop_subtraction
res = (b'\x00') * (65 * num)
MemoryError
choose a smaller amount and then change the target with the last pubkey in the database list (to continue from there).
This is all clear.
But we don't know what range our last key fell into, do we? Accordingly, we cannot know what amount and how many times it can be subtracted from it so as not to go into a minus. That's where the snag is.
P.S.:Your script works great! Thank you very much!
Update:
If, when subtracting, it was immediately checked whether you "flew over" a certain public key (went into minus or not). Back then, all public-key puzzles could be solved within an hour. Can someone write such a script?
PS: @digaran, you are awesome , 3 months ago im teaching you how to substract from public keys
WP taught me subtraction/addition, I learned division from garlonicon's posts.
Please don't take credit for things you haven't done. Thanks for kind words.!
Hello everyone What happens when dividing a scalar from a point (vector/scalar) on the secp256k1 calculator from Mr.maxwell. How can I find out what result it gives when using known points for an example, can you show an example?!.I still don't understand how division works here, I can't find the right result in any way.
PS: @digaran, you are awesome , 3 months ago im teaching you how to substract from public keys
WP taught me subtraction/addition, I learned division from garlonicon's posts.
Please don't take credit for things you haven't done. Thanks for kind words.!
@Op, in the output file I have several #targets, is that what we are looking for? How do I derive the private key now?
@Op, in the output file I have several #targets, is that what we are looking for? How do I derive the private key now?
You should only have 1 target in output file unless you ran the program more than once with same output file. The target key is the original public key you used in the settings.
To derive the private key you need to search whatever range/bits of your original public key used to generate all of the offset keys in your output file.
Now you say #target is my input, but why is it in my output file and why did the tool add + to them instead of subtracting? Because I selected -s only.
I have 3 #targets, one of them is derived from 64 hex string and 2 of them are from 31 char hex string, should I search the one leading to the target?
And why does it select the additions like this : eeeeeeeeeeeeee434343434343, did you just hit the keyboard for add/sub selection or is it doing it by itself?
I got what you said about how it works, I have a problem with the results I have got, for example:
dc629ccec8a0c3c53e5a0707021a0053a325720e3321f5fb6db3f9339eac23f7 #+ 184ffe30916bcf90fdba43677100000 and I used -s, which means I have to actually add, but add what to what and how?
Edit, one other thing, how does this adding and subtracting exactly work? Is it done using integers or hex and why do I get different results when I use decimal values to add and subtract? Could you explain this please?
dc629ccec8a0c3c53e5a0707021a0053a325720e3321f5fb6db3f9339eac23f7 #+ 184ffe30916bcf90fdba43677100000 and I used -s, which means I have to actually add, but add what to what and how?
Edit, one other thing, how does this adding and subtracting exactly work? Is it done using integers or hex and why do I get different results when I use decimal values to add and subtract? Could you explain this please?
./keysubtracter -p 02ceb6cbbcdbdf5ef7150682150f4ce2c6f4807b349827dcdbdd1f2efa885a2630-n 100 -b 120
Note the bolded part above, no space therefore it starts to produce invalid keys.
Note one of the public keys above is the 0 public key aka k(0) public key, it shows up if you subtract your k from your p, basically point at infinity.
Now our actual target's k is 13292279957849158729038070602803446 because we subtracted it from our target.
Showing examples for newbies to understand, not that a few posts above I wasn't a total noob, now I act as if I know things, go figure.😅
Note the bolded part above, no space therefore it starts to produce invalid keys.
Code:
03f1d41da8acf0506f3bf7140b5629dd33a5cf546133479530cd8065e335a97666 # - 13292279957849158729038070602803446
02000000000000000000000000000000000000000000000000000000000000000 # + 13292279957849158729038070602803446
02b70ae2dcb442548570313f652b91ca093a3acac3a2441cb64614e8195505b6b8 # - 26584559915698317458076141205606892
0367dabeef20a6a8b7b5555b162cc8c8489e3134dcec624fe028573c34dbbf20f6 # + 26584559915698317458076141205606892
02a1d21298779f888cd8169f9ed59e4383219cdadbdb342ba886034ef9013b89be # - 39876839873547476187114211808410338
02ae015703cbaee9570dc648d7bce78ac7cb438630e09d69eef4f1208655e1027d # + 39876839873547476187114211808410338
Note one of the public keys above is the 0 public key aka k(0) public key, it shows up if you subtract your k from your p, basically point at infinity.
Now our actual target's k is 13292279957849158729038070602803446 because we subtracted it from our target.
Showing examples for newbies to understand, not that a few posts above I wasn't a total noob, now I act as if I know things, go figure.😅
work on any puzzle public key puzzle 100 or 105, you will understand how it work, and put the range like this Keysubstracter -s ------- 0:fffffffffffffffffffffffff -o puzzle100.txt
do only -s dont add -a, you will have all public key from 0 to range 100
put this range always
0 to : end range
and when you create the file.txt, just go and do the maths with https://www.boxentriq.com/code-breaking/big-number-calculator
just do this privatekey of the puzzle 100 - number that you get,, in any line ,exemple af55fc59c335c8ec67ed24826 + .....
you will get the privatekey of the public key that you generate with keysubs,,,, do that with more that 20 lines randomly,,, you wil have smaller and bigger ranges pk,,, you will understand how you will search for puzzle 120 or 125 by this methode,
because your work range with rangepuzzle120:rangepuzzle120 and -a and -s
you only generate public keys between 800000000000000000000000000000 and ffffffffffffffffffffffffffffff,
but the methode above and i wanna you to try it
you will get all addresses txt file from 0 to puzzle,,, you can find any address in smaller range 10 or in 66 like 13zb1hQ did you get it ? you will now know how to search and work with this programme. its easy, you can substract 125 puzzle to 80 and 100 but you will have millions in this txt file, you can do bsgs on that file but its slow because it devide your speed to millions that you generated, so you can generate with addresses and search manually, and there is a lot of tricks how can you search , but sir your methode is totally wrong, in one case,, you generate and search with bsgs in that range already, but its the same this if you search for 1 public key 125 puzzle or a file contain 100 million public key substracted from 125 and speed is devided to 100 million, same thing already,, but you must work again on that program to learn how to use it its simple and try my methode you will get it simple, just do an exemple or old puzzle you will find how it works
4 months ago, you didint knew nothing about substraction,,,
when i did reply last week about a range did you saw what you said to me
? Hi, so i found 2 address similar 11 digits of hash160 in extraction of bit 130 that means if you scan on this range and have the private key of those one of two addresses we will split the 13 BTC
---SNIP---
---SNIP---
what makes you think that a partial string of one hash has a reference to another?
They need to learn their lessons through experience if verbal education is not effective.
😉
so please bro let us think about the puzzle and coloborate to crack it, and dont ever reply to me as the other member said that you are really act like you are genious ok?
Any C++ pro here? I have some dummy question. Is that difficult to convert Python into C++ and integrate it to Keyhunt? Or maybe I should say are we able to do some minor modification on Keyhunt by using my Python code logic because I did saw some similarity. I am currently using Python code to search and estimate can only get about 400k key per sec, if Keyhunt without GPU I can get roughly about 12 M/Keys per second. It is not compulsory to use GPU and I believe I have found some obvious pattern on 66, 67, 68. I just hope if able to integrate into Keyhunt, possibly I can increase the keys per sec instead of only around 400k per sec on Python. We can work together, find the 66,67,68 keys and share what we get.
We maybe also can work together after I find #66 keys if nobody able to find it in possibly a month time. Although much slower to find it on my current speed, but still able to find it. It might cost me like another 10-20 times difficulty to find with current speeds.
We maybe also can work together after I find #66 keys if nobody able to find it in possibly a month time. Although much slower to find it on my current speed, but still able to find it. It might cost me like another 10-20 times difficulty to find with current speeds.
PS: @digaran, you are awesome , 3 months ago im teaching you how to substract from public keys
WP taught me subtraction/addition, I learned division from garlonicon's posts.
Please don't take credit for things you haven't done. Thanks for kind words.!
Jump to: