From de20066d716486f8568c0acdc633a7b3c2eb816e Mon Sep 17 00:00:00 2001 From: UdjinM6 Date: Tue, 14 Nov 2017 22:40:35 +0300 Subject: [PATCH] fix bit1 hex representation/description bit1 corresponds to 0x20000002 https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki#specification --- dip-0001.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/dip-0001.md b/dip-0001.md index b31dfc7..71f3409 100644 --- a/dip-0001.md +++ b/dip-0001.md @@ -50,9 +50,8 @@ It removes the need for users to trust in Dash’s proposal system. ## Conventions * `0x20000000` is the bit sequence `00100000000000000000000000000000` and is the current version of dash blocks. -* `0x20000001` is the version used to signal acceptance of a consensus change rule. +* `0x20000002` is the version used to signal acceptance of a consensus change rule. A miner should use this version to signal acceptance of the miner and the masternode for the block of a consensus rule change. -* We let `bit1` be the last bit of the version number read left to right. We interpret this as an integer which is either 0 or 1. * We use `%` as it is used in C++. It is the remainder on division. So `7 % 3` is 7 modulo 3 and is equal to 1. ## Prior Work @@ -102,7 +101,7 @@ However, checking if a transaction is in the mempool might take as long as verif To ensure a coherent network roll-out we employ BIP9 signaling adjusted for Dash. We reserve the last bit in the version to signal for DIP1 activation. -A DIP0001 enabled miner will broadcast block version `0x20000001` only if the masternode selected for that block is also DIP1 enabled. +A DIP0001 enabled miner will broadcast block version `0x20000002` only if the masternode selected for that block is also DIP1 enabled. We model the 2016 block difficulty adjustment period in BIP9 with a 4032 block round. This length of a round should allow for a representative sample of masternodes to be taken.