mirror of
https://github.com/bitcoin/bips.git
synced 2024-11-19 09:50:06 +01:00
43 lines
1.4 KiB
Plaintext
43 lines
1.4 KiB
Plaintext
<pre>
|
|
BIP: 102
|
|
Title: Block size increase to 2MB
|
|
Author: Jeff Garzik <jgarzik@gmail.com>
|
|
Status: Draft
|
|
Type: Standards Track
|
|
Created: 2015-06-23
|
|
</pre>
|
|
|
|
==Abstract==
|
|
|
|
Simple, one-time increase in total amount of transaction data permitted in a block from 1MB to 2MB.
|
|
|
|
==Motivation==
|
|
|
|
# Enable network growth.
|
|
# Continue current economic policy of low fee pressure on average.
|
|
# Exercise network upgrade procedure.
|
|
|
|
==Specification==
|
|
|
|
# Maximum block size permitted to be valid is 1MB.
|
|
# Increase this maximum to 2MB as soon as 75% of the last 1,000 blocks have signaled support.
|
|
# Increase maximum block sigops by similar factor, preserving SIZE/50 formula.
|
|
|
|
==Backward compatibility==
|
|
|
|
Older clients are not compatible with this change. The first block exceeding 1,000,000 bytes will partition older clients off the new network.
|
|
|
|
==Discussion==
|
|
|
|
In the short term, an increase is needed to continue to facilitate
|
|
network growth, and buy time for more comprehensive solutions to be
|
|
developed. This continues the current economic policies with regards to
|
|
fees, matching market expectations and preventing market disruption.
|
|
|
|
In the long term, continued direct management of this limit is a moral hazard that clouds free market input and prevents a healthy fee market from developing. This area of code should be transitioned away from direct management.
|
|
|
|
==Implementation==
|
|
|
|
https://github.com/jgarzik/bitcoin/tree/2015_2mb_blocksize
|
|
|