Nope. It is not critical update for my version. Gradually, our scripts are starting to diverge in terms of functionality. The next thing I’m going to update is SECP256K1 itself—I’ve already removed some unnecessary files from Git, like Timer.cpp, Timer.h, Random.cpp, and Random.h. They were just collecting dust and serving no purpose, unnecessarily increasing the size of the executable file.
How many keys are scanned at once (batch = group_size) when using sequential or random mode? 0x10000? 0x100000?
This would be interesting to know, for example, when using STRIDE.
If I start at 0x400000000000000000 and STRIDE = 0x10000000 and BATCH = 0x10000, at the end of each round I just need to add
BATCH * Number of rounds to the start point 0x400000000000000000 (keeping the same STRIDE value)
The same principle of both python scripts that I had sent you in PM some weeks before.
That function has never worked here as it should. It just causes problems—either showing unrealistically high speeds or unrealistically low ones. I think I’ll remove it from the script altogether