From 4bc9d38dbf02bdbc8d6a88452f9192280ad55ee5 Mon Sep 17 00:00:00 2001 From: Marzig Date: Wed, 2 Sep 2015 15:05:35 -0400 Subject: [PATCH] 1MB floor Ensure that miners cannot drop the limit below 1MB --- discussion.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/discussion.md b/discussion.md index 7ac571f..2360689 100644 --- a/discussion.md +++ b/discussion.md @@ -235,7 +235,8 @@ Protocol changes proposed: 6. Schedule the hard fork on bitcoin main chain for January 11, 2016. 7. Changing the 1MB limit is accomplished in a manner similar to BIP 34, a one-way lock-in upgrade with a 12,000 block (3 month) threshold by 90% of the blocks. 8. Limit increase or decrease may not exceed 2x in any one step. -9. Miners vote by encoding ‘BV’+BlockSizeRequestValue into coinbase scriptSig, e.g. “/BV8000000/” to vote for 8M. Votes are evaluated by dropping bottom 20% and top 20%, and then the most common floor (minimum) is chosen. +9. Limit may not decrease below 1MB. +10. Miners vote by encoding ‘BV’+BlockSizeRequestValue into coinbase scriptSig, e.g. “/BV8000000/” to vote for 8M. Votes are evaluated by dropping bottom 20% and top 20%, and then the most common floor (minimum) is chosen. This creates a framework whereby the network may increase the block size by consensus, a lower and less politically risky hurdle than hard fork.