Skip to content

Commit db1f646

Browse files
author
Jeff Garzik
committed
Merge pull request bitcoin#262 from jgarzik/bip102_updates
BIP 102: update to match implementation
2 parents f01ec3f + 5cdae75 commit db1f646

File tree

1 file changed

+12
-11
lines changed

1 file changed

+12
-11
lines changed

bip-0102.mediawiki

Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -13,28 +13,29 @@ Simple, one-time increase in total amount of transaction data permitted in a blo
1313

1414
==Motivation==
1515

16-
# Enable network growth.
17-
# Continue current economic policy of low fee pressure on average.
18-
# Exercise network upgrade procedure.
16+
# Continue current economic policy.
17+
# Exercise hard fork network upgrade.
1918
2019
==Specification==
2120

22-
# Maximum block size permitted to be valid is 1MB.
23-
# Increase this maximum to 2MB as soon as 75% of the last 1,000 blocks have signaled support.
21+
# MAX_BLOCK_SIZE increased to 2,000,000 bytes at trigger point.
2422
# Increase maximum block sigops by similar factor, preserving SIZE/50 formula.
23+
# Trigger: (1) Block time 00:00:00 on flag day, AND (2) 95% of the last 1,000 blocks have signaled support.
2524
2625
==Backward compatibility==
2726

28-
Older clients are not compatible with this change. The first block exceeding 1,000,000 bytes will partition older clients off the new network.
27+
Fully validating older clients are not compatible with this change.
28+
The first block exceeding 1,000,000 bytes will partition older clients
29+
off the new network.
2930

3031
==Discussion==
3132

32-
In the short term, an increase is needed to continue to facilitate
33-
network growth, and buy time for more comprehensive solutions to be
34-
developed. This continues the current economic policies with regards to
35-
fees, matching market expectations and preventing market disruption.
33+
In the short term, an increase is needed to continue to current
34+
economic policies with regards to fees and block space, matching
35+
market expectations and preventing market disruption.
3636

37-
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.
37+
In the long term, this limit should focus on reflecting the maximum
38+
network engineering limit.
3839

3940
==Implementation==
4041

0 commit comments

Comments
 (0)