[bisq-network/bisq] Client unable to synch on DAO on startup (#2900)

[UnityJon]

Last weds I went away for 6 days.  I had 6 open offers at the time and 1 open trade (which I opened a dispute on as the counter-party was late confirming).  Client was shut down whilst away.  On returning and starting up it consistently throws a java exception when trying to synch the DAO.  Looking at the log files it would seem linked to the (now closed) dispute.  I can view my offers but not edit or remove them.  I can also view wallets - but basically cant do any trades as the client can't synch the DAO.  At a guess it's because it was so long after the dispute was closed that the messages aren't available any more - but my client wants them.

I attach a log of my latest session - have tried plenty of times with same results (including rebuilding the DAO from genesis block).

[bisqlog.txt](https://github.com/bisq-network/bisq/files/3303195/bisqlog.txt)


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/2900
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190618/eb144bed/attachment.html>