<p>Those parameters are for BIP 9 soft fork deployments. For a BIP 9 soft fork with these deployment parameters, the fork will transition from the <code>STARTED</code> state to <code>LOCKED_IN</code> when 6 blocks (<code>nRuleChangeActivationThreshold</code>) out of an 8 block non-overlapping window (<code>nMinerCOnfirmationWindow</code>) signal for that soft fork.</p>

<p>These values are not necessary for normal operation. They are only used for soft forks, so unless you are deploying soft forks, these values don't matter at all.</p>

<blockquote>
  <p>Is this value attached to the nPowTargetTimespan / nPowTargetSpacing * 4</p>
</blockquote>

<p>No, it is not. There is no relation between these parameters at all.</p>

CC BY-SA 3.0
2017-08-11T18:38:29.680Z
2017-08-11T18:47:05.987Z
2017-08-11T18:47:05.987Z
Ava Chow
<pre><code>consensus.nRuleChangeActivationThreshold = 6; // 75% of 6
consensus.nMinerConfirmationWindow = 8; // nPowTargetTimespan / nPowTargetSpacing * 4
</code></pre>

<ol>
<li>For what this rule exit ? How to calculate this rule for find valid </li>
<li>value for altcoin.</li>
<li>What can be happen if it's value to low or to high ?</li>
</ol>

<p>Is this value attached to the nPowTargetTimespan / nPowTargetSpacing * 4</p>

<p>Or is it completely unrelated to them?</p>

<blockchain><development><altcoin-development><consensus>
What this param in chainparams.cpp do?
mraksoll
# What this param in chainparams.cpp do?

(Asked by: username_0 on 2017-08-11)

```
consensus.nRuleChangeActivationThreshold = 6; // 75% of 6
consensus.nMinerConfirmationWindow = 8; // nPowTargetTimespan / nPowTargetSpacing * 4

```

1. For what this rule exit ? How to calculate this rule for find valid
2. value for altcoin.
3. What can be happen if it's value to low or to high ?

Is this value attached to the nPowTargetTimespan / nPowTargetSpacing \* 4

Or is it completely unrelated to them?

**Tags:** blockchain, development, altcoin-development, consensus


---

## 1 answers

### Answer by username_1 on 2017-08-11. Score: 1 | Accepted answer

Those parameters are for BIP 9 soft fork deployments. For a BIP 9 soft fork with these deployment parameters, the fork will transition from the `STARTED` state to `LOCKED_IN` when 6 blocks (`nRuleChangeActivationThreshold`) out of an 8 block non-overlapping window (`nMinerCOnfirmationWindow`) signal for that soft fork.

These values are not necessary for normal operation. They are only used for soft forks, so unless you are deploying soft forks, these values don't matter at all.

> Is this value attached to the nPowTargetTimespan / nPowTargetSpacing \* 4

No, it is not. There is no relation between these parameters at all.


---

