If after a jump I get second (cheap) point for almost free, I can calc K without this point.
Yes it's not 100% correct, but it's definitely better than counting it as 1op, showing almost twice speed at almost twice worse K.
But of course this assumption must be mentioned in the method description and I do it.
Also, it depends on a point of view: for example, if cheap point is used for vanity addresses generation, this point should be counted because it's used as a normal point. But for kangaroo jumps - this point should not be counted because only one point is used for next jump and only one point is calculated completely (both X and Y).
I have a different question, how you transfer the BTC and protect it for the bots? Use you MARA or have you a different way?
Many thanks
Hey atom13,
You need to learn a bit of how a Bitcoin Address is generated and in which ranges are we talking.
Generate private key:
1. Private key is 256 random bits.
2. Prepend version number.
3. Append compression flag.
4. Append checksum. Checksum is the first 4 bytes of double sha256 hash of whatever is being checkedsum'ed.
5. Base58 encoded data is easier to read and manage.
Generate public key:
6. Multiply the private key by the elliptic curve generator point to get the public key. The public key is a point on the elliptic curve and has x and y coordinates.
7. Use parity of y coordinate and full x coordinate to represent the public key.
8. Hash public key twice. This obfuscates the public key and shortens it.
9. Prepend version (version number is different than in step 2)
10. Append checksum (same method as step 4)
11. After another base58 encoding, we have our public address
This page will help you a bit to understand the process behind it:
https://royalforkblog.github.io/2014/08/11/graphical-address-generator/The problem with bots is in the ranges where it is fast to calculate the private key given a public key (not the same as a public address).
Moreover, puzzles 135, 140, 145, 150, 155 and 160 have the public key known, but nobody has taken the public key. That is due to the range they are in.
The problem is in puzzles 67, 68, ... where the public key is not yet available (but the public address is). The moment you send the transaction to send Bitcoin from that puzzle to a wallet of yours is when you can get the public key (it is in Mempool).
Public keys can be found inside the ScriptPubKey or ScriptSig of raw transactions.
I hope this helps you a bit to understand the process behind it. If you have any questions, feel free to ask. I will be glad to help you.