pull down to refresh
I don't see that in the code, I think
reply
My bad, I should have stated my assumptions, especially given that my assumption appears to have been incorrect.
BIP 9 does not have the lockinontimeout mechanism as it was introduced later by BIP 8. I assumed that RDTS was going to reuse the semantics of BIP 8 which enforce activation by mandatory signaling, but it appears that this assumption was incorrect, instead RDTS appears to simply switch to LOCKED_IN one difficulty period and a block before the max activation height, so a flag day activation was actually a fitting description.
reply
[as they’d have to find two blocks before the rest of the network finds one] … each and every time the majority of the hashrate adds a block that does not adhere to the soft fork rules.