<p>There isn't any blockchain voting for accepting a BIP: See <a href="https://bitcoin.stackexchange.com/questions/5640/how-is-a-bip-accepted">How is a BIP accepted?</a> and <a href="https://github.com/bitcoin/bips/blob/master/bip-0001.mediawiki" rel="nofollow noreferrer">BIP0001</a>.</p>

<p>Rather, the BIP is accepted or rejected on the basis of consensus. Consensus is never defined, but even if you interpret it fairly broadly, I don't think any of the three will reach consensus.</p>

<p>There are frequently blockchain votes about activating the new rules, but that's less of a mechanism to measure acceptance and more of a way to only deploy the new changes once enough of the network runs them that the switchover won't be disruptive.</p>

<p>There is a related issue, which is Bitcoin-XT, which grew out of several developer's frustrations with the process. That proposes to alter the blocksize according to BIP 101 once more than 75% of the blocks are created by Bitcoin-XT nodes. But that's not something within the BIP process.</p>

CC BY-SA 3.0
2015-08-16T20:30:23.670Z
You might want to differentiate between hard and soft changes, as there's a catastrophic difference between the two.
Claris
CC BY-SA 3.0
2015-08-16T20:33:04.230Z
The distinction is important, but it's out of scope of the question, and has been elaborated elsewhere.
Nick ODell
CC BY-SA 3.0
2015-08-16T20:38:43.063Z
It's necessary in understanding why it isn't up to miners to make breaking changes, and why voting for it with a coinbase string isn't completely appropriate.
Claris
CC BY-SA 3.0
2015-08-16T21:13:12.737Z
@Bitcoin Nor are hardforks entirely up to Bitcoin Core developers. I sense that we're getting into an argument that we've had before. I feel that my answer to the asker's question is complete. If you disagree, you're free to write an answer.
Nick ODell
CC BY-SA 3.0
2015-08-16T20:22:04.390Z
2015-09-09T22:50:32.553Z
2017-04-13T12:47:32.940Z
Nick ODell
<p>Are the BIP 100, BIP 101 and BIP 102 proposals being voted on now by miners? What is the procedure for a bitcoin miner to vote for a particular BIP and where can a tally of votes be viewed?</p>

<bip>
Are BIP 100, 101 and 102 being voted on now by Bitcoin miners?
allegro101
# Are BIP 100, 101 and 102 being voted on now by Bitcoin miners?

(Asked by: username_0 on 2015-08-16)

Are the BIP 100, BIP 101 and BIP 102 proposals being voted on now by miners? What is the procedure for a bitcoin miner to vote for a particular BIP and where can a tally of votes be viewed?

**Tags:** bip


---

## 1 answers

### Answer by username_1 on 2015-08-16. Score: 3

There isn't any blockchain voting for accepting a BIP: See [How is a BIP accepted?](https://bitcoin.stackexchange.com/questions/5640/how-is-a-bip-accepted) and [BIP0001](https://github.com/bitcoin/bips/blob/master/bip-0001.mediawiki).

Rather, the BIP is accepted or rejected on the basis of consensus. Consensus is never defined, but even if you interpret it fairly broadly, I don't think any of the three will reach consensus.

There are frequently blockchain votes about activating the new rules, but that's less of a mechanism to measure acceptance and more of a way to only deploy the new changes once enough of the network runs them that the switchover won't be disruptive.

There is a related issue, which is Bitcoin-XT, which grew out of several developer's frustrations with the process. That proposes to alter the blocksize according to BIP 101 once more than 75% of the blocks are created by Bitcoin-XT nodes. But that's not something within the BIP process.

> **Comments:**
> **username_2**: You might want to differentiate between hard and soft changes, as there's a catastrophic difference between the two.  
> **username_1**: The distinction is important, but it's out of scope of the question, and has been elaborated elsewhere.  
> **username_2**: It's necessary in understanding why it isn't up to miners to make breaking changes, and why voting for it with a coinbase string isn't completely appropriate.  
> **username_1**: @Bitcoin Nor are hardforks entirely up to Bitcoin Core developers. I sense that we're getting into an argument that we've had before. I feel that my answer to the asker's question is complete. If you disagree, you're free to write an answer.  

---

