Giving myself the answer ;-):
It seems that the heavy loading of so many blockheaders just consumed a lot
o CPU and that caused that bas user experience to have the startup getting
stalled.
With a newly created up to date checkpoint file the initial download is not
super fast.
There are
After further testing I could isolate the issue to be between v14.4. and
v.14.5. Bisq is based on 14.4. After comparing and I found that the
checkpoint files was causing the issue. After updating it from 14.5. it
works. Any idea why?
I got those logs in the "broken" version:
00:09:44 26
The stall messages are just a symptom. For finding the cause have a look
at the logfile of both bitcoinj and Bitcoin Core.
On 04/12/2018 00.12, Manfred Karrer wrote:
> I use whitelist=127.0.0.1 in the bitcoin.conf file. There was another
> property but that does require the port as well and we
Here is a bug report form a user as
well: https://github.com/bisq-network/bisq/issues/1823
Here is the fork we are using:
https://github.com/bisq-network/bitcoinj/commits/bisq_0.14.4.1
Am Sonntag, 2. Dezember 2018 18:53:49 UTC+1 schrieb Manfred Karrer:
>
> When having latest Bitcoin Core
