Nov 4, 2026

I've changed bip90 to off by default. It's the only hard fork we've been carrying, and there's no reason for it. It costs 10-15 seconds on the header sync to disable it. It's a hard fork material query optimization for Core, but we don't need it. I pointed out that it was a hard fork when they documented it, and they argued about it, called it a hard fork, and then reverted that status to unspecified. And after that they never documented another, but there have been seven others by my count (4 hard forks, 3 soft forks). The only difference with bip90 is that they posted it to a website after the fact. That's not counting the LevelDB bug, stopgap, and removal, or the inflation bug and removal. That's 5 more forks (3 hard, 2 soft), but since those weren't intentional, I'm discounting them above.