BIP 0102: Difference between revisions
Created page with "{{bip}} <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> {..." |
Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0102.mediawiki |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{bip}} | {{bip}} | ||
{{BipMoved|bip-0102.mediawiki}} | |||
<pre> | <pre> | ||
BIP: 102 | BIP: 102 | ||
Layer: Consensus (hard fork) | |||
Title: Block size increase to 2MB | Title: Block size increase to 2MB | ||
Author: Jeff Garzik <jgarzik@gmail.com> | Author: Jeff Garzik <jgarzik@gmail.com> | ||
Status: | Comments-Summary: No comments yet. | ||
Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0102 | |||
Status: Rejected | |||
Type: Standards Track | Type: Standards Track | ||
Created: 2015-06-23 | Created: 2015-06-23 | ||
</pre> | </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 | |||
Latest revision as of 17:59, 24 September 2019
|
This page describes a BIP (Bitcoin Improvement Proposal). |
|
Please do not modify this page. This is a mirror of the BIP from the source Git repository here. |
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: Rejected Type: Standards Track Created: 2015-06-23
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.