mirrors/bitcoin-bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-03-04 11:08:05 +01:00
Code Issues Projects Releases Wiki Activity

Merge pull request #229 from petertodd/bip65-spv-clients

Browse source 
BIP65 spv clients
This commit is contained in:
Luke-Jr 2015-10-27 20:53:26 +00:00
commit e770b1cd33
1 changed files with 12 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
bip-0065.mediawiki
View file

@ -277,8 +277,8 @@ We reuse the double-threshold IsSuperMajority() switchover mechanism used in
BIP 66 with the same thresholds, but for nVersion = 4. The new rules are
in effect for every block (at height H) with nVersion = 4 and at least
750 out of 1000 blocks preceding it (with heights H-1000..H-1) also
have nVersion = 4. Furthermore, when 950 out of the 1000 blocks
preceding a block do have nVersion = 4, nVersion = 3 blocks become
have nVersion >= 4. Furthermore, when 950 out of the 1000 blocks
preceding a block do have nVersion >= 4, nVersion < 4 blocks become
invalid, and all further blocks enforce the new rules.
It should be noted that BIP9 involves permanently setting a high-order bit to
@ -286,6 +286,16 @@ It should be noted that BIP9 involves permanently setting a high-order bit to
no bits in nVersion are permanently lost.
===SPV Clients===
While SPV clients are (currently) unable to validate blocks in general,
trusting miners to do validation for them, they are able to validate block
headers and thus can validate a subset of the deployment rules. SPV clients
should reject nVersion < 4 blocks if 950 out of 1000 preceding blocks have
nVersion >= 4 to prevent false confirmations from the remaining 5% of
non-upgraded miners when the 95% threshold has been reached.
==Credits==
Thanks goes to Gregory Maxwell for suggesting that the argument be compared