There is a generation of softforks used the block header’s nVersion field for signalling (up to the year 2015). Each of those used a subsequent version numbers (BIP34 used version 2; BIP66 used version 3; BIP65 used version 4).
Whenever 750 out blocks number N-1000..N-1 (so 75%) had the proposal’s version number of higher, block N would be subject to the proposal’s rules. Whenever 950 out of blocks number N-1000..N-1 (so 95%) did, the next block would be required to also signal for it – resulting in a final lock-in.
I want to build a simple bitcoin version for myself and want to sign another version for the block that I mine. In the past what the developer had to do was changing the CURRENT_VERSION of block into a new number (like BIP34: https://github.com/bitcoin/bitcoin/pull/1526).
But the code base has changed now so I’m not sure what I need to do if I want the same thing, can anybody tell me what to do? I think I need to change VERSIONBITS_TOP_BITS into a new number but I believe that may be not the correct way.