<p><strong>Solution</strong>
This solution gains access to the coins that are unavailable via BitcoinXT.</p>

<ol>
<li><p>Using the bitcoin client, export the private key using the command <code>bitcoin-cli dumpprivkey "accountname"</code>.</p></li>
<li><p>Uninstall BitcoinXT and remove the existing block chain (usually stored in ~/.bitcoin ).</p></li>
<li><p>Install Bitcoin Core (not Bitcoin XT), start the bitcoin-d server.</p></li>
<li><p>While the new chain is syncing, import the old key with <code>bitcoin-cli importprivkey "keyExportedInStep1"</code></p></li>
<li><p>Wait for blockchain to sync.</p></li>
</ol>

<p><strong>Discussion and Lessons Learned</strong></p>

<p>I was not sure that the testnet work had separated, but the fact that the transaction I was looking for was not in the corresponding block number was a huge indication.  After uninstalling BitcoinXT and installing Bitcoin, I now see the "missing" funds referenced above.</p>

<p>What this means is that the test network has reached that point where BitcoinXT no longer recognizes transactions and block chains that are approved by standard Bitcoin Core clients.  While BitcoinXT is compatible still on a public network, the test network is no longer compatible.</p>

<p>This also means that there is a need for a BitcoinXT faucet. At the time of this writing, I have not found a faucet for BitcoinXT compatible transactions.</p>

<p>The screen shot below shows that I now have access to the coins that were previously lost.</p>

<p><a href="https://i.sstatic.net/vtXJy.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/vtXJy.png" alt="enter image description here"></a></p>

CC BY-SA 3.0
2015-12-06T22:28:13.083Z
2015-12-06T22:28:13.083Z
Jared Clemence
<p>I installed bitcoind and bitcoin-cli, set the configuration file so that I am using test-net and requested funds from <a href="https://tpfaucet.appspot.com" rel="nofollow noreferrer">TP's TestNet Faucet</a>. The funds never appeared in my account.</p>

<p>I thought at first that it was a matter of syncing the blockchain.  I waited several days, and my block count remains at least 400 blocks behind the most current block displayed on <a href="http://tbtc.blockr.io" rel="nofollow noreferrer">this blockchain (testnet) viewer</a>.  The network traffic displayed in my system monitor makes it clear that no new blocks are being downloaded to bridge the 400 block gap that exists between my block height and the block height displayed on the public testnet blockchain; blocks are being downloaded once every 10 minutes allowing my system to at least keep pace with the network with a constant gap.</p>

<p>It took several more days for me to get to a block height that includes the faucet transaction described in the first paragraph, but even after my block height exceeded the needed <a href="http://tbtc.blockr.io/address/info/n2k8hWiu2PGieUe7DXtJaVMmGyTtupfFqc" rel="nofollow noreferrer">block number in which the transaction occured</a>, my account balances remained at zero.</p>

<p>I display a screen shot below that includes the confirmed transaction as viewed on the publicly visible blockchain (testnet), and the terminal window that shows the results of my "getinfo", "getaccountaddress", and "getblockcount" commands.  There are 12 peers, which are a mixture of inbound and outbound connections, none-of-which were manually entered, all of which were automatically discovered through P2P discovery.</p>

<p>Thinking there was something wrong with the faucet, I installed the Mycelium Testnet Wallet on my phone and made a faucet withdrawal to that new account.  That faucet transaction appeared in my phone immediately with 0 confirmations and has since been fully confirmed.</p>

<p>Given all the above, I am thinking that my "failed" testnet connection with 12 peers is somehow on a separate testnet that uses a different blockchain than the one that is used by the faucet.  It is my understanding of BitcoinXT that it should be fully compatible with the Bitcoin testnet in the same way that BitcoinXT is designed to be fully compatible with the real Bitcoin network, unless in test-net that condition has been met which causes the networks to diverge and separate.</p>

<p>If this is the case, is there a separate BitcoinXT faucet that can be used?</p>

<p>Or, have I set up my system incorrectly, perhaps?</p>

<p>The graphic of the browser window below shows the successful and confirmed faucet transaction visible in block number 68146. It also shows that the block is in the testnet. The terminal window inside that graphic shows that my server is running on testnet and that my blockchain includes the block numbered 68146, which should have included the transaction depicted, but does not.  As confirmation that the account is right, I display the account address in the terminal, and it is the same address that displays as the recipient of the testnet transaction appearing in the browser window.</p>

<p><a href="https://i.sstatic.net/R4Pud.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/R4Pud.png" alt="Bitcoin Transaction displayed on Ubuntu 15.04 system"></a></p>

<transactions><bitcoind><testnet><bitcoin-xt>
What am I doing wrong with my BitcoinXT test net setup?
Jared Clemence
# What am I doing wrong with my BitcoinXT test net setup?

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

I installed bitcoind and bitcoin-cli, set the configuration file so that I am using test-net and requested funds from [TP's TestNet Faucet](https://tpfaucet.appspot.com). The funds never appeared in my account.

I thought at first that it was a matter of syncing the blockchain. I waited several days, and my block count remains at least 400 blocks behind the most current block displayed on [this blockchain (testnet) viewer](http://tbtc.blockr.io). The network traffic displayed in my system monitor makes it clear that no new blocks are being downloaded to bridge the 400 block gap that exists between my block height and the block height displayed on the public testnet blockchain; blocks are being downloaded once every 10 minutes allowing my system to at least keep pace with the network with a constant gap.

It took several more days for me to get to a block height that includes the faucet transaction described in the first paragraph, but even after my block height exceeded the needed [block number in which the transaction occured](http://tbtc.blockr.io/address/info/n2k8hWiu2PGieUe7DXtJaVMmGyTtupfFqc), my account balances remained at zero.

I display a screen shot below that includes the confirmed transaction as viewed on the publicly visible blockchain (testnet), and the terminal window that shows the results of my "getinfo", "getaccountaddress", and "getblockcount" commands. There are 12 peers, which are a mixture of inbound and outbound connections, none-of-which were manually entered, all of which were automatically discovered through P2P discovery.

Thinking there was something wrong with the faucet, I installed the Mycelium Testnet Wallet on my phone and made a faucet withdrawal to that new account. That faucet transaction appeared in my phone immediately with 0 confirmations and has since been fully confirmed.

Given all the above, I am thinking that my "failed" testnet connection with 12 peers is somehow on a separate testnet that uses a different blockchain than the one that is used by the faucet. It is my understanding of BitcoinXT that it should be fully compatible with the Bitcoin testnet in the same way that BitcoinXT is designed to be fully compatible with the real Bitcoin network, unless in test-net that condition has been met which causes the networks to diverge and separate.

If this is the case, is there a separate BitcoinXT faucet that can be used?

Or, have I set up my system incorrectly, perhaps?

The graphic of the browser window below shows the successful and confirmed faucet transaction visible in block number 68146. It also shows that the block is in the testnet. The terminal window inside that graphic shows that my server is running on testnet and that my blockchain includes the block numbered 68146, which should have included the transaction depicted, but does not. As confirmation that the account is right, I display the account address in the terminal, and it is the same address that displays as the recipient of the testnet transaction appearing in the browser window.

[![Bitcoin Transaction displayed on Ubuntu 15.04 system](https://i.sstatic.net/R4Pud.png)](https://i.sstatic.net/R4Pud.png)

**Tags:** transactions, bitcoind, testnet, bitcoin-xt


---

## 1 answers

### Answer by username_0 on 2015-12-06. Score: 0 | Accepted answer

**Solution**
This solution gains access to the coins that are unavailable via BitcoinXT.

1. Using the bitcoin client, export the private key using the command `bitcoin-cli dumpprivkey "accountname"`.
2. Uninstall BitcoinXT and remove the existing block chain (usually stored in ~/.bitcoin ).
3. Install Bitcoin Core (not Bitcoin XT), start the bitcoin-d server.
4. While the new chain is syncing, import the old key with `bitcoin-cli importprivkey "keyExportedInStep1"`
5. Wait for blockchain to sync.

**Discussion and Lessons Learned**

I was not sure that the testnet work had separated, but the fact that the transaction I was looking for was not in the corresponding block number was a huge indication. After uninstalling BitcoinXT and installing Bitcoin, I now see the "missing" funds referenced above.

What this means is that the test network has reached that point where BitcoinXT no longer recognizes transactions and block chains that are approved by standard Bitcoin Core clients. While BitcoinXT is compatible still on a public network, the test network is no longer compatible.

This also means that there is a need for a BitcoinXT faucet. At the time of this writing, I have not found a faucet for BitcoinXT compatible transactions.

The screen shot below shows that I now have access to the coins that were previously lost.

[![enter image description here](https://i.sstatic.net/vtXJy.png)](https://i.sstatic.net/vtXJy.png)


---

