<p>I'm not totally sure why it failed on height 26859, but I upgraded to 0.9.4 (from 0.9.3) using:</p>

<pre><code>apt-get install --only-upgrade bitcoind
</code></pre>

<p>then I deleted the testnet3 folder and fired up bitcoind and now it's working and has passed height 26859.</p>

CC BY-SA 3.0
2015-02-11T03:20:26.667Z
Glad you got it to work. There was a not so obvious patch I had to apply to get v0.9.4 to compile.
skaht
CC BY-SA 3.0
2015-02-11T03:24:58.390Z
The instructions above are for people using the PPA.
greatwitenorth
CC BY-SA 3.0
2015-02-11T02:32:07.427Z
2015-02-11T02:39:45.937Z
2015-02-11T02:39:45.937Z
greatwitenorth
<p>Not sure if I can assist you directly. I compiled the code myself from the Github bitcoin/bitcoin <a href="https://github.com/bitcoin/bitcoin" rel="nofollow">site</a>.  </p>

<p>Just compiled bitcoind for OSX 10.9 and 10.10.  Notice that the results below are for v0.9.4. Here are the "getinfo" results I get for the testNet. (FYSA - had to apply a soft link so that I didn't have to supply a fully qualified file path name.)</p>

<pre><code>Skaht% bitcoin-cli -conf=testNet.conf getinfo
{
    "version" : 90400,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 322742,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 1.00000000,
    "testnet" : true,
    "keypoololdest" : 1423202150,
    "keypoolsize" : 102,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}
</code></pre>

<p>Its a little disturbing to see the difficulty factor is shown to be one. However, when I issued a "coin" RPC to the bfgminer connected to the testNet bitcoind I received a valid difficulty factor.</p>

CC BY-SA 3.0
2015-02-11T07:52:39.377Z
Yes looks like the pb was fixed in 0.9.4 and later.
damienx
CC BY-SA 3.0
2015-02-11T07:55:07.210Z
I know why it was stuck, block 26860 had a transaction that couldn't be verified (0.9.3 version), that's why  it would never sync the rest of the blocks.
damienx
CC BY-SA 3.0
2015-02-11T11:19:48.347Z
For the reason why the difficulty appeared as 1, see http://bitcoin.stackexchange.com/questions/18554/how-can-i-find-the-real-difficulty-on-testnet.
Nate Eldredge
CC BY-SA 3.0
2015-02-11T01:34:39.610Z
2015-02-11T06:09:43.997Z
2015-02-11T06:09:43.997Z
skaht
<p>Downloaded the latest bitcoin core tar ball 0.9.3.
New install for test and development. This thread relates only to the TESTNET, I haven't tried on the production network.
When launching the bitcoind everything works as expected until it reaches block at 26859 where it stops adding blocks. Nothing happens after no more blocks are requested.
After some debugging, it appears that the next block 26860 contains a transaction that fails verification, so it won't validate the block. These blocks (that are failing) are more than 2 years old, but I didn't expect to hit this hurdle so early in the game. Can anybody shed some light ? Am I doing something wrong here? DOwnloaded the bitcoin tar from the official web site and checked the signature.</p>

<p>Anyone can easily reproduce this on the testnet network.
Any help appreciated.</p>

CC BY-SA 3.0
2015-02-10T14:17:00.563Z
That's really early. You can try deleting the latest block (blk00xxx.dat file) in .bitcoin/testnet3/blocks and restart bitcoind?
Jimmy Song
CC BY-SA 3.0
2015-02-11T02:19:18.413Z
I'm having the exact same issue. Using ubuntu 14.04 and bitcoin version 90300, protocol version 70002 and I've set txindex=1
greatwitenorth
<bitcoind><testnet>
bitcoin-0.9.3 won't syncup on TESTNET stuck at height 26859
damienx
# bitcoin-0.9.3 won't syncup on TESTNET stuck at height 26859

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

Downloaded the latest bitcoin core tar ball 0.9.3.
New install for test and development. This thread relates only to the TESTNET, I haven't tried on the production network.
When launching the bitcoind everything works as expected until it reaches block at 26859 where it stops adding blocks. Nothing happens after no more blocks are requested.
After some debugging, it appears that the next block 26860 contains a transaction that fails verification, so it won't validate the block. These blocks (that are failing) are more than 2 years old, but I didn't expect to hit this hurdle so early in the game. Can anybody shed some light ? Am I doing something wrong here? DOwnloaded the bitcoin tar from the official web site and checked the signature.

Anyone can easily reproduce this on the testnet network.
Any help appreciated.

**Tags:** bitcoind, testnet

> **Comments:**
> **username_1**: That's really early. You can try deleting the latest block (blk00xxx.dat file) in .bitcoin/testnet3/blocks and restart bitcoind?  
> **username_2**: I'm having the exact same issue. Using ubuntu 14.04 and bitcoin version 90300, protocol version 70002 and I've set txindex=1  

---

## 2 answers

### Answer by username_2 on 2015-02-11. Score: 2

I'm not totally sure why it failed on height 26859, but I upgraded to 0.9.4 (from 0.9.3) using:

```
apt-get install --only-upgrade bitcoind

```

then I deleted the testnet3 folder and fired up bitcoind and now it's working and has passed height 26859.

> **Comments:**
> **username_3**: Glad you got it to work. There was a not so obvious patch I had to apply to get v0.9.4 to compile.  
> **username_2**: The instructions above are for people using the PPA.  

---

### Answer by username_3 on 2015-02-11. Score: 0

Not sure if I can assist you directly. I compiled the code myself from the Github bitcoin/bitcoin [site](https://github.com/bitcoin/bitcoin).

Just compiled bitcoind for OSX 10.9 and 10.10. Notice that the results below are for v0.9.4. Here are the "getinfo" results I get for the testNet. (FYSA - had to apply a soft link so that I didn't have to supply a fully qualified file path name.)

```
username_3% bitcoin-cli -conf=testNet.conf getinfo
{
    "version" : 90400,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 322742,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 1.00000000,
    "testnet" : true,
    "keypoololdest" : 1423202150,
    "keypoolsize" : 102,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}

```

Its a little disturbing to see the difficulty factor is shown to be one. However, when I issued a "coin" RPC to the bfgminer connected to the testNet bitcoind I received a valid difficulty factor.

> **Comments:**
> **username_0**: Yes looks like the pb was fixed in 0.9.4 and later.  
> **username_0**: I know why it was stuck, block 26860 had a transaction that couldn't be verified (0.9.3 version), that's why  it would never sync the rest of the blocks.  
> **username_4**: For the reason why the difficulty appeared as 1, see http://bitcoin.stackexchange.com/questions/18554/how-can-i-find-the-real-difficulty-on-testnet.  

---

