@unpluggedcoin I see so much potentials in this code... I need to know how we can further get something to work by mapping one point to another on the curve so even if x coordinates is not going to hit, maybe the double or subtracted or divided would... we can work together if you want... though still very new with the curve but I'm trying my best... I must admit.
To all who are using my script and have doubts!
First of all, the script is not some kind of magical idea or trick no nothing! It is simplest subtraction of equal amount in parts! The script won't generate any points itself into checkpoints.txt file. You have to provide it both checkpoints.txt and xy.txt files. It will only generate j_value.txt file in which it will be saving number of iterations (you'll know what they are in a minute). The script is a simplest possible kangaroo sort of thing and nothing else. Let me explain again:
Suppose our puzzle pub key has the private key 1593 and its bit range is between 1024 to 2048.
You have its public key x and y coordinates in decimal format in xy.txt file in same directory.
You have checkpoints.txt file in which you have public key x coordinate only in decimal (1 per line).
These are the public keys of starting private keys. In our example suppose they are 2 to 11. Now you have 10 x coordinates in checkpoints.txt file. (The important point why I gave it a shot is that I liked the idea of doubling the checkpoints while keeping it single because starting 10 private keys and last 10 private keys have same x coordinates. So if you subtract public key of 15 (15 is private key) from the public key of 10 (10 is private key) you'll get the public key of n-4 whose x coordinate must be same as of 5.
back to our example So you place initial 11 public keys x coordinates in checkpoints.txt file.
Script loads checkpoints.txt file and subtracts from it equal parts in one iteration and write 1 in j_value.txt file. I writes 2 after second iteration and so on. So if power goes out or anything happens and system is off, your script will start from where it left. Here is our example working:
pubkeys 2-11 are loaded.
You can change your settings, i'll just show what I did back there:
As we know the range it is between 1024 and 2048 (For puzzle 125 I divided the starting range into 100,000 parts, so scripts single iteration has 100,000 parts, (these are sort of subtraction jumps) in our example suppose we pick 16 equal jumps and we divide range into 10 parts so one subtraction is subtracting 102 (there is always be a whole number in EC don't worry about perfect numbers). Let's run it,
1593-102=1491 (script matches this point within checkpoints.txt file, NO MATCH)
1491-102=1389 (NO MATCH)
1389-102=1287=(NO MATCH)
.
.
.
165-102=63 (NO MATH)
1st iteration completed. The script writes 1 in j_value.txt file. NOW script subtracts 11 from your puzzle pub key and then starts iteration:
1593-11= 1582 (Now this replaces the starting point, now please don't asks how you would get back to original pub key, be mindful)
1582-102=1480 (NO MATCH)
1480-102=1378 (NO MATCH)
.
.
.
154-102=52 (NO MATCH)
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
Few pages earlier OP himself asked if someone needed help to upgrade system and stuff like that, I saw people bashing other people, sort of disappointing! I did asked him if I could have access to a strong CPU with more RAM and few TB HARD, I could have cracked puzzle 125, considering the time I ran those script on my dual core with upgraded 8 RAM.