Skip to content

Commit ee2ea4f

Browse files
committed
trigger build 3
1 parent 57a67f0 commit ee2ea4f

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

scalingbitcoin/hong-kong-2015/a-bevy-of-block-size-proposals-bip100-bip102-and-more.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,7 @@ A: That's reasonable. You are going to be rolling out a patch, which says 6 mont
9191

9292
Q: In one of those slides, you said 75% levels, so 750 out of 1000 blocks. That was bip101. What is your optimal choice for that? Is it 75% 80% 90%?
9393

94+
9495
A: That's why we're leaning towards flag day with non-binding miner voting. It's to avoid picking a specific number. You want to have a clear majority of hashpower on the fork that users prefer. I don't want to pick a number. I don't have a number. It's just a supermajority of the hashpower. That's step 2. But step 1 is the users agreeing by running the new software.
9596

9697
Q: Would you break SPV clients in a hard-fork?

0 commit comments

Comments
 (0)