<p><a href="https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#Deployment" rel="nofollow noreferrer">BIP141 – Deployment</a> says:</p>
<blockquote>
<p>This BIP will be deployed by &quot;version bits&quot; BIP9 with the name &quot;segwit&quot; and using bit 1.</p>
<p>For Bitcoin mainnet, the BIP9 <code>starttime</code> will be midnight 15 november 2016 UTC (Epoch timestamp 1479168000) and BIP9 timeout will be midnight 15 november 2017 UTC (Epoch timestamp 1510704000).</p>
</blockquote>
<p>As we're currently on the second version of blocks, the version field will be showing <code>0x20000002</code> when signaling readiness for segwit and <code>0x20000000</code> when not. Readiness for segwit2x would show as <code>0x20000010</code> if only signaling bit 4 or <code>0x20000012</code> if signaling both bit 1 and bit 4.</p>
<p>BIP 9 requires 95% readiness signaled over one difficulty period (from reset to reset). Once that is achieved, SegWit will be activated on the network after the following difficulty period has passed.</p>
<p>It appears that <a href="https://coin.dance/blocks/proposals" rel="nofollow noreferrer">Coin.Dance</a> will show support in the linked graph, as indicated by the footnote &quot;BIP 141 (voting starts on 2016-11-15)&quot;.</p>
<p><em>Note: In BIP9 signaling readiness only starts with the first difficulty retarget after the <code>starttime</code>. In the case of SegWit this is likely to be around the 19th of November.</em></p>

CC BY-SA 3.0
2017-07-07T18:09:54.860Z
So the version would be 0x20000002 if showing support and 0x20000000 if not?
Albert S
CC BY-SA 3.0
2017-07-07T19:23:05.240Z
@Alberts: I've updated my answer.
Murch
CC BY-SA 3.0
2016-11-15T13:22:33.953Z
I assume (since I do not see it yet), that the black BIP 141 line will only be visible after the next retarget?
Janus Troelsen
CC BY-SA 3.0
2016-11-15T13:27:14.687Z
@JanusTroelsen: Signaling only starts after the retarget, so before then the line will be at 0%. I don't have any information on what coin.dance will do regarding the line. :)
Murch
CC BY-SA 3.0
2016-10-28T17:01:36.463Z
2017-07-07T19:22:56.483Z
2020-06-16T11:10:03.350Z
Murch
<p>Ideally, I'd also like to see graphs that indicate how close we are to segwit adoption and the number of minimum blocks we are away from actual segwit adoption.</p>

<blockchain><block><segregated-witness><activation-mechanism><bip9-version-bits>
How do blocks signal whether it supports segwit for the 95% threshold?
Jimmy Song
# How do blocks signal whether it supports segwit for the 95% threshold?

(Asked by: username_0 on 2016-10-28)

Ideally, I'd also like to see graphs that indicate how close we are to segwit adoption and the number of minimum blocks we are away from actual segwit adoption.

**Tags:** blockchain, block, segregated-witness, activation-mechanism, bip9-version-bits


---

## 1 answers

### Answer by username_1 on 2016-10-28. Score: 3 | Accepted answer

[BIP141 – Deployment](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#Deployment) says:

> This BIP will be deployed by "version bits" BIP9 with the name "segwit" and using bit 1.
>
> For Bitcoin mainnet, the BIP9 `starttime` will be midnight 15 november 2016 UTC (Epoch timestamp 1479168000) and BIP9 timeout will be midnight 15 november 2017 UTC (Epoch timestamp 1510704000).

As we're currently on the second version of blocks, the version field will be showing `0x20000002` when signaling readiness for segwit and `0x20000000` when not. Readiness for segwit2x would show as `0x20000010` if only signaling bit 4 or `0x20000012` if signaling both bit 1 and bit 4.

BIP 9 requires 95% readiness signaled over one difficulty period (from reset to reset). Once that is achieved, SegWit will be activated on the network after the following difficulty period has passed.

It appears that [Coin.Dance](https://coin.dance/blocks/proposals) will show support in the linked graph, as indicated by the footnote "BIP 141 (voting starts on 2016-11-15)".

*Note: In BIP9 signaling readiness only starts with the first difficulty retarget after the `starttime`. In the case of SegWit this is likely to be around the 19th of November.*

> **Comments:**
> **username_3**: I assume (since I do not see it yet), that the black BIP 141 line will only be visible after the next retarget?  
> **username_1**: @username_3: Signaling only starts after the retarget, so before then the line will be at 0%. I don't have any information on what coin.dance will do regarding the line. :)  
> **username_2**: So the version would be 0x20000002 if showing support and 0x20000000 if not?  
> **username_1**: @Alberts: I've updated my answer.  

---

