01:59 <stellar-slack> <sacarlson> I gave stellar-core build version v0.2.4 on Live Public network a try today. It seems I'm only connected to 2 of the five nodes that I can see. I also see many Dropping peer connectHandler error: Operation aborted from most attempted connetions.

02:30 <stellar-slack> <jed> Yeah you need to use 0.3.1 at least

02:34 <stellar-slack> <sacarlson> that's not what is indicated on http://horizon.stellar.org|horizon.stellar.org that indicates it's running v 2.4-7

02:35 <stellar-slack> <sacarlson> and when I checked horizon is still working

02:35 <stellar-slack> <sacarlson> seems to be some conflict in what you publish

02:40 <stellar-slack> <jed> 2.4-7 means 7 commits after 2.4

02:42 <stellar-slack> <sacarlson> yes that I would also expect mean it some time before 0.3.1. also the g25fd2a8 at the end should be the hash of the git but I fail to find that version publshed at all in github branches

02:48 <stellar-slack> <jed> you have to ignore the g

02:48 <stellar-slack> <jed> 25fd2a8

02:48 <stellar-slack> <sacarlson> I stand corrected yes I found that one when I removed the g

02:48 <stellar-slack> <jed> don't know why it puts the g there

02:49 <stellar-slack> <sacarlson> well I've already tried 0.3.1 and failed so might as whell try version 25fd2a8 as well

02:50 <stellar-slack> <jed> why does 3.1 fail?

02:50 <stellar-slack> <sacarlson> similar with droped peers

02:51 <stellar-slack> <sacarlson> stuck in joining

02:51 <stellar-slack> <sacarlson> I can give that another try as now I no longer delete the binary like I did before that required recompile

02:51 <stellar-slack> <jed> probably an issue with your quorum set

02:51 <stellar-slack> <sacarlson> could be

02:52 <stellar-slack> <sacarlson> it was working fine with this set just 3 - 4 days ago

02:53 <stellar-slack> <jed> yeah but not all the validators have switched to 0.3.1 yet so there are less online

02:54 <stellar-slack> <sacarlson> the way bitcoin does upgrades is that they all switch at the same time at a ledger crossing point, the new software still works with the old up until that point

02:55 <stellar-slack> <sacarlson> there should be no spliting of the network in upgrade transitions

02:56 <stellar-slack> <sacarlson> this method provides overlap time to be able to install and restart systems before the upgrade point