Default signet reorg history — was the fork at height 287766 (depth 19) deliberate?

The discussion raises an important consideration regarding the handling of deep reorganizations (reorgs) in blockchain networks. It is suggested that instead of using a shared default approach which could lead to unexpected challenges, it might be more prudent to have an opt-in mechanism. This would allow participants to choose their level of engagement with deep reorg testing rather than being caught off-guard.

However, there is a counterargument presented that highlights the unpredictability of deep reorgs on mainnet, which do not provide the luxury of opting in or out. Given this reality, the suggestion is made to increase the frequency of such tests on Signet. This approach would presumably offer better preparedness for similar scenarios on the mainnet, enhancing the robustness and reliability of the network in dealing with real-time issues.

This debate underscores the need for careful consideration and strategy in the testing and implementation of blockchain protocols, particularly in regards to potentially disruptive events like deep reorgs.