Merge pull request #194 from btcdrak/patch-2

BIP105: Update to account for BIP34

bip-0105.mediawiki

@@ -62,10 +62,12 @@ Each time a miner creates a block, they may vote to increase or decrease the
 blocksize by a maximum of 10% of the current block size limit. These votes will 
 be used to recalculate the new block size limit every 2016 blocks.
 
-Votes are cast using the block's coinbase field.
+Votes are cast using the block's coinbase transaction scriptSig.
 
-The first 4 bytes of the coinbase field shall be repurposed for voting as an
-unsigned long integer which will be the block size in bytes.
+As per BIP34, the coinbase transaction scriptSig starts with a push of the block
+height. The next push is a little-endian number representing the preferred block
+size in bytes. For example, 0x4c(OP_PUSHDATA1) 0x03(size of constant) 0x80 0x84 0x1e(2MB)
+or 0x4c(OP_PUSHDATA1) 0x04(size of constant) 0x80 0x96 0x98 0x00(10MB).
 
 If a miner votes for an increase, the block hash must meet a difficulty target
 which is proportionally larger than the standard difficulty target based on the
@@ -95,6 +97,10 @@ This proposal is based on ideas and concepts derived from the writings of
 Meni Rosenfeld and Gregory Maxwell.
 
 
+==References==
+
+[[bip-0034.mediawiki|BIP34]]
+
 ==Copyright==
 
 This work is placed in the public domain.