mirror of
https://github.com/bitcoin/bips.git
synced 2025-02-23 23:27:22 +01:00
Add note about free bits and correct deployment recommendations
This commit is contained in:
parent
c141645a1f
commit
060c37f6d5
1 changed files with 3 additions and 1 deletions
|
@ -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>
|
||||
|
|
Loading…
Add table
Reference in a new issue