if (blocknum % 1000 = 0) and (most recent 256 headers time >= FORKTIME). Only occuring at x000 blocks provides some certanty, as well as provides a backward compatible number we can say “the fork was at block x000"
Couple other q's:
@tkstanczak which version of Nethermind should I include in the blog post that points to Istanbul compatibility?
@holiman @Arachnid @cdetrio @jpitts is anyone responsible for http://forkmon.ethdevops.io/?
v4.1.1(introduced beta support for Istanbul) is highly recommended.
@/all Istanbul announcement blog released.
We are recommending people update their nodes before Dec. 1st in order to account for variable block times
Tweet with fun emojis: https://twitter.com/hudsonjameson/status/1197021040305754112?s=20
Reddit Thread: https://www.reddit.com/r/ethereum/comments/dyx7oq/ethereum_istanbul_upgrade_announcement/
Spread the word to your friends, miners, exchanges, and anyone else running a node!
did some more digging:
since the diff bomb delay is 2mn blocks from when it started kicking in last, the increase in block times syncs up perfectly.
~1 month ago the diff bomb kicked in at around block 876xxxx
~1 year ago the diff bomb kicked in at around block 676xxxx
It's rough data but it fits the theory that block times are getting longer due to the diff bomb.