<p>The answer is pretty boring. Nobody did the work to implement it (yet).</p>

CC BY-SA 3.0
2017-01-31T21:12:34.573Z
Works for me :-)
https://github.com/bitcoin/bitcoin/pull/9571
pinhead
CC BY-SA 3.0
2017-01-11T05:11:08.483Z
2017-01-11T05:11:08.483Z
Pieter Wuille
<p>An example of the output of <code>getblockchaininfo</code> is here:</p>

<p><a href="https://chainquery.com/bitcoin-api/getblockchaininfo" rel="nofollow noreferrer">https://chainquery.com/bitcoin-api/getblockchaininfo</a></p>

<p>The <code>softforks</code> field describes the number of required / found blocks signaling the soft fork, but the <code>bip9_softforks</code> field does not. It just indicates a generic status message ("defined", "started", "locked_in", "active", "failed").</p>

<p>Is there an RPC command that will return the number of SegWit blocks?</p>

<bitcoin-core><json-rpc><segregated-witness><bip9-version-bits>
Why doesn't getblockchaininfo reveal BIP9 signaling statistics?
pinhead
# Why doesn't getblockchaininfo reveal BIP9 signaling statistics?

(Asked by: username_0 on 2017-01-06)

An example of the output of `getblockchaininfo` is here:

<https://chainquery.com/bitcoin-api/getblockchaininfo>

The `softforks` field describes the number of required / found blocks signaling the soft fork, but the `bip9_softforks` field does not. It just indicates a generic status message ("defined", "started", "locked\_in", "active", "failed").

Is there an RPC command that will return the number of SegWit blocks?

**Tags:** bitcoin-core, json-rpc, segregated-witness, bip9-version-bits


---

## 1 answers

### Answer by username_1 on 2017-01-11. Score: 1

The answer is pretty boring. Nobody did the work to implement it (yet).

> **Comments:**
> **username_0**: Works for me :-) https://github.com/bitcoin/bitcoin/pull/9571  

---

