Skip to content
This repository has been archived by the owner on Jul 2, 2022. It is now read-only.

Vote search edge cases #21

Merged
merged 2 commits into from
May 4, 2017
Merged

Vote search edge cases #21

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b82d840
Vote search edge cases
dgenr8 May 1, 2017
4ed2a0e
Update headers, copyright, reference impl
dgenr8 May 4, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions bip-0100.mediawiki
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,14 @@
<pre>
BIP: 100
Layer: Consensus (hard fork)
Title: Dynamic maximum block size by miner vote
Author: Jeff Garzik <jgarzik@gmail.com>
Tom Harding <tomh@thinlink.com>
Dagur Valberg Johannsson <dagurval@pvv.ntnu.no>
Status: Draft
Type: Standards Track
Created: 2015-06-11
License: BSD-2-Clause
</pre>

==Abstract==
Expand All @@ -27,14 +29,14 @@ The system is compatible with emergent consensus, but whereas under that system
# Initial value of <code>hardLimit</code> is 1000000 bytes, preserving current system.
# Changing <code>hardLimit</code> is accomplished by encoding a proposed value, a vote, within a block's coinbase scriptSig, and by processing the votes contained in the previous retargeting period.<br /><br />
## Vote encoding
### A vote is represented as a positive megabyte value using the BIP100 pattern<br /><br /><code>/BIP100/B[0-9]+/</code><br /><br />Example: <code>/BIP100/B8/</code> is a vote for a 8000000-byte <code>hardLimit</code>.<br /><br />
### A vote is represented as a megabyte value using the BIP100 pattern<br /><br /><code>/BIP100/B[0-9]+/</code><br /><br />Example: <code>/BIP100/B8/</code> is a vote for a 8000000-byte <code>hardLimit</code>.<br /><br />
### If the block height is encoded at the start of the coinbase scriptSig, as per BIP34, it is ignored.
### Only the first BIP100 pattern match is processed in "Maximum block size recalculation" below.
### A valid megabyte value is represented by consecutive base-ten digits.
### A megabyte value is represented by consecutive base-ten digits.
### If no BIP100 pattern is matched, the first matching emergent consensus pattern <code>/EB[0-9]+/</code>, if any, is accepted as the megabyte vote.<br /><br />
## Maximum block size recalculation
### A <code>new hardLimit</code> is calculated after each difficulty adjustment period of 2016 blocks, and applies to the next 2016 blocks.
### Absent/invalid votes are counted as votes for the <code>current hardLimit</code>.
### Absent/zero-valued votes are counted as votes for the <code>current hardLimit</code>.
### The votes of the previous 2016 blocks are sorted by megabyte vote.
### Raising <code>hardLimit</code><br /><br />
#### The <code>raise value</code> is defined as the vote of the 1512th highest block, converted to bytes.
Expand All @@ -61,3 +63,9 @@ This BIP is presumed deployed and activated as of block height 449568 by impleme

The first block larger than 1M will create a network partition, as nodes with a fixed 1M hard limit reject that block.

==Reference Implementation==
https://github.com/bitcoinxt/bitcoinxt/pull/188

==Copyright==
This document is licensed under the BSD 2-clause license.