<p>The version and other parameters that could be used for signaling are generally set by the work producer, i.e. your own node or the pool you are mining with. That will issue the work for your mining hardware and include what block version to produce.</p>
<p>For your own pool or node, you would have to configure your pool or node software to produce work with your desired block version. It depends on the software - it may have some setting that you can set, or you may need to use a different version of the software itself.</p>
<p>If you mine with a third party pool, you'd generally have to switch to a different pool if you wanted to signal.</p>
<p>Note that it is not voting, but rather it is signaling readiness. The purpose is for miners to signal to every other node on the network that they are ready to enforce the new soft fork rules. Since the hashrate hardware is not receiving and validating new blocks and transactions, having it set the version (or other signaling mechanism) would not make sense. Thus the entity that is issuing the work needs to set the version as that entity should be receiving and validating new blocks and transactions, and can therefore make the decision about whether it is ready to enforce the new rules.</p>
<blockquote>
<p>Does the vote only count if you win a block?</p>
</blockquote>
<p>Yes. The only way for other nodes on the network to know what you are signaling is by receiving a valid block from you. So you have to produce valid blocks to be counted.</p>

CC BY-SA 4.0
2024-03-03T03:45:36.430Z
2024-03-03T03:45:36.430Z
Ava Chow
<p>Where, exactly, do these tags for <code>scriptSig</code> and <code>nVersion</code> get entered or modified? I don't see any field to do so on my asic config webpage, nor on my USB miner cgminer.</p>
<p>For example, I have a small USB miner, using cgminer, connected to my own pool running on my umbrel node. How would I have signaled support for a previous BIP (or possibly in the future)? Does the vote only count if you win a block?</p>
<p>I also have an ASIC miner connected to a third party pool. Would I be able to &quot;vote&quot; with that miner? Or is my &quot;vote&quot; simply my choice to mine to that pool versus another?</p>

<miner-configuration><bip><bip9-version-bits>
How do miners signal approval for a BIP via nVersion, exactly?
VegArchie
# How do miners signal approval for a BIP via nVersion, exactly?

(Asked by: username_0 on 2024-03-03)

Where, exactly, do these tags for `scriptSig` and `nVersion` get entered or modified? I don't see any field to do so on my asic config webpage, nor on my USB miner cgminer.

For example, I have a small USB miner, using cgminer, connected to my own pool running on my umbrel node. How would I have signaled support for a previous BIP (or possibly in the future)? Does the vote only count if you win a block?

I also have an ASIC miner connected to a third party pool. Would I be able to "vote" with that miner? Or is my "vote" simply my choice to mine to that pool versus another?

**Tags:** miner-configuration, bip, bip9-version-bits


---

## 1 answers

### Answer by username_1 on 2024-03-03. Score: 1

The version and other parameters that could be used for signaling are generally set by the work producer, i.e. your own node or the pool you are mining with. That will issue the work for your mining hardware and include what block version to produce.

For your own pool or node, you would have to configure your pool or node software to produce work with your desired block version. It depends on the software - it may have some setting that you can set, or you may need to use a different version of the software itself.

If you mine with a third party pool, you'd generally have to switch to a different pool if you wanted to signal.

Note that it is not voting, but rather it is signaling readiness. The purpose is for miners to signal to every other node on the network that they are ready to enforce the new soft fork rules. Since the hashrate hardware is not receiving and validating new blocks and transactions, having it set the version (or other signaling mechanism) would not make sense. Thus the entity that is issuing the work needs to set the version as that entity should be receiving and validating new blocks and transactions, and can therefore make the decision about whether it is ready to enforce the new rules.

> Does the vote only count if you win a block?

Yes. The only way for other nodes on the network to know what you are signaling is by receiving a valid block from you. So you have to produce valid blocks to be counted.


---

