Skip to content

BIP 102: update to match implementation #262

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jgarzik merged 3 commits into from
Jan 19, 2016
Merged

BIP 102: update to match implementation #262

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
097983d
BIP 102: update to match implementation
jgarzik Dec 18, 2015
3211298
BIP 102: remove dynamic adjustment
jgarzik Dec 18, 2015
5cdae75
BIP 102: 95% update req
jgarzik Dec 18, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 12 additions & 11 deletions bip-0102.mediawiki
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,28 +13,29 @@ Simple, one-time increase in total amount of transaction data permitted in a blo

==Motivation==

# Enable network growth.
# Continue current economic policy of low fee pressure on average.
# Exercise network upgrade procedure.
# Continue current economic policy.
# Exercise hard fork network upgrade.

==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.
# 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==

Older clients are not compatible with this change. The first block exceeding 1,000,000 bytes will partition older clients off the new network.
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 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 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, 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.
In the long term, this limit should focus on reflecting the maximum
network engineering limit.

==Implementation==

Expand Down