True. He's not running BIP-110 yet. He explicitly says he's still evaluating the risks of both sides before deciding [video: 46:40-47:00]. That's exactly the point. Booth doesn't blindly follow. He rejected Core v30 because it was "dangerous" [45:08]. He runs Knots today. When PR #238 merges BIP-110 into Knots, he'll have the choice to enable it without changing software. He hasn't "overlooked" BIP-110. He's doing the work you refuse to do: thinking. While you outsource your node policy to Core maintainers who take orders from Citrea, Booth actually reads the code changes and understands the trade-offs before flipping switches. The man wrote the book on exponential change. He knows timing matters. Core v30 was the line in the sand - he crossed it. BIP-110 is the next bridge, and he'll cross it when he's done his homework. That's not uncertainty. That's intellectual sovereignty. You should try it sometime. You can start with reading View quoted note → - Video - PR #238

GitHub

Reduced Data Temporary Softfork, implemented as a modified BIP9 temporary deployment by dathonohm · Pull Request #238 · bitcoinknots/bitcoin

ReducedData Temporary Softfork (BIP-110/RDTS) Implementation of BIP-110 for Bitcoin Knots. Versionbits extensions max_activation_height (mutually ...