So how does one stay away from any of this? Is this temporary and when in september they launch the new PoW thing, then this gets solved? Or does it stay like this? I saw a video on Mathew Krammer's YouTube channel and said they recommended not to move any coins for now until "this resolves".
Looks like they're talking about which chain would be the real Bitcoin by saying "
until this resolves".
In that case, it's already resolved and Knots' chain is an Altcoin.
Because when a user still don't know which will be "
Bitcoin" (
although obvious), he might be opening himself for replay attack in the Bitcoin chain after he moved a coin on the chain that'll be an altcoin.
The recommendation is most likely for users who don't know what they're doing.
For the replay issue, it's only per UTXO that's existing in both chains.
Not its children after you managed to "
split" it.
For example:
UTXO- "
0123456:0" is in Bitcoin and Knots chain since it remained unspent before the fork.
You spent it in Bitcoin blockchain creating new UTXO- "
0000001:0" in Bitcoin Blockchain.
Then, the transaction above is not replayed in Knots blockchain and you spent it with a different output, creating a new UTXO- "
1111112:0" in Knots Blockchain.
With that, UTXO- "
0123456:0" is now spent in both chains.
The newly created UTXO (
"0000001:0" and "1111112:0") are exclusive in their respective chains since those are created after the fork.
So, replaying the transactions that will spend those will be invalid in the other chain because the UTXO used as in its input doesn't exist there.
This applies to those UTXO's children as well.
The edge case here is if the newly created UTXO is exactly the same in both chains.
That could happen in you use the exact same output, amounts, and everything in the transaction that will produce the same hash,
basically replaying your own transaction from the other chain so the new UTXO is still the same in both chains.
I don't get it. Why they didn't implement replay protection? isn't this considered a standard safety measure when forking?
If one is in a delusion that its blockchain will be the real "
Bitcoin", enabling replay protection wouldn't be necessary since other clients would be forking away instead in that mindset.