UPDATE: Bisq 1.9.17 has just been released, please download and install it to resolve the incumbent issues.
.
.
.
There is an issue going on with bitcoinj, which is the bitcoin wallet library that Bisq1 uses
opened 03:50PM - 23 Jun 24 UTC
### Description
Bisq cannot sync SPV. The error in the title is in the logs. … This is happening both with network SPV sync as well as local full node.
Possibly a bug in bitcoinj and I have opened an issue over there (https://github.com/bitcoinj/bitcoinj/issues/3410)
#### Version
1.9.16
### Steps to reproduce
Just run the app, it won't sync and logs are spammed with the message
#### Additional info
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #033[0;39m#033[31mJun-23 08:44:26.728 [NioClientManager] WARN org.bitcoinj.core.PeerSocketHandler: [127.0.0.1]:8333 - java.lang.IllegalStateException: Ran out of space to store chain work!
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at com.google.common.base.Preconditions.checkState(Preconditions.java:510)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.core.StoredBlock.serializeCompact(StoredBlock.java:121)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.store.SPVBlockStore.put(SPVBlockStore.java:201)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.core.BlockChain.addToBlockStore(BlockChain.java:93)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.core.AbstractBlockChain.connectBlock(AbstractBlockChain.java:543)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.core.AbstractBlockChain.add(AbstractBlockChain.java:469)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.core.AbstractBlockChain.add(AbstractBlockChain.java:361)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.core.BlockChain.add(BlockChain.java:170)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.core.Peer.endFilteredBlock(Peer.java:1072)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.core.Peer.processMessage(Peer.java:454)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.core.PeerSocketHandler.receiveBytes(PeerSocketHandler.java:187)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.net.ConnectionHandler.handleKey(ConnectionHandler.java:238)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.net.NioClientManager.handleKey(NioClientManager.java:86)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.net.NioClientManager.run(NioClientManager.java:122)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at com.google.common.util.concurrent.AbstractExecutionThreadService$1$2.run(AbstractExecutionThreadService.java:66)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at com.google.common.util.concurrent.Callables$4.run(Callables.java:117)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at org.bitcoinj.utils.ContextPropagatingThreadFactory$1.run(ContextPropagatingThreadFactory.java:51)
Jun 23 08:44:26 bisq bisq-Bisq.desktop[263666]: #011at java.base/java.lang.Thread.run(Thread.java:829)
The chainwork value since block 849138 was mined has exceeded the variable allocation size of 12byte in bitcoinj, and this prevents the whole library from working.
This is a network wide problem that prevents all bisq clients from correctly syncing with the blockchain.
If you are connecting to your own bitcoin node, you will see the btc network peers change continuously between 0 and 1.
Devs are assessing the issue and evaluating the best course of action.