diff options
| author | BtcDrak <btcdrak@gmail.com> | 2015-11-20 17:12:43 +0000 |
|---|---|---|
| committer | BtcDrak <btcdrak@gmail.com> | 2015-11-20 18:56:00 +0000 |
| commit | 060c37f6d530881e4e5b06a711244adb2d18a7de (patch) | |
| tree | 1380f0acde2c3c7195c592b44a55ce1290d24f60 | |
| parent | c141645a1f6428ba183c927391efb1d316f45743 (diff) | |
Add note about free bits and correct deployment recommendations
| -rw-r--r-- | bip-0068.mediawiki | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/bip-0068.mediawiki b/bip-0068.mediawiki index 6d0b146..8077d08 100644 --- a/bip-0068.mediawiki +++ b/bip-0068.mediawiki @@ -189,7 +189,7 @@ This BIP was edited by BtcDrak, Nicolas Dorier and kinoshitajona. This BIP is to be deployed by either version-bits BIP9 or by isSuperMajority(). Exact details TDB. -It is recommended to deploy BIP68 and BIP112 at the same time as this BIP. +It is recommended to deploy BIP112 and BIP113 at the same time as this BIP. ==Compatibility== @@ -197,6 +197,8 @@ The only use of sequence numbers by the Bitcoin Core reference client software i As can be seen from the specification section, a number of bits are undefined by this BIP to allow for other use cases by setting bit (1 << 31) as the remaining 31 bits have no meaning under this BIP. Additionally, bits (1 << 23) through (1 << 30) inclusive have no meaning at all when bit (1 << 31) is unset. +Additionally, this BIP specifies only 16 bits to actually encode relative lock-time meaning a further 6 are unused (1 << 16 through 1 << 21 inclusive). This allows the possibility to increase granularity by soft-fork, or for increasing the maximum possible relative lock-time in the future. + The most efficient way to calculate sequence number from relative lock-time is with bit masks and shifts: <pre> |