Universal opt-in replay protection?

The concept of reorganization (reorg) safety in Bitcoin transactions is a crucial aspect of network stability and user trust. Reorgs, which refer to changes in the blockchain due to forks or other alterations, can potentially invalidate transactions unless specific safeguards are in place. One prominent suggestion for enhancing reorg safety is to implement height locks on transactions, where a transaction references a block some distance back from the current one—commonly proposed at 100 blocks. This distance helps ensure that only extreme reorganizations, beyond this 100-block horizon, could affect the transaction, thus adding a layer of security against frequent, minor reorgs.

However, there is debate surrounding the appropriateness of this 100-block parameter. Some argue that adversaries who control the blockchain's progression can manipulate such rules to their advantage. For instance, in scenarios where blockchain forkers act with hostility—as seen in some cases where there was an absence of replay protection or it was made intentionally difficult to use—the risk is that these actors might simply choose to ignore or alter the agreed-upon rules like the 100-block reference to disrupt transactions deliberately.

Furthermore, the practice of using generated coins' children as a method of achieving reorg safety is mentioned. While theoretically feasible, it involves significant social and commercial complexity, potentially making simpler solutions like setting transaction fields more attractive. Despite these challenges, the ongoing dialogue about how best to secure transactions against reorgs illustrates both the technical and strategic dimensions of cryptocurrency management. The discussion underscores the importance of considering both technological safeguards and the broader behavioral patterns of network participants when designing systems that can withstand such challenges.