Author: Jacob Eliosoff 2017-11-06 19:21:28
Published on: 2017-11-06T19:21:28+00:00
The email thread discusses a proposal for replay protection and fork-specific addresses to be implemented in the Bitcoin protocol. This proposal aims to standardize replay protection across different forks, which is currently done on an ad-hoc basis. The introduction of fork-specific incompatible address space ensures users are protected against accidentally sending coins on the wrong chain, as the coin/token type is encoded in the address itself. The proposed schema assigns a unique `nForkId` to each hard fork, which is appended to the final template when preparing a transaction for signing or validation. Payment addresses will also contain the fork id, allowing wallets to parse the address and display which token the user is about to spend. For light clients, the `nForkId` can be enforced in the coinbase/block header, or a new P2P message type can be introduced for sending transactions. The proposal suggests allowing signatures with `nForkId=1` through a soft fork by incrementing the script version of SegWit.
Updated on: 2023-06-12T22:02:51.823151+00:00