As far as I understood the problem, transaction versions are not part of the consensus. So they can be any value and for confirmed transactions it doesn't make a difference. However, in order to get the transaction hash right, we persist the transaction version along with everything else.
Bitcoin Core 0.14 started to make use of the transaction version (for unconfirmed transactions only), which is why you're starting to see this problem. On 03/22/2017 03:04 PM, Manfred Karrer wrote: > I just saw that I get an UnreadableWalletException when I use Bitcoin > Core 14 for creating blocks (regtest) and have a transaction in my > wallet which is in that block. > I found > that > https://github.com/bitcoinj/bitcoinj/commit/be09b620626681c9e51a211ee314a34cb7958a12 > fixed an serialization issues with the transaction version. After > applying that fix to my branch I get rid of the problem as well. > > I wanted to ask for a bit more background why that suddenly breaks with > Bitcoin Core 14. > Is transaction version added in Bitcoin Core 14 and was not used in > earlier versions? > > Br, > Manfred > > -- > You received this message because you are subscribed to the Google > Groups "bitcoinj" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
