Network Attack on XVG / VERGE

[remon78eg]

maybe he attacks the master nodes servers and make them vote to his blocks and reject the others, then the difficulty be low and he can mining alone at near zero difficulty.

[Firethorn29]

They stole our jibs!!

[ocminer]

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.

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.

[bubbagump]

They stole our jibs!!

They're still stealing our jibs!!

FTFY

[lotfiuser]

if im not wrong they fixed it bug could be happen on any coin even bitcoin so lets  not blame them for bug lets blame them for not fixing it so fast

[asmodat]

RIP

[LinuxDude]

maybe he attacks the master nodes servers and make them vote to his blocks and reject the others, then the difficulty be low and he can mining alone at near zero difficulty.

XVG doesn't use masternodes.

[jamesdavidso2]

VER "shitcoin" GE

[MundaneGatt]

the XVG community and Sunerok are assholes, i got kicked from their discord just for asking question, legit questions about a possible audit, y they made a crowdfund to release this info, then said we cant release for 3 weeks, cause NDA, and i was like well y do a crowdfund if u knew u couldn't disclose. i was called all sorts of names, FUDster was a nice one, and kicked. the XVG community and developers are shady, and theyre also assholes
ppl came to him about this attack when it was occurring, they were given the same treatment on forums. im not saying XVG isn't gonna go anywhere, but if it does, its gonna be in spite of its devs and community, which makes u question the currency
https://www.youtube.com/watch?v=ViW-6GhYy4Q

[BillionDollarMan]

The vergeDEV @ Discord says "everything is okay - there's nothing to fix"..

Since about 99% blocks by legit pools are rejected - and the dev team is not able to understand this problem, i'm closing and removing all VERGE pools from suprnova.

It could be Verge team it self. Perfect excuse for not living up to expectations after begging for partnership crap.

[Ai7xpressTV]

The explorer shows it's going on right now.

Where do you exactly see that? Would be nice to get some more information about how you detect these attacks using a block explorer.

[darkly spectre]

the XVG community and Sunerok are assholes, i got kicked from their discord just for asking question, legit questions about a possible audit, y they made a crowdfund to release this info, then said we cant release for 3 weeks, cause NDA, and i was like well y do a crowdfund if u knew u couldn't disclose. i was called all sorts of names, FUDster was a nice one, and kicked. the XVG community and developers are shady, and theyre also assholes
ppl came to him about this attack when it was occurring, they were given the same treatment on forums. im not saying XVG isn't gonna go anywhere, but if it does, its gonna be in spite of its devs and community, which makes u question the currency
https://www.youtube.com/watch?v=ViW-6GhYy4Q

yeah sunerok IS a huge arrogant cunt. the community is so stockholm syndrome'd he literally can't do anything wrong. just look at this topic and the wave of new accounts going "LOL FUD VERGE IS GOD"

[bubbagump]

The explorer shows it's going on right now.

Where do you exactly see that? Would be nice to get some more information about how you detect these attacks using a block explorer.

https://verge-blockchain.info/  Look at the timestamps.  I don't have a node running so I don't know if it's the hacker going at it or if there's an issue with that website.  I'm just assuming that it's the hacker since what's being shown on the site is exactly what ocminer described in the OP.

[ocminer]

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.

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

[BlackCon2018]

I couldn't agree more that the XVG community is filled with retards. All they do in the chat is post memes and troll other people. And when the facts are presented they scream at you that you're a FUDster... A bunch of delusional kids thinking XVG will make them rich. When lambo? - they say!

[buzzkillb]

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.

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

XVG hodlers should be thanking you for this info.  I hope this get this fixed soon, as it sucks in general for crypto.

[aciddude]

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.

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

how can we verify the hardfork ?

[ocminer]

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.

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

how can we verify the hardfork ?

just download an updated wallet which includes the "fix" - then download the blockchain snapshot and try to sync up to the latest block...it will get stuck at 2007364

[phm87]

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.

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

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.

[ocminer]

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.

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

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