Search results
Jump to navigation
Jump to search
- ...to enforce new rules, without support from miners, it is called a '''user-activated softfork''' (UASF). 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
- abandoned in favor of levelDB, and - at the same time - the miner's ===Unilateral softforks=== ...18 KB (2,863 words) - 21:58, 30 April 2024
- ...efined flag timestamp (or flag block height), instead relying on measuring miner support indicated by a higher version number in block headers. As it relies # '''name''' should be selected such that no two softforks, concurrent or otherwise, ever use the same name. ...14 KB (2,096 words) - 15:42, 15 December 2021
- # The '''timeoutheight''' specifies a block height at which the miner signalling ends. Once this height has been reached, if the soft fork has no # '''name''' should be selected such that no two softforks, concurrent or otherwise, ever use the same name. For deployments described ...17 KB (2,558 words) - 15:52, 15 December 2021
- ...t relay policy turned on, and with a small amount of money after BIP141 is activated on mainnet. ...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 ...26 KB (3,935 words) - 23:08, 26 April 2024