Author: Mats Jerratsch 2017-11-10 11:28:06
Published on: 2017-11-10T11:28:06+00:00
This proposal suggests using `nForkId=1` for Bitcoin, which would make `nForkId=0` valid on all future forks. This would allow for the creation of `nLockTime` transactions and backing up future-safe addresses even if the sending wallet displays a warning message about unknown side effects. `nForkId=0` can also be used for L2 applications that require replay protection. With this proposal, users have additional choices to make in scenarios involving forks, such as creating commitment transactions with `nForkId=0` or making the protocol aware of different `nForkId`. The author also considers using the human-readable part of the standard as the fork id and discusses its potential limitations.
Updated on: 2023-06-12T22:02:09.716396+00:00