On soft-forks and hard-forks



Summary:

The discussion revolves around whether to reject blocks with nVersions that a node does not expect, and the implication of doing so. Rejecting such blocks could potentially lead to an isolated chain fork, which is not desirable as it undermines the security model of Bitcoin. The suggestion is to accept and relay these blocks, with some minor safeguards to prevent DoS attacks. Soft-forks and SPV nodes are also discussed, with the conclusion that allowing miners to upgrade their SPV nodes is acceptable. The nVersion field can be used for voting on upgrades, and a two-stage approach is suggested to signal intent to upgrade and when the new rules are active.


Updated on: 2023-06-07T18:52:14.213826+00:00