Done with map changes. Shouldn't ever get stuck now, and should also still pick up new work as it comes in.
Also, I quickly bound the map filter options to a key so you can select between no map filtering, and the two map filters minim1ner released.
However, I just realized that the secondary work code in motogame got lost somewhere during the other patches. I'm going to have to work that back in very quickly. Noone build against master right now! :\
What was the url to your master branch again?
https://github.com/hunterminercrafter/motocoinI just re-merged the secondary work function, without the openssl dependency in motogame. (Someone please sanity check my compact representation logic?!?!)
This code has been running on a testnet in testmode with a ~200% warp set on all the mining bots. It appears to be stable, however, it also took about 20 re-targets before the secondary work function settled on a difficulty. Since we're currently using the same 2000 block interval for the second target check, this ends up allowing for quite a bit of the work deficit created in a warp to go unpaid over time! As such, I'm redoubling my stance that we should quickly follow this up with another change to apply the secondary target calculation at a more frequent interval. (Hopefully *none* of this crap will ever become relevant/necessary because hopefully nobody will ever attempt any warp attacks to begin with, but "better safe than sorry" ofc! It would certainly be preferable to constrain warp "steps" to tens of blocks instead of thousands, for hopefully self-evident reasons.)
I've also re-merged the median correction, since we are forking anyway. This should accelerate (downward) TT adjustment by a very small amount.
Those 10k blocks are going by a bit faster than I expected... I had originally estimated them at just over 48 hours but we are already halfway there! Should we delay the fork point more blocks? Personally I want to see the network secured as soon as possible, so I'm all for sticking with the 100k mark. Thoughts?
EDIT: Woops, just realized that I also let one of my private/internal patches slip through as well. Perhaps the content of it is a bit "telling" but I'm going to just leave it and call it a feature. It will become a relevant patch for users soon enough anyway, so it wouldn't have been long before I released it. It was just originally intended to go out along with some other "still secret" stuff.