<p>You can use the <code>jq</code> shell command to filter out the unwanted keys.</p>

<p><code>
$ ./bitcoin-cli getblockchaininfo | jq 'del (.softforks)' | jq 'del (.bip9_softforks)'
</code></p>

<p>with as output:</p>

<pre><code>{
  "chain": "main",
  "blocks": 485623,
  "headers": 485623,
  "bestblockhash": "000000000000000000772fa60c075c57b8ba2db277a84454e1f8e27c3c307b10",
  "difficulty": 922724699725.9628,
  "mediantime": 1505593445,
  "verificationprogress": 0.9999959396017668,
  "chainwork": "0000000000000000000000000000000000000000008aeb8bb8310a6b50e24bb0",
  "pruned": false
}
</code></pre>

CC BY-SA 3.0
2017-09-16T20:56:48.730Z
2017-09-16T20:56:48.730Z
Pieter Wuille
<p>The blockchaininfo command is now returning a lot of "softfork" information.</p>

<p>Is there a way I can get other fields without the softfork blob?</p>

CC BY-SA 3.0
2017-08-15T04:07:08.800Z
Don't look at them? Or if you're using `bitcoin-cli`, use `jq` or even `grep` to filter them out?
Pieter Wuille
CC BY-SA 3.0
2017-08-15T12:07:45.013Z
@PieterWuille You know, Pieter, blockchaininfo is a very commonly used command. It makes sense to return a single screen of the most useful information. For most users, the key thing is to make sure that they are synced, which means comparing the block count to the headers. Scrolling this critical information off the screen with a lot of softfork verbiage is a nuisance. There should either be a switch to remove that information altogether or at least it should be distilled to a synopsis so that the printout stays on one page.
Harry Pillsbury
CC BY-SA 3.0
2017-08-15T17:15:08.450Z
RPC calls are more intended to be machine readable than human readable.
Pieter Wuille
<bitcoin-core><client>
getblockchaininfo returning excessive "soft fork" info
Harry Pillsbury
# getblockchaininfo returning excessive "soft fork" info

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

The blockchaininfo command is now returning a lot of "softfork" information.

Is there a way I can get other fields without the softfork blob?

**Tags:** bitcoin-core, client

> **Comments:**
> **username_1**: Don't look at them? Or if you're using `bitcoin-cli`, use `jq` or even `grep` to filter them out?  
> **username_0**: @username_1 You know, username_1, blockchaininfo is a very commonly used command. It makes sense to return a single screen of the most useful information. For most users, the key thing is to make sure that they are synced, which means comparing the block count to the headers. Scrolling this critical information off the screen with a lot of softfork verbiage is a nuisance. There should either be a switch to remove that information altogether or at least it should be distilled to a synopsis so that the printout stays on one page.  
> **username_1**: RPC calls are more intended to be machine readable than human readable.  

---

## 1 answers

### Answer by username_1 on 2017-09-16. Score: 1

You can use the `jq` shell command to filter out the unwanted keys.

`$ ./bitcoin-cli getblockchaininfo | jq 'del (.softforks)' | jq 'del (.bip9_softforks)'`

with as output:

```
{
  "chain": "main",
  "blocks": 485623,
  "headers": 485623,
  "bestblockhash": "000000000000000000772fa60c075c57b8ba2db277a84454e1f8e27c3c307b10",
  "difficulty": 922724699725.9628,
  "mediantime": 1505593445,
  "verificationprogress": 0.9999959396017668,
  "chainwork": "0000000000000000000000000000000000000000008aeb8bb8310a6b50e24bb0",
  "pruned": false
}

```


---

