phm87



Offline



Activity: 173

Merit: 101



Mining pool operator @ https://www.unimining.net







Full MemberActivity: 173Merit: 101Mining pool operator @ https://www.unimining.net

Re: Network Attack on XVG / VERGE April 04, 2018, 09:05:15 PM #115 Quote from: ocminer on April 04, 2018, 08:34:47 PM Quote from: phm87 on April 04, 2018, 08:31:18 PM Quote from: ocminer on April 04, 2018, 08:13:44 PM Quote from: ocminer on April 04, 2018, 07:40:18 PM Quote from: Dogedarkdev on April 04, 2018, 07:06:39 PM Quote from: defaced on April 04, 2018, 06:58:33 PM nice a new version of the famed timewarp attack.. very interesting.



yep.. we pushed a quick fix and most pools have already updated.. we're already working on a whole new block verification process.



we're kinda glad this happened and that it wasn't as bad as it could have been.

yep.. we pushed a quick fix and most pools have already updated.. we're already working on a whole new block verification process.we're kinda glad this happened and that it wasn't as bad as it could have been.



Hmm, you guys are aware that the "fix" you pushed actually IS a hardfork ? So your blockchain snapshot is not valid anymore, the wallet's won't sync up from scratch anymore and the current chain is simply not usable anymore with that new "fix" ?



Your change simply disagrees with the attackers blocks, the first block I see from the attacker was 2007365 - so the wallets will stop syncing there and simply not progress any further.



I remember your first forking dramas when trying to fork into Tor which failed 2 times IIRC.



You should immediately refrain from that "fix" and set a proper fork-height (at least 48h) and the chain up until the fork block MUST accept blocks with the old timestamps and blocks after that fork block then only with the new timestamp.







Hmm, you guys are aware that the "fix" you pushed actually IS a hardfork ? So your blockchain snapshot is not valid anymore, the wallet's won't sync up from scratch anymore and the current chain is simply not usable anymore with that new "fix" ?Your change simply disagrees with the attackers blocks, the first block I see from the attacker was 2007365 - so the wallets will stop syncing there and simply not progress any further.I remember your first forking dramas when trying to fork into Tor which failed 2 times IIRC.You should immediately refrain from that "fix" and set a proper fork-height (at least 48h) and the chain up until the fork block MUST accept blocks with the old timestamps and blocks after that fork block then only with the new timestamp.

bumping this for awareness

bumping this for awareness

Thank you ocminer, I hope that dev coin team will fix this problem and warn pools in a timely manner if a fork should be done. i'd be happy that we revert the coins mined by the attacker.

Thank you ocminer, I hope that dev coin team will fix this problem and warn pools in a timely manner if a fork should be done. i'd be happy that we revert the coins mined by the attacker.



From what I know they won't roll back and just move on.. However, they still must do the hardfork in a proper way

From what I know they won't roll back and just move on.. However, they still must do the hardfork in a proper way

I'd prefer that XVG coin dev team decide to roll back to cancel the coins mined during the hack, it is better I think.





What do you think guys ? I'd prefer that XVG coin dev team decide to roll back to cancel the coins mined during the hack, it is better I think.What do you think guys ?