Bitcoin.org is a community funded project, donations are appreciated and used to improve the website.

Bitcoin Improvement Proposal 102

Block size increase to 2MB

Closed Specification Consensus (hard fork)
Repository status: Closed. This label comes directly from the canonical BIP source and may change in a later revision.
About this mirror. A BIP is a proposal or technical document. Publication here does not imply adoption, Bitcoin community consensus, or endorsement by Bitcoin.org. For authoritative text and history, use the canonical bitcoin/bips source.

Abstract

Simple, one-time increase in total amount of transaction data permitted in a block from 1MB to 2MB.

Motivation

  1. Continue current economic policy.
  2. Exercise hard fork network upgrade.

Specification

  1. MAX_BLOCK_SIZE increased to 2,000,000 bytes at trigger point.
  2. Increase maximum block sigops by similar factor, preserving SIZE/50 formula.
  3. Trigger: (1) Block time 00:00:00 on flag day, AND (2) 95% of the last 1,000 blocks have signaled support.

Backward compatibility

Fully validating 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 current economic policies with regards to fees and block space, matching market expectations and preventing market disruption.

In the long term, this limit should focus on reflecting the maximum network engineering limit.

Implementation

https://github.com/jgarzik/bitcoin/tree/2015_2mb_blocksize

Rendered from bitcoin/bips revision 60f5b33b0a7b. The document is distributed under its declared Not specified licence.