I've been lurking (and discussing) in Luke's Bitcoin Knots discord as we discuss the hardfork strategy. I think this point is really important to get clear, because a lot of plebs on our side still have a terrible misconception about it. Replay "attacks" are actually not a bug, they're a feature for people who are unsure which chain is the real Bitcoin Timechain, either because they haven't had time to weigh the arguments (or even hear them), or because they've been duped. It carries much of their economic activity over to the correct chain, it allows you to use Bitcoin to some extent even if you get tricked into accepting invalid blocks for a while. You can switch to the correct consensus rules and pick up where you left off with much or all of your post-split history intact. The BLAKE2b hardfork is adding an opt-in to transactions that lets you choose to split your coins (the act of transacting on the BLAKE2b chain with the new opt-in sighash in the transaction itself permanently splits the coins). It is opt-in by design. If you want to use a chain without any chance of replay, it is your responsibility to ensure that. We are not going to sacrifice the property of people who have been duped by invalid blocks for the sake of a minor convenience for you. To sum up this whole concept in Luke-speak, which is delightfully simple and gets to the very essence of this, > Bitcoin isn't going to make Bitcoin transactions invalid to protect scamcoiners. Further hammering this home, Luke added: > Keep in mind that would block Lightning channels from closing So stop calling replay an "attack." Permitting it preserves Bitcoin, and preserves users' sats. Bitcoin is Bitcoin. It is not an airdrop. The onus to split from Bitcoin is on Scamcoin.