<h2>What's the meaning of the score in <code>getnetworkinfo</code>?</h2>

<p>When you look up <code>getnetworkinfo</code> in the Bitcoin <a href="https://bitcoin.org/en/developer-reference#getnetworkinfo" rel="nofollow noreferrer">Developer Reference</a>, it says about <code>score</code>: </p>

<blockquote>
  <p>The number of incoming connections during the uptime of this node that have used this address in their <code>version</code> message</p>
</blockquote>

<p>If I understand that correctly, this means that the score is the number of times <em>incoming</em> connections have been established with your node since it started. </p>

<h2>Network services and pruning</h2>

<p>Nodes on the network announce the services they offer by setting their network services flags. </p>

<p>There are currently five flags in use:</p>

<ul>
<li><code>NODE_NETWORK (1)</code></li>
<li><code>NODE_GETUTXOS (2)</code></li>
<li><code>NODE_BLOOM (4)</code></li>
<li><code>NODE_WITNESS (8)</code></li>
<li><code>NODE_XTHIN (16)</code></li>
</ul>

<p>Out of these, <code>NODE_NETWORK</code> indicates that your node will serve historical blocks. Currently there is no way to announce that you can only serve a subset of all blocks, so just like nodes that cannot serve blocks at all, pruning nodes don't advertise <code>NODE_NETWORK</code>.</p>

<h2>Pruning nodes don't get referred by DNS seeders</h2>

<p>This has a direct effect on the number of incoming connections pruning nodes get, as DNS seeders only refer nodes that advertise <code>NODE_NETWORK</code> when new nodes request additional peers to connect to. This means that pruning nodes only get incoming connections when they are referred by non-DNS seeder nodes.</p>

CC BY-SA 3.0
2017-05-21T18:36:22.000Z
2017-05-22T02:26:12.290Z
2017-05-22T02:26:12.290Z
Murch
<p>My node's network score (revealed by <code>getnetworkinfo</code>) is very low (&lt;75). Most of the time there are no peers with incoming connections connected to the node. Is this because I'm running a pruned node? Would that reduce the network score?</p>

<full-node><connection><pruning>
Does having a pruned node reduce its network score?
Geremia
# Does having a pruned node reduce its network score?

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

My node's network score (revealed by `getnetworkinfo`) is very low (<75). Most of the time there are no peers with incoming connections connected to the node. Is this because I'm running a pruned node? Would that reduce the network score?

**Tags:** full-node, connection, pruning


---

## 1 answers

### Answer by username_1 on 2017-05-21. Score: 3 | Accepted answer

## What's the meaning of the score in `getnetworkinfo`?

When you look up `getnetworkinfo` in the Bitcoin [Developer Reference](https://bitcoin.org/en/developer-reference#getnetworkinfo), it says about `score`:

> The number of incoming connections during the uptime of this node that have used this address in their `version` message

If I understand that correctly, this means that the score is the number of times *incoming* connections have been established with your node since it started.

## Network services and pruning

Nodes on the network announce the services they offer by setting their network services flags.

There are currently five flags in use:

* `NODE_NETWORK (1)`
* `NODE_GETUTXOS (2)`
* `NODE_BLOOM (4)`
* `NODE_WITNESS (8)`
* `NODE_XTHIN (16)`

Out of these, `NODE_NETWORK` indicates that your node will serve historical blocks. Currently there is no way to announce that you can only serve a subset of all blocks, so just like nodes that cannot serve blocks at all, pruning nodes don't advertise `NODE_NETWORK`.

## Pruning nodes don't get referred by DNS seeders

This has a direct effect on the number of incoming connections pruning nodes get, as DNS seeders only refer nodes that advertise `NODE_NETWORK` when new nodes request additional peers to connect to. This means that pruning nodes only get incoming connections when they are referred by non-DNS seeder nodes.


---

