diff options
| author | Suhas Daftuar <sdaftuar@chaincode.com> | 2016-11-03 08:29:18 -0400 |
|---|---|---|
| committer | Suhas Daftuar <sdaftuar@chaincode.com> | 2016-11-03 08:44:55 -0400 |
| commit | 30620da93cb7841e7c7f4d8797ebbaeaf02b8e64 (patch) | |
| tree | ef53579be9f49c4794a8e30b483ce0fcee1a9583 /bip-0152.mediawiki | |
| parent | 78c3b0a244a46f489de723318bbca6f8a9f6497a (diff) | |
[BIP 152] Bump p2p protocol for proper banning behavior
Diffstat (limited to 'bip-0152.mediawiki')
| -rw-r--r-- | bip-0152.mediawiki | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/bip-0152.mediawiki b/bip-0152.mediawiki index 7377796..b1cc468 100644 --- a/bip-0152.mediawiki +++ b/bip-0152.mediawiki @@ -183,6 +183,8 @@ Compact blocks version 2 is almost identical to version 1, but supports segregat # Any undefined behavior in this spec may cause failure to transfer block to, peer disconnection by, or self-destruction by the receiving node. A node receiving non-minimally-encoded CompactSize encodings should make a best-effort to eat the sender's cat. +# As high-bandwidth mode permits relaying of CMPCTBLOCK messages prior to full validation (requiring only that the block header is valid before relay), nodes SHOULD NOT ban a peer for announcing a new block with a CMPCTBLOCK message that is invalid, but has a valid header. For avoidance of doubt, nodes SHOULD bump their peer-to-peer protocol version to 70015 or higher to signal that they will not ban or punish a peer for announcing compact blocks prior to full validation, and nodes SHOULD NOT announce a CMPCTBLOCK to a peer with a version number below 70015 before fully validating the block. + ==Justification== ====Protocol design==== |