<p>It is possible to configure your server/clients as follows, although it is not exactly what you have described. I presume that you still want each client to have its own separate wallet.</p>

<ol>
<li>On your server, make a full installation of Bitcoin Core.

<ol>
<li>In the config file set <code>bind=&lt;internal network IP&gt;</code>.</li>
<li>Set any other options, for example to enable incoming peers from the internet.</li>
<li>Restart server node for config to take effect.</li>
</ol></li>
<li>On each client make a full installation of Bitcoin Core.

<ol>
<li>In your config file set <code>connect=&lt;server IP&gt;</code>.</li>
<li>In your config file set <code>prune=&lt;n&gt;</code> where n is greater than 550MiB. This will limit storage requirements.</li>
<li>Set any other options.</li>
<li>Restart client node for config to take effect.</li>
</ol></li>
</ol>

<p>Using <code>connect=</code> disables automatic connections so, your nodes will only connect to the server.</p>

CC BY-SA 4.0
2018-05-19T00:14:17.757Z
2018-05-19T00:14:17.757Z
Willtech
<p>This is not supported.</p>

<p>What is supported:</p>

<ul>
<li>Run Bitcoin Core in pruning mode (which means it still has a local blockchain, but only recent blocks are kept.</li>
<li>Run lightweight software as client, and make it only connect to your (clearly trusted) server. This way you get a fully validated chain, without the resource usage.</li>
</ul>

CC BY-SA 3.0
2017-08-09T00:50:46.860Z
2017-08-09T00:50:46.860Z
Pieter Wuille
<p>You could try <a href="https://bitcore.io/" rel="nofollow noreferrer">Bitcore</a> instead. It contains a fork of the reference bitcoin implementation with added support for indexing of data, and includes an API for running it on a server. You can then use the API from your local computers or access the built-in blockchain explorer.</p>

CC BY-SA 3.0
2017-11-07T02:59:30.140Z
2017-11-07T02:59:30.140Z
Adam Millerchip
<p><strong>How to store full blockchain on server and run Bitcoin Core as client only?</strong></p>

<p>I want to run Core wallets on 2 or 3 or even more computers on my local network. The best way to store the full blockchain is to put it on one server on my local network.</p>

<p>I want the Core client to read only the blockchain data and listen for changes from the server but not write anything to the server, like a read-only directory. The server should be the only one allowed to write updates to the blockchain data.</p>

<p>The Core client should write private data to <code>%AppData%\Bitcoin</code> as usual but segregate the blockchain data onto the server.</p>

<p>How do I do this?</p>

<bitcoin-core>
How to store full blockchain on server and run Bitcoin Core as client only?
XP1
# How to store full blockchain on server and run Bitcoin Core as client only?

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

**How to store full blockchain on server and run Bitcoin Core as client only?**

I want to run Core wallets on 2 or 3 or even more computers on my local network. The best way to store the full blockchain is to put it on one server on my local network.

I want the Core client to read only the blockchain data and listen for changes from the server but not write anything to the server, like a read-only directory. The server should be the only one allowed to write updates to the blockchain data.

The Core client should write private data to `%AppData%\Bitcoin` as usual but segregate the blockchain data onto the server.

How do I do this?

**Tags:** bitcoin-core


---

## 3 answers

### Answer by username_1 on 2018-05-19. Score: 2

It is possible to configure your server/clients as follows, although it is not exactly what you have described. I presume that you still want each client to have its own separate wallet.

1. On your server, make a full installation of Bitcoin Core.
   1. In the config file set `bind=`.
   2. Set any other options, for example to enable incoming peers from the internet.
   3. Restart server node for config to take effect.
2. On each client make a full installation of Bitcoin Core.
   1. In your config file set `connect=`.
   2. In your config file set `prune=` where n is greater than 550MiB. This will limit storage requirements.
   3. Set any other options.
   4. Restart client node for config to take effect.

Using `connect=` disables automatic connections so, your nodes will only connect to the server.


---

### Answer by username_2 on 2017-08-09. Score: 1

This is not supported.

What is supported:

* Run Bitcoin Core in pruning mode (which means it still has a local blockchain, but only recent blocks are kept.
* Run lightweight software as client, and make it only connect to your (clearly trusted) server. This way you get a fully validated chain, without the resource usage.


---

### Answer by username_3 on 2017-11-07. Score: 0

You could try [Bitcore](https://bitcore.io/) instead. It contains a fork of the reference bitcoin implementation with added support for indexing of data, and includes an API for running it on a server. You can then use the API from your local computers or access the built-in blockchain explorer.


---

