These values are not very important, but I think having to change the config at upgrade time is better than having to restart the client at a precise time.
I think we’re mostly waiting for exchange comments.
Still, about #1:
Exchanges are intensive users of the client and the most likely to find bugs in the large internal changes. So recommending them to make this important upgrade at a specific time without a possible way back adds the risk of a temporary delisting if something goes wrong, until the problem is fixed.
I think it’s less risky to have 2 distinct upgrades. Note that 2.2 could also have an automatic switch time if we want. It’s just mixing the important internal changes and the time constrained upgrade that concerns me.
