<p>In the <a href="https://bitcoin.stackexchange.com/questions/35938/where-does-multibit-keep-its-data-directory">Multibit data directory</a>, there is a file called <code>log/multibit.log</code>. When you connect to a peer, it will write something like this to the log:</p>

<pre><code>20:01:26.124 [bitcoinj user thread] DEBUG o.m.c.b.BitcoinPeerEventListener - Connected to peer:
client version: 70002
local services: 1
time:           1424228484
my addr:        [xx.xx.xx.xx]:51127
their addr:     [xx.xx.xx.xx]:8333
sub version:    /Satoshi:0.10.0/
best height:    343977
delay tx relay: true
</code></pre>

<p>The 'sub version' field contains the version in a human readable format. The 'client version' field contains a machine-readable protocol version.</p>

CC BY-SA 3.0
2015-02-19T01:58:10.123Z
Perfect thanks Nick! I appreciate the link to finding the Multibit data directory as well.  So bounus question, I see my wallet last used Satoshi:0.9.2.1, but I see it skips around, what determines which version it uses?
Jonathan Chad Faling
CC BY-SA 3.0
2015-02-19T02:17:04.320Z
@JonathanChadFaling It connects to nodes owned by other people, so it's whatever they decide to run.
Nick ODell
CC BY-SA 3.0
2015-07-04T15:24:33.630Z
This is not entirely true. Looking at https://blockchain.info/connected-nodes, lots of nodes have same 'client version' but vastly differently 'sub versions'.
Jus12
CC BY-SA 3.0
2015-07-04T15:54:15.217Z
@Jus12 It's because the protocol version and the client version are different.
Nick ODell
CC BY-SA 3.0
2015-02-18T03:10:37.523Z
2015-09-11T01:43:10.503Z
2017-04-13T12:47:32.940Z
Nick ODell
<p>On Bitcoin Core go to Windows &gt; Console (CTRL+T).
Then, type:</p>
<pre><code>getwalletinfo
</code></pre>
<p>Should show you a json with the wallet version.
Not sure if multibit software has that option thought.</p>

CC BY-SA 4.0
2021-01-26T17:49:03.800Z
2021-01-26T17:49:03.800Z
Lucas Serafim
<p>You can find this out on the command line with:</p>

<pre><code>$ bitcoin-cli getinfo
</code></pre>

<p>This will give you an output like this:</p>

<pre><code>{   
    "version" : 90400,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.62950000,
    "blocks" : 323377,
    "timeoffset" : -5,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : 1.00000000,
    "testnet" : true,
    "keypoololdest" : 1412131069,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}
</code></pre>

<p>Version is the actual bitcoin core version and probably what you're looking for.</p>

CC BY-SA 3.0
2015-02-18T03:04:38.717Z
This appears to get the version of a local bitcoind instance. I don't think that's what the asker is asking about.
Nick ODell
CC BY-SA 3.0
2015-02-18T03:05:17.060Z
Gah, you're right
Jimmy Song
CC BY-SA 3.0
2015-02-18T02:30:55.110Z
2015-02-18T02:30:55.110Z
Jimmy Song
<p>I use the multibit wallet which I understand doesn't download the whole bitcoin core i.e. the entire block chain, but it must use the bitcoin core protocol right? So how do I see which version of the protocol my wallet is using? </p>

<client><multibit><bitcoin-core-development>
How do I see what version of bitcoin core my wallet uses
Jonathan Chad Faling
# How do I see what version of bitcoin core my wallet uses

(Asked by: username_0 on 2015-02-17)

I use the multibit wallet which I understand doesn't download the whole bitcoin core i.e. the entire block chain, but it must use the bitcoin core protocol right? So how do I see which version of the protocol my wallet is using?

**Tags:** client, multibit, bitcoin-core-development


---

## 3 answers

### Answer by username_1 on 2015-02-18. Score: 1 | Accepted answer

In the [Multibit data directory](https://bitcoin.stackexchange.com/questions/35938/where-does-multibit-keep-its-data-directory), there is a file called `log/multibit.log`. When you connect to a peer, it will write something like this to the log:

```
20:01:26.124 [bitcoinj user thread] DEBUG o.m.c.b.BitcoinPeerEventListener - Connected to peer:
client version: 70002
local services: 1
time:           1424228484
my addr:        [xx.xx.xx.xx]:51127
their addr:     [xx.xx.xx.xx]:8333
sub version:    /Satoshi:0.10.0/
best height:    343977
delay tx relay: true

```

The 'sub version' field contains the version in a human readable format. The 'client version' field contains a machine-readable protocol version.

> **Comments:**
> **username_0**: Perfect thanks username_1! I appreciate the link to finding the Multibit data directory as well.  So bounus question, I see my wallet last used Satoshi:0.9.2.1, but I see it skips around, what determines which version it uses?  
> **username_1**: @username_0 It connects to nodes owned by other people, so it's whatever they decide to run.  
> **username_2**: This is not entirely true. Looking at https://blockchain.info/connected-nodes, lots of nodes have same 'client version' but vastly differently 'sub versions'.  
> **username_1**: @username_2 It's because the protocol version and the client version are different.  

---

### Answer by username_3 on 2021-01-26. Score: 0

On Bitcoin Core go to Windows > Console (CTRL+T).
Then, type:

```
getwalletinfo

```

Should show you a json with the wallet version.
Not sure if multibit software has that option thought.


---

### Answer by username_4 on 2015-02-18. Score: -2

You can find this out on the command line with:

```
$ bitcoin-cli getinfo

```

This will give you an output like this:

```
{   
    "version" : 90400,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.62950000,
    "blocks" : 323377,
    "timeoffset" : -5,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : 1.00000000,
    "testnet" : true,
    "keypoololdest" : 1412131069,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}

```

Version is the actual bitcoin core version and probably what you're looking for.

> **Comments:**
> **username_1**: This appears to get the version of a local bitcoind instance. I don't think that's what the asker is asking about.  
> **username_4**: Gah, you're right  

---

