That’s one way to do it, but would be pretty ugly.

It would be better IMO to activate using BIP8 with LOT=true. That way miners will be required to signal readiness for soft fork activation before some deadline. Blocks that don’t signal would then start being rejected. (Assuming nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk will be involved with this UASF I assume this is what he’ll prefer as well.)

The URSF client should then use these same signals in the opposite way; it should start *rejecting* blocks that signal readiness.

This way you get a relatively clean split at a (more or less) predictable time.