Search results

Jump to: navigation, search
  • # '''name''' should be selected such that no two softforks, concurrent or otherwise, ever use the same name. # '''bit''' should be selected such that no two concurrent softforks use the same bit.
    14 KB (2,076 words) - 17:58, 24 September 2019
  • | [[Consensus versions|Various hardforks and softforks]] | Softforks: Rel locktime, CSV & MTP locktime
    31 KB (4,299 words) - 21:52, 12 April 2020
  • When a majority of miners upgrade to enforce new rules, it is called a '''miner-activated softfork''' (MASF). When full nodes coordinate to enforce new rules, withou New transaction types can often be added as softforks, requiring only that the participants (sender and receiver) and miners unde
    6 KB (1,054 words) - 14:29, 21 September 2018
  • ...m the entire community of users - not necessarily unanimous in the case of softforks (and it is up to each entity to decide what level of support they require f
    9 KB (1,312 words) - 05:11, 21 June 2017
  • ===Unilateral softforks=== ====Uncontroversial softforks====
    18 KB (2,863 words) - 17:59, 24 September 2019
  • ...release of segregated witness at reference implementation version 0.13.1. Softforks based on these policies are likely to be proposed in the near future. To av ...nsensus meaning, but in the future allows new commitment values for future softforks. For example, if a new consensus-critical commitment is required in the fut
    25 KB (3,853 words) - 17:58, 24 September 2019