<p>No, they’re completely incompatible. </p>

CC BY-SA 4.0
2019-11-26T15:31:50.217Z
2019-11-26T15:31:50.217Z
Claris
<p>You can't use the same <code>datadir</code>, but you can tell <code>btcd</code> to connect to your locally-running <code>bitcoind</code> instance in order to do the initial blockchain sync. This means that you'll end up with two copies of the blockchain (one for <code>bitcoind</code> and one for <code>btcd</code>) but the sync will happen much faster than starting <code>btcd</code> with default settings.</p>
<p>In your <code>btcd.conf</code> file:</p>
<pre><code>; only connect to locally-running node
connect=127.0.0.1

; no need to query for other nodes
nodnsseed=1

; listen on a port other than the default (if bitcoind is already running on the default)
listen=127.0.0.1:8336

; secure the RPC API so that you can interface with your sycing node by using btcctl
rpcuser=&lt;rpcusername&gt;
rpcpassword=&lt;rpcuserpassword&gt;

; sync with indexes enabled
txindex=1
addrindex=1
</code></pre>
<p>Now start <code>btcd</code>. It should start, but no peers will be connected - you can verify this by running <code>btcctl getpeerinfo</code> and you'll get <code>[]</code>.</p>
<p>With <code>btcd</code> running, force your <code>bitcoind</code> node to connect to it by using the command <code>bitcoin-cli --rpcuser=&lt;bitcoindrpcusername&gt; --rpcpassword=&lt;bitcoindrpcuserpassword&gt; addnode 127.0.0.1:8336 'onetry'</code></p>
<p>Now run <code>btcctl getpeerinfo</code> again, and you should see that your local <code>bitcoind</code> node is connected. <code>btcd</code> has started to sync and it should only take a few hours to sync from the local node. This is much faster than the days it would take to sync over the internet.</p>

CC BY-SA 4.0
2021-03-11T02:02:40.860Z
2021-03-11T02:02:40.860Z
Chris Concannon
<p>I've already fully synced the blockchain with btcd, can I point bitcoind at the same <code>datadir</code> and use its contents?</p>

<blockchain><bitcoind><full-node><datadir><btcd>
Can bitcoind and btcd share a datadir?
Matthew Cruz
# Can bitcoind and btcd share a datadir?

(Asked by: username_0 on 2019-11-26)

I've already fully synced the blockchain with btcd, can I point bitcoind at the same `datadir` and use its contents?

**Tags:** blockchain, bitcoind, full-node, datadir, btcd


---

## 2 answers

### Answer by username_1 on 2019-11-26. Score: 3 | Accepted answer

No, they’re completely incompatible.


---

### Answer by username_2 on 2021-03-11. Score: 2

You can't use the same `datadir`, but you can tell `btcd` to connect to your locally-running `bitcoind` instance in order to do the initial blockchain sync. This means that you'll end up with two copies of the blockchain (one for `bitcoind` and one for `btcd`) but the sync will happen much faster than starting `btcd` with default settings.

In your `btcd.conf` file:

```
; only connect to locally-running node
connect=127.0.0.1

; no need to query for other nodes
nodnsseed=1

; listen on a port other than the default (if bitcoind is already running on the default)
listen=127.0.0.1:8336

; secure the RPC API so that you can interface with your sycing node by using btcctl
rpcuser=<rpcusername>
rpcpassword=<rpcuserpassword>

; sync with indexes enabled
txindex=1
addrindex=1

```

Now start `btcd`. It should start, but no peers will be connected - you can verify this by running `btcctl getpeerinfo` and you'll get `[]`.

With `btcd` running, force your `bitcoind` node to connect to it by using the command `bitcoin-cli --rpcuser=<bitcoindrpcusername> --rpcpassword=<bitcoindrpcuserpassword> addnode 127.0.0.1:8336 'onetry'`

Now run `btcctl getpeerinfo` again, and you should see that your local `bitcoind` node is connected. `btcd` has started to sync and it should only take a few hours to sync from the local node. This is much faster than the days it would take to sync over the internet.


---

