Quote from: kalos15btc on Today at 08:46:50 PM

Quote from: tptkimikaze on Today at 08:43:35 PM

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?