getinfo longestchain takes startingheight as the value from a banned unsynced node #72
Description
on the TOKEL chain getinfo showed bad "longestchain" much greater than the actual tip (53474 vs 52577). There was a banned, not synced node in the net (in getpeerinfo it has the startingheight=53474 taken as longestchain).
So the longestchain calc algo appears incorrect, it should skip not-synced nodes somehow