Quote from: tepelstreeltje on September 18, 2016, 12:55:30 PM

Hey all im really sorry you encounter all these issues and i apologize for that and to be honest im not really sure why some have this issue. Also hoped to reproduce it but i haven't so far and staking with 19m. That kinda sucks because i can't debug it myself or look for a solution.

Also i know i failed to bring the news out earlier but to be honest i was really struggeling to release the update or not after update 2.4 because of the forks and when i decided to go for it in all the hectic i forgot this thread.

Quote from: desynct on September 18, 2016, 03:08:03 AM

already tested everything, just too many 2.3.1 yet, and presstab, i hope they'll soon update, nothing to worry
~~too little Führers of Cryptopia may j*** off until xmas, let them be happy~~

I knew the old connections would be a problem as it will take a long time before all the people have updated. There was even a 2.3.0 wallet running. I thought about it to bump the peer proto version aswell but wasn't really sure on that so i didn't which was perhaps another error on my side. Presstab is contacted but it seems he has issues syncing aswell.

Quote from: 6436346346 on September 18, 2016, 04:22:26 AM

Quote from: o0o0 on September 18, 2016, 04:16:15 AM

Quote from: 6436346346 on September 18, 2016, 04:05:09 AM

Quote from: o0o0 on September 18, 2016, 03:42:02 AM

Quote from: desynct on September 18, 2016, 03:08:03 AM

already tested everything, just too many 2.3.1 yet, and presstab, i hope they'll soon update, nothing to worry
too little Führers of Cryptopia may j*** off until xmas, let them be happy

i don't understand that last part... fuhrers of cryptopia may jerk off? let them be happy? what do you mean

They are butthurt cause out NET wallet forked on 2.5, and now they think abusing us will fix it overnight.

It was meant to fork on 2.5 i thought though.. so isn't that normal behavior. Or do you mean it didn't stay on correct chain?

Our 2.5 went off on its own fork (twice), we are resyncing now and battling the abusive support tickets from NET users, never a dull moment.

Again sorry for all the inconvenience that it has caused you but yes there where 2 forks in this update actually 3 if you count the PoW reward change on block 1296010. The first was with the PoW and the second was probably on block 1300000 or a few after. On that block a signature check became active but that should be the last one

Will bumping the peer proto version be a softfork change? I think we need to knock that stuff out ignoring old peers.