Yes, current situation is sort of a mess. I suppose 1.5.3 (and 1.5.4) are the winning chain. Kind of a shame since 1.5.5 was a nice update but no one is using it. To make matters worse the original source was update to 1.5.5 but still no one has switched. Doing so now produces problems for the exchanges as all transactions would not have occurred on 1.5.5.
What to do?
i can push the 1.55 fork time back another few months so people need to update before say... august 1st (and rename it 1.56)? then spread the message to the exchanges and explorer with an updated github link for them to update.
this would require everyone running 1.55 to go back to 1.53, resync, and upgrade to 1.56 from there. that could work.
orrr we can accept that the source will never get updated/upgraded XD