[bisq-network/bisq] Fix issue with invalid vote result (#2358)

[Manfred Karrer]

I understand now why the own tx is included if triggered at same block. The usage of bsqNode.getChainTipHeight results that we get an unrelated blockheight to the blockheight which is in daoState. So it can be that the own BV was already parsed in earlier startup and the dao state was persisted, so the tx is there even we are currently in parsing not completed. Newly added BVs which have not been already included in the snapshot are not parsed yet ans therefore the BV tx is not found and not included for the majority hash.

-- 
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/2358#issuecomment-460048686
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190203/36513474/attachment.html>