What's wrong with uasf? the whole thing seems pretty cut and dry to me
>>2482936
because it can lead to two simultaneous competing forks, with possible replay attacks and wipeouts leading to transactions affecting both forks and/or transactions with many confirmations being invalid