<p><a href="https://github.com/bitcoinj/bitcoinj/issues/1336" rel="nofollow noreferrer">https://github.com/bitcoinj/bitcoinj/issues/1336</a></p>

<blockquote>
  <p>Just ran into this issue and spent a while debugging it (on latest release, 0.14.5). I added rpcserialversion=0 and that fixed the issue, so it's easy enough to work around. If bitcoinj isn't planning to add support for the new format, it might be nice for bitcoinj to realize it is parsing the new format, and throw a more relevant error message, something like "New rpc serial format not supported, see #1336".</p>
</blockquote>

CC BY-SA 3.0
2017-12-12T17:41:56.247Z
2017-12-12T17:41:56.247Z
blasteye
<p>I am experimenting with Bitcoinj to design a stable node that is synced.
Older versions of bitcoinj seem to drop connections and stop syncing. </p>

<p>I currently see the following branches (see screenshots).
<a href="https://i.sstatic.net/49zQg.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/49zQg.png" alt="enter image description here"></a></p>

<p>I would assume to use the "release" branch but the latest one is "Unverified"</p>

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

<p>On the other hand, I am also inclined to use one of the active branches.
The Segwit has not been updated for 11 months. I recall reading on the mailing list that the segwit code is still not complete.</p>

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

<p>Instead of having to dig into the code myself, I would like to get opinions on which branch to use and save some time.</p>

<segregated-witness><bitcoinj><segwit2x>
Which branch of bitcoinj should I sync to?
Jus12
# Which branch of bitcoinj should I sync to?

(Asked by: username_0 on 2017-10-28)

I am experimenting with Bitcoinj to design a stable node that is synced.
Older versions of bitcoinj seem to drop connections and stop syncing.

I currently see the following branches (see screenshots).
[![enter image description here](https://i.sstatic.net/49zQg.png)](https://i.sstatic.net/49zQg.png)

I would assume to use the "release" branch but the latest one is "Unverified"

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

On the other hand, I am also inclined to use one of the active branches.
The Segwit has not been updated for 11 months. I recall reading on the mailing list that the segwit code is still not complete.

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

Instead of having to dig into the code myself, I would like to get opinions on which branch to use and save some time.

**Tags:** segregated-witness, bitcoinj, segwit2x


---

## 1 answers

### Answer by username_1 on 2017-12-12. Score: 1

<https://github.com/bitcoinj/bitcoinj/issues/1336>

> Just ran into this issue and spent a while debugging it (on latest release, 0.14.5). I added rpcserialversion=0 and that fixed the issue, so it's easy enough to work around. If bitcoinj isn't planning to add support for the new format, it might be nice for bitcoinj to realize it is parsing the new format, and throw a more relevant error message, something like "New rpc serial format not supported, see #1336".


---

