<p>This is in addition to Dan K's answer. Since he wrote it there is a new field:</p>

<p>relayfee: The relay fee is also the transaction fee, but it refers to a different use than what you may know. A transaction fee is included with a transaction to encourage and reward miners for including the transaction in the blockchain. It refers to the minimum fee amount that other clients on the peer-to-peer network require in order to forward transactions to other peers. This fee is in place in order to prevent the broadcast and propogation of DDoS-like spam transactions. The relay fee is coded in a different place than the transaction fee in Bitcoin. In the past, it has also been set at a different amount than the transaction fee. For a good portion of recent Bitcoin history, the minimum transaction fee used by the Bitcoin client and by most miners was 0.0005 BTC per kB, but the minimum relay fee was coded at 0.0001 BTC. The transaction fee was then lowered, bringing them in sync.</p>

CC BY-SA 3.0
2015-08-12T13:45:16.117Z
Drew, thanks for your answer, and welcome to the bitcoin stack exchange. Since your answer isn't a full answer by itself, I would suggest you use the edit button on the accepted answer to suggest an edit. Since you are a new user, someone will review your changes before they are accepted.
morsecoder
CC BY-SA 3.0
2015-08-12T13:46:55.297Z
`unlocked_until` is a new getinfo field, as well.
morsecoder
CC BY-SA 3.0
2015-08-12T07:46:17.960Z
2015-08-12T07:46:17.960Z
Drew
<p>An explanation of the meaning of the fields given by 'getinfo' :</p>

<p>version - The version number of this bitcoin-qt or bitcoind program itself. Both of are equivalent. -qt is simply the graphical user interface version</p>

<p>protocolversion: The version of the bitcoin network protocol supported by this client (user agent software).</p>

<p>walletversion: The version of the wallet.dat file. Wallet.dat contains bitcoin addresses and public &amp; private key pairs for these addresses. There is additional data on the wallet. Care must be taken to not restore from an old wallet backup. New addresses generated in the wallet since the old backup was made will not exist in the old backup! Source: <a href="https://en.bitcoin.it/wiki/Wallet">https://en.bitcoin.it/wiki/Wallet</a></p>

<p>balance: The total number of bitcoins held in the wallet.dat file.</p>

<p>blocks: The total number of blocks which constitute the shared block chain.</p>

<p>timeoffset: Seconds of difference between this node's "wall clock time" and the median reported by our network peers.</p>

<p>connections: the number of peers on the bitcoin P2P network that this node is connected to.</p>

<p>proxy: If using a proxy to connect to the network, listed here, otherwise blank.</p>

<p>difficulty: the current mining difficulty factor. Difficulty is increased as more miners and more hash compute power compete to be the next one to have a block of transactions added to the blockchain.</p>

<p>testnet: Boolean value (true OR false). There is a parallel bitcoin network, the testnet, where trials and experiments may be carried out without impacting the official, live bitcoin P2P network</p>

<p>keypoololdest: timestamp (UNIX epoch) of the oldest key in the keypool</p>

<p>keypoolsize: A number of addresses are kept in reserve by the client. This is the size of that reserve.</p>

<p>paytxfee: Specifies what fee the client is willing to pay to expedite transactions. Miners may choose to ignore transactions that do not pay a fee, and these fee-less transactions will have low priority on queue of pending transaction and may linger there for hours.</p>

<p>errors: This field may inform of different status conditions. Full list of error codes in source file bitcoinrpc.h (<a href="https://dev.visucore.com/bitcoin/doxygen/bitcoinrpc_8h_source.html">https://dev.visucore.com/bitcoin/doxygen/bitcoinrpc_8h_source.html</a>) (Examples: "Bitcoin not connected", "database error", "Keypool ran out"...) </p>

CC BY-SA 3.0
2013-12-05T18:27:42.587Z
2013-12-05T18:27:42.587Z
Dan K
<p>I am trying to get my foot in the door wrt to bitcoind. I pulled the github version <a href="https://github.com/bitcoin/bitcoin" rel="nofollow noreferrer">here</a>. As suggested <a href="https://bitcoin.stackexchange.com/a/18024/10137">here</a>, I am starting the daemon like so</p>

<pre><code>bitcoind -daemon
</code></pre>

<p>and I am monitoring it like so</p>

<pre><code>bitcoind getinfo
</code></pre>

<p>And I get the following output</p>

<pre><code>{
    "version" : 89900,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 269516,
    "timeoffset" : -2,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 510929738.01615179,
    "testnet" : false,
    "keypoololdest" : 1386220819,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"
}
</code></pre>

<p>Obviously some are self explanatory, but could someone go through and explain what all of this output means?</p>

CC BY-SA 3.0
2013-12-05T10:18:37.657Z
Also could someone add some tags, I really don't know what to add besides `bitcoin` =P
puk
<bitcoind><daemon>
What does getinfo output mean?
puk
# What does getinfo output mean?

(Asked by: username_0 on 2013-12-05)

I am trying to get my foot in the door wrt to bitcoind. I pulled the github version [here](https://github.com/bitcoin/bitcoin). As suggested [here](https://bitcoin.stackexchange.com/a/18024/10137), I am starting the daemon like so

```
bitcoind -daemon

```

and I am monitoring it like so

```
bitcoind getinfo

```

And I get the following output

```
{
    "version" : 89900,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 269516,
    "timeoffset" : -2,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 510929738.01615179,
    "testnet" : false,
    "keypoololdest" : 1386220819,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"
}

```

Obviously some are self explanatory, but could someone go through and explain what all of this output means?

**Tags:** bitcoind, daemon

> **Comments:**
> **username_0**: Also could someone add some tags, I really don't know what to add besides `bitcoin` =P  

---

## 2 answers

### Answer by username_3 on 2013-12-05. Score: 11 | Accepted answer

An explanation of the meaning of the fields given by 'getinfo' :

version - The version number of this bitcoin-qt or bitcoind program itself. Both of are equivalent. -qt is simply the graphical user interface version

protocolversion: The version of the bitcoin network protocol supported by this client (user agent software).

walletversion: The version of the wallet.dat file. Wallet.dat contains bitcoin addresses and public & private key pairs for these addresses. There is additional data on the wallet. Care must be taken to not restore from an old wallet backup. New addresses generated in the wallet since the old backup was made will not exist in the old backup! Source: <https://en.bitcoin.it/wiki/Wallet>

balance: The total number of bitcoins held in the wallet.dat file.

blocks: The total number of blocks which constitute the shared block chain.

timeoffset: Seconds of difference between this node's "wall clock time" and the median reported by our network peers.

connections: the number of peers on the bitcoin P2P network that this node is connected to.

proxy: If using a proxy to connect to the network, listed here, otherwise blank.

difficulty: the current mining difficulty factor. Difficulty is increased as more miners and more hash compute power compete to be the next one to have a block of transactions added to the blockchain.

testnet: Boolean value (true OR false). There is a parallel bitcoin network, the testnet, where trials and experiments may be carried out without impacting the official, live bitcoin P2P network

keypoololdest: timestamp (UNIX epoch) of the oldest key in the keypool

keypoolsize: A number of addresses are kept in reserve by the client. This is the size of that reserve.

paytxfee: Specifies what fee the client is willing to pay to expedite transactions. Miners may choose to ignore transactions that do not pay a fee, and these fee-less transactions will have low priority on queue of pending transaction and may linger there for hours.

errors: This field may inform of different status conditions. Full list of error codes in source file bitcoinrpc.h (<https://dev.visucore.com/bitcoin/doxygen/bitcoinrpc_8h_source.html>) (Examples: "Bitcoin not connected", "database error", "Keypool ran out"...)


---

### Answer by username_1 on 2015-08-12. Score: 0

This is in addition to username_3's answer. Since he wrote it there is a new field:

relayfee: The relay fee is also the transaction fee, but it refers to a different use than what you may know. A transaction fee is included with a transaction to encourage and reward miners for including the transaction in the blockchain. It refers to the minimum fee amount that other clients on the peer-to-peer network require in order to forward transactions to other peers. This fee is in place in order to prevent the broadcast and propogation of DDoS-like spam transactions. The relay fee is coded in a different place than the transaction fee in Bitcoin. In the past, it has also been set at a different amount than the transaction fee. For a good portion of recent Bitcoin history, the minimum transaction fee used by the Bitcoin client and by most miners was 0.0005 BTC per kB, but the minimum relay fee was coded at 0.0001 BTC. The transaction fee was then lowered, bringing them in sync.

> **Comments:**
> **username_2**: username_1, thanks for your answer, and welcome to the bitcoin stack exchange. Since your answer isn't a full answer by itself, I would suggest you use the edit button on the accepted answer to suggest an edit. Since you are a new user, someone will review your changes before they are accepted.  
> **username_2**: `unlocked_until` is a new getinfo field, as well.  

---

