<p>Blocks signalling for the SegWit2x, i.e. the New York Agreement segwit activation (BIP91), are setting bit4. This shows up as a '1' in the second to last position of the version field. Blocks signalling readiness for BIP141, i.e. regular segwit activation, do so on bit1 which shows up as '2' in the last position of the version field. It is also possible to signal readiness for both:</p>

<pre><code>  20000010              20000002               20000012
        ↑                      ↑                     ↑↑
       bit4                   bit1                   bit4 and bit1
</code></pre>

<p><a href="https://xbt.eu" rel="nofollow noreferrer"><strong>xbt.eu</strong></a> is explicitly tracking the bit4 signalling already, but you can see the version field for blocks on most block explorers, and sites that track such information such as <a href="https://coin.dance" rel="nofollow noreferrer">coin.dance</a>.</p>

<p>Note: Bit 4 refers to <code>1&lt;&lt;4</code> and is thus the fifth bit from the back because the first is Bit 0. ;) </p>

CC BY-SA 3.0
2017-07-18T08:15:49.170Z
Why is bit 28 set to 1?
sanket1729
CC BY-SA 3.0
2017-07-18T14:45:48.130Z
@sanket1729: I've amended my answer to answer your question.
Murch
CC BY-SA 3.0
2017-07-19T03:10:48.137Z
I meant bit 28 in sense you were talking 1<<28. Referring to the 2 at the start of each number. **2**0000010. Or should this be asked as a new question?
sanket1729
CC BY-SA 3.0
2017-07-19T03:35:29.443Z
@sanket1729: Before BIP9, the version field was supposed to be linearly counted up for protocol upgrades. We got up to version 2. ;)
Murch
CC BY-SA 3.0
2017-07-19T07:29:15.553Z
Quick one; Is the % above based on (hash rate signalling)/(total current hash rate)?
Josh
CC BY-SA 3.0
2017-07-19T15:01:14.680Z
@Josh: Hash rate signalling is measured as `blocks signalling/total blocks`. I'm confused, though, in that my answer doesn't mention percentages.
Murch
CC BY-SA 3.0
2017-07-20T06:54:56.503Z
Thanks @Murch I get it. Sorry meant percentages on websites which would obviously be the ratio you just mentioned.
Josh
CC BY-SA 3.0
2017-07-21T15:50:19.427Z
Forgive my ignorance, but why does xbt.eu show BIP91 and NYA separately, if they are one and the same?
Robin
CC BY-SA 3.0
2017-07-21T16:20:00.953Z
@Robin: "NYA" was a string miners put into the coinbase transaction in order to communicate intent to support SegWit2x. BIP91 is an actual versionbits deployment of a softfork by setting a bit in the versionfield.
Murch
CC BY-SA 3.0
2017-07-21T16:37:18.067Z
@Murch Thank you! I think the way the data was presented on that site threw me a little, but with your explanation it makes complete sense now :)
Robin
CC BY-SA 3.0
2017-07-17T15:12:46.433Z
2017-07-19T03:37:01.053Z
2017-07-19T03:37:01.053Z
Murch
<p>You can see that information here (SegWit2x is BIP91): <a href="https://www.xbt.eu/" rel="nofollow noreferrer">https://www.xbt.eu/</a></p>

CC BY-SA 3.0
2017-07-17T14:02:17.077Z
2017-07-17T14:02:17.077Z
Paul
<p><a href="https://btc.com/" rel="nofollow noreferrer">BTC.com</a> will show you what miners are signalling for in their coinbase. In their <a href="https://btc.com/stats/pool" rel="nofollow noreferrer">pools page</a>, you can see recent blocks for each pool too, so that you can see when pools start/stop signalling for different proposals.</p>

CC BY-SA 3.0
2017-07-17T09:30:53.413Z
2017-07-17T09:30:53.413Z
alcio
<p>I found a live update here of miners signalling for SegWit2x. At time of writing Bitmain has just started signalling bringing SegWit2x at 64% support. (This is what was meant by signalling vs intent) </p>

<p><a href="http://www.coindesk.com/bitcoin-scaling-watch-news-guides-navigate-coming-clash-code/" rel="nofollow noreferrer">http://www.coindesk.com/bitcoin-scaling-watch-news-guides-navigate-coming-clash-code/</a></p>

CC BY-SA 3.0
2017-07-20T10:10:49.983Z
and here https://blockchain.info/charts/nya-support
Josh
CC BY-SA 3.0
2017-07-17T19:22:17.657Z
2017-07-17T19:22:17.657Z
Josh
<p>Hi I know you can view current miners signalling 'intent' to implement SegWit2x on coindance <a href="https://coin.dance/blocks" rel="noreferrer">https://coin.dance/blocks</a> . But is there a live website that show miners actually signalling SegWit2x? </p>

<segwit2x>
Where can you see current Bitcoin miners signalling SegWit2x?
Josh
# Where can you see current Bitcoin miners signalling SegWit2x?

(Asked by: username_0 on 2017-07-17)

Hi I know you can view current miners signalling 'intent' to implement SegWit2x on coindance <https://coin.dance/blocks> . But is there a live website that show miners actually signalling SegWit2x?

**Tags:** segwit2x


---

## 4 answers

### Answer by username_1 on 2017-07-17. Score: 8

Blocks signalling for the SegWit2x, i.e. the New York Agreement segwit activation (BIP91), are setting bit4. This shows up as a '1' in the second to last position of the version field. Blocks signalling readiness for BIP141, i.e. regular segwit activation, do so on bit1 which shows up as '2' in the last position of the version field. It is also possible to signal readiness for both:

```
  20000010              20000002               20000012
        ↑                      ↑                     ↑↑
       bit4                   bit1                   bit4 and bit1

```

[**xbt.eu**](https://xbt.eu) is explicitly tracking the bit4 signalling already, but you can see the version field for blocks on most block explorers, and sites that track such information such as [coin.dance](https://coin.dance).

Note: Bit 4 refers to `1<<4` and is thus the fifth bit from the back because the first is Bit 0. ;)

> **Comments:**
> **username_2**: Why is bit 28 set to 1?  
> **username_1**: @username_2: I've amended my answer to answer your question.  
> **username_2**: I meant bit 28 in sense you were talking 1<<28. Referring to the 2 at the start of each number. **2**0000010. Or should this be asked as a new question?  
> **username_1**: @username_2: Before BIP9, the version field was supposed to be linearly counted up for protocol upgrades. We got up to version 2. ;)  
> **username_0**: Quick one; Is the % above based on (hash rate signalling)/(total current hash rate)?  
> **username_1**: @username_0: Hash rate signalling is measured as `blocks signalling/total blocks`. I'm confused, though, in that my answer doesn't mention percentages.  
> **username_0**: Thanks @username_1 I get it. Sorry meant percentages on websites which would obviously be the ratio you just mentioned.  
> **username_3**: Forgive my ignorance, but why does xbt.eu show BIP91 and NYA separately, if they are one and the same?  
> **username_1**: @username_3: "NYA" was a string miners put into the coinbase transaction in order to communicate intent to support SegWit2x. BIP91 is an actual versionbits deployment of a softfork by setting a bit in the versionfield.  
> **username_3**: @username_1 Thank you! I think the way the data was presented on that site threw me a little, but with your explanation it makes complete sense now :)  

---

### Answer by username_4 on 2017-07-17. Score: 3

You can see that information here (SegWit2x is BIP91): <https://www.xbt.eu/>


---

### Answer by username_5 on 2017-07-17. Score: 1

[BTC.com](https://btc.com/) will show you what miners are signalling for in their coinbase. In their [pools page](https://btc.com/stats/pool), you can see recent blocks for each pool too, so that you can see when pools start/stop signalling for different proposals.


---

### Answer by username_0 on 2017-07-17. Score: 0

I found a live update here of miners signalling for SegWit2x. At time of writing Bitmain has just started signalling bringing SegWit2x at 64% support. (This is what was meant by signalling vs intent)

<http://www.coindesk.com/bitcoin-scaling-watch-news-guides-navigate-coming-clash-code/>

> **Comments:**
> **username_0**: and here https://blockchain.info/charts/nya-support  

---

