mirror of
https://github.com/bisq-network/bisq.git
synced 2025-02-21 22:31:44 +01:00
persistance is below the chain height of btc core. With the new handling of dao state hashblocks it can be the we have persisted the latest block up to the chain height. Before that change we only had the last snapshot which was at least 20 blocks back persisted. We want to avoid to get caught in a retry loop at parseBlocksOnHeadHeight so we filter out that case just at the caller. At parseBlocksOnHeadHeight we inline the requestChainHeadHeightAndParseBlocks method as it is not used by other callers anymore. This case that we request a block but our local btc core chain hight is below that might be some edge case when we had a synced dao blocks but we btc core is resyncing... |
||
---|---|---|
.. | ||
.tx | ||
src | ||
update_translations.sh |