Bitcoinj caught after chain break up

0
60


I’m utilizing LevelDBFullPrunedBlockStore as a BlockChain. as soon as in each 2-3 chainsplit within the community my bitcoinJ node stops to obtain new block. The state of affairs is at all times the identical

1)My node get block on peak x that community will mark as orphaned later
2)My node will get block x+1 (from mainchain) and says that block x (orphaned by the community later) can be orphaned
3)My node get the mainchain block on peak x and says that “couldn’t confirm block”

Later friends are sending me single transactions, however I’m unable to obtain any extra blocks, there is no such thing as a logs in regards to the new block in any respect. I didn’t change something within the code that’s answerable for block persistence. After I restart the appliance it doesn’t obtain any new block as nicely.

Right here is log type Saturday the place it happend:

2017-05-13 22:45:56 INFO  AbstractBlockChain:597 - Block forks the chain at peak 466251/block 000000000000000000c0b4c4e062b8cc77a5fd3dc5594bee9fd5a8cacdeba92b, nevertheless it didn't trigger a reorganize:
000000000000000001b3699313793566fb947d554173c5f19fe790e597adedbf
2017-05-13 22:45:56 INFO  AbstractBlockChain:926 - Related orphan 00000000000000000005b2d8a9d429b050a5a9ba4d44dbe1543280d6e89b77af
2017-05-13 22:45:56 INFO  AbstractBlockChain:576 - Block is inflicting a re-organize
2017-05-13 22:45:56 INFO  AbstractBlockChain:752 - Re-organize after break up at peak 466251
2017-05-13 22:45:56 INFO  AbstractBlockChain:753 - Previous chain head: 000000000000000000c89a56fec1a04a5981e7f614e6ba2f877559fc2ef9e138
2017-05-13 22:45:56 INFO  AbstractBlockChain:754 - New chain head: 00000000000000000005b2d8a9d429b050a5a9ba4d44dbe1543280d6e89b77af
2017-05-13 22:45:56 INFO  AbstractBlockChain:755 - Cut up at block: 000000000000000000c0b4c4e062b8cc77a5fd3dc5594bee9fd5a8cacdeba92b
2017-05-13 22:45:57 WARN  Peer:1025 - [2a03:4000:2:496:0:0:0:8]:8333: Block verification failed
org.bitcoinj.core.VerificationException: Couldn't confirm block:
 block: 
   hash: 000000000000000001b3699313793566fb947d554173c5f19fe790e597adedbf
   model: 536870912 (BIP34, BIP66, BIP65)
   earlier block: 000000000000000000c0b4c4e062b8cc77a5fd3dc5594bee9fd5a8cacdeba92b
   merkle root: dcf81e3a220fa3a14ed09cd76497e13fb9c9affeef9c9ce052c9c1e1854fac26
   time: 1494708074 (2017-05-13T20:41:14Z)
   problem goal (nBits): 402781863
   nonce: 2897470832
   with 2100 transaction(s):
  8a0d0a5f11ef31f974f59658c27824b2ddacba88e6b6dfa1865caa48bf4bb444

Did anybody had the identical difficulty? I’ve no clue what I suppose to do.

LEAVE A REPLY

Please enter your comment!
Please enter your name here