1
0
mirror of https://github.com/bitcoin/bips.git synced 2026-01-19 15:03:08 +00:00
bips/bip-0102.mediawiki
Murch a233bde4af
process: Standards Track ↦ Specification
```
sed -z -i 's/Type: Standards Track/Type: Specification/' bip-0*.md
sed -z -i 's/Type: Standards Track/Type: Specification/' bip-0*.mediawiki
```

After the scripted changes, the changes to BIP-40, BIP-41, and BIP-63
were undone, because it breaks CI.

These three BIPs only exist conceptually and their proposal documents
are missing which causes changes to them ot break the CI. I defer the
changes to these BIPs to a separate pull request to get CI to pass.
2026-01-12 14:22:40 -08:00

47 lines
1.3 KiB
Plaintext

<pre>
BIP: 102
Layer: Consensus (hard fork)
Title: Block size increase to 2MB
Author: Jeff Garzik <jgarzik@gmail.com>
Comments-Summary: No comments yet.
Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0102
Status: Closed
Type: Specification
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==
# Continue current economic policy.
# Exercise hard fork network upgrade.
==Specification==
# MAX_BLOCK_SIZE increased to 2,000,000 bytes at trigger point.
# Increase maximum block sigops by similar factor, preserving SIZE/50 formula.
# 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