<pre><code>static const int32_t VERSIONBITS_LAST_OLD_BLOCK_VERSION = 4;
</code></pre>

<p>no need for change, for old blockchain need add in</p>

<pre><code>consensus.BIP65Height = 4; //  Block with what start bip if it's old block chain need add block 1,2,3 next block after block chain ( for people update before the this block can be mined. 
consensus.BIP66Height = 14; // this to, but + count off blocks in nMinerconfirmationwindow.

consensus.nRuleChangeActivationThreshold = 6; // 75% of 8064
consensus.nMinerConfirmationWindow = 8; // 
</code></pre>

<p>End bip's be activated after this count of block be mined.</p>

<p>end you cant answer this simple question ?</p>

CC BY-SA 3.0
2017-08-07T14:51:46.563Z
2017-08-08T22:51:21.557Z
2017-08-08T22:51:21.557Z
mraksoll
<pre><code>/** What block version to use for new blocks (pre versionbits) */
static const int32_t VERSIONBITS_LAST_OLD_BLOCK_VERSION = 4;
/** What bits to set in version for versionbits blocks */
static const int32_t VERSIONBITS_TOP_BITS = 0x20000000UL;
/** What bitmask determines whether versionbits is in use */
static const int32_t VERSIONBITS_TOP_MASK = 0xE0000000UL;
/** Total bits available for versionbits */
static const int32_t VERSIONBITS_NUM_BITS = 29;
</code></pre>

<p>bip's 65 end 66 are on 3 end 4 version block's. But blockchain latest block is 2 version. What value i need put on this for upgrade when new block's be mined to ver 3 end 4.</p>

<p>or i need change the bip 65 end 66 to the same block ver4, end put value prev block to 2 ? How it do correctly</p>

CC BY-SA 3.0
2017-08-06T13:19:37.807Z
uh, four downvotes without explanation... could someone explain? I see that tseries is new here, trying to read and understand the code, and get involved, shouldn't this merit some understanding? Even if english seems not to be native language (same with me). @tseries: I feel the question is not precise enough, so people find it difficult to help out. You might explain a bit more, what you intend to do. BIP66 is "Strict DER signatures" and BIP65 is "OP_CHECKLOCKTIMEVERIFY" - at least for bitcoin world... difficult to see, how this relates to blockchain version code you mention.
pebwindkraft
CC BY-SA 3.0
2017-08-07T06:38:31.827Z
The downvotes are likely because the question is unclear as to what the question actually is.
Ava Chow
<blockchain><block><altcoin-development><bip>
what this parameters do end what i need put on them in blockchain ver2
tseries
# what this parameters do end what i need put on them in blockchain ver2

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

```
/** What block version to use for new blocks (pre versionbits) */
static const int32_t VERSIONBITS_LAST_OLD_BLOCK_VERSION = 4;
/** What bits to set in version for versionbits blocks */
static const int32_t VERSIONBITS_TOP_BITS = 0x20000000UL;
/** What bitmask determines whether versionbits is in use */
static const int32_t VERSIONBITS_TOP_MASK = 0xE0000000UL;
/** Total bits available for versionbits */
static const int32_t VERSIONBITS_NUM_BITS = 29;

```

bip's 65 end 66 are on 3 end 4 version block's. But blockchain latest block is 2 version. What value i need put on this for upgrade when new block's be mined to ver 3 end 4.

or i need change the bip 65 end 66 to the same block ver4, end put value prev block to 2 ? How it do correctly

**Tags:** blockchain, block, altcoin-development, bip

> **Comments:**
> **username_1**: uh, four downvotes without explanation... could someone explain? I see that username_0 is new here, trying to read and understand the code, and get involved, shouldn't this merit some understanding? Even if english seems not to be native language (same with me). @username_0: I feel the question is not precise enough, so people find it difficult to help out. You might explain a bit more, what you intend to do. BIP66 is "Strict DER signatures" and BIP65 is "OP_CHECKLOCKTIMEVERIFY" - at least for bitcoin world... difficult to see, how this relates to blockchain version code you mention.  
> **username_2**: The downvotes are likely because the question is unclear as to what the question actually is.  

---

## 1 answers

### Answer by username_3 on 2017-08-07. Score: 0

```
static const int32_t VERSIONBITS_LAST_OLD_BLOCK_VERSION = 4;

```

no need for change, for old blockchain need add in

```
consensus.BIP65Height = 4; //  Block with what start bip if it's old block chain need add block 1,2,3 next block after block chain ( for people update before the this block can be mined. 
consensus.BIP66Height = 14; // this to, but + count off blocks in nMinerconfirmationwindow.

consensus.nRuleChangeActivationThreshold = 6; // 75% of 8064
consensus.nMinerConfirmationWindow = 8; // 

```

End bip's be activated after this count of block be mined.

end you cant answer this simple question ?


---

