Author: Sjors Provoost 2017-11-09 21:01:10
Published on: 2017-11-09T21:01:10+00:00
In a discussion on the bitcoin-dev mailing list, Jacob Eliosoff asked about the validity of an address across various forks. He suggested that while a private key in cold storage would remain valid across hard forks, an address would only be valid for the fork it was generated for. However, he raised the possibility of scenarios where it might be necessary for an address to be valid across all chains, such as to intentionally allow replay protection. The proposal suggests that nForkId could be used to specify the fork in bech32. While nForkId is only in the transaction signature pre-image and not in the serialized transaction, a node would just need to check if the signature is valid. The purpose of nForkId 1 is unclear, but it may provide a way to opt-out of replay protection of any fork, where deemed necessary (can be beneficial for some L2 applications). In Spoonnet, the version number is added to the SIGHASH_TYPE in the pre-image.
Updated on: 2023-06-12T22:02:01.517508+00:00