Topic: Network Attack on XVG / VERGE - page 75. (Read 29513 times)
This is a pretty interesting event going on here. Attack vector of sopping up all seconds of time during a set block of time is pretty cool.
here is the best piece of advice i can give to anyone.... BUY THE FN DIP!!!!....
Go buy that Centra and BitConnect dip while you're at it.
So did I get it right: The devs just need to fix this timestamp bug and reset to the last legit block? The hacker(s) even cannot move their illegit coins? (btw: binance has blocked transfers to it, anyways)
It's actually not so hard to get it fixed and even the hackers coins removed:
Simply exclude all blocks from the blockchain mined with a "bad timestamp" e.g. don't accept blocks where the next block is more than an hour ahead of the previous one.
By doing it this way, you'd already see from the beginning which blocks "belong" to the attacker and which blocks are legit. Then you would simply set checkpoints to exclude the malicious chain and only include legit blocks again.
It's definitely possible.. it requires some work but it's possible.. Definitely better than letting one person get away with > 20 Million XVG ...
That's good news. So just a matter of time. Thanx for answer and I'm gonna return to your x17-xvg pool as soon as it is up again.
Verge Is Forced to Fork After Suffering a 51% Attack https://news.bitcoin.com/verge-is-forced-to-fork-after-suffering-a-51-attack/ … 
This isn't even a 51% attack. This is more like a 100% attack. Who needs hashing power when you can just magically orphan all legit blocks?
Can someone elaborate whats happening. ExplainLikeim5. Thanks =)
Your best to read through the whole post to get a good understanding of what has happened.
On another note, this is hardly the first crypto to be hit like this and most probably won't be the last..... don't really see why people are freaking out so badly.... shit happens like this all the time.... Welcome to crypto.
Stop being so nonchalant. You're behaving like Sunerok. It's actually quite a big deal.
clearly you have not been in crypto that long lol..... i am not going to panic or worry.... a fix will be released as it has always been done with soo many different crypto coins. i have seen this happen so many times and everything has always recovered at the end of the day, may take weeks or months but it eventually recovers. the team is working on a fix just like many other coin devs did...
Stop embarrassing yourself. These sort of attacks are not common at least not in this way with exploitable code. Stop comparing with eth. You have an idiot dev who can't calculate 15 minutes and copy-pastes all the code for the coin (including the "fix" they tried from peercoin which he just copy pasted without even editing the comment) and they have vitalik.
Just found out about this event. So is the attack still ongoing and the chain is at risk?
Verge Is Forced to Fork After Suffering a 51% Attack https://news.bitcoin.com/verge-is-forced-to-fork-after-suffering-a-51-attack/ …
So did I get it right: The devs just need to fix this timestamp bug and reset to the last legit block? The hacker(s) even cannot move their illegit coins? (btw: binance has blocked transfers to it, anyways)
It's actually not so hard to get it fixed and even the hackers coins removed:
Simply exclude all blocks from the blockchain mined with a "bad timestamp" e.g. don't accept blocks where the next block is more than an hour ahead of the previous one.
By doing it this way, you'd already see from the beginning which blocks "belong" to the attacker and which blocks are legit. Then you would simply set checkpoints to exclude the malicious chain and only include legit blocks again.
It's definitely possible.. it requires some work but it's possible.. Definitely better than letting one person get away with > 20 Million XVG ...
Ty. Will it kill the project or is it an easy fix? If it hard forks, do I need my coins in wallet off the exchanges?
Could've just turn off scrypt algo support for now, until its all got fixed.
You can do that with every algo ... scrypt is just easy to rent at nicehash and that's probably why the attacker used it
So did I get it right: The devs just need to fix this timestamp bug and reset to the last legit block? The hacker(s) even cannot move their illegit coins? (btw: binance has blocked transfers to it, anyways)
Could've just turn off scrypt algo support for now, until its all got fixed.
I just made quick research on few addresses that continue to exploit the bug.
D8Z2APfnC68K461amMR6v4faaiCxWiY1rE - user phm87
https://verge-blockchain.info/address/D8Z2APfnC68K461amMR6v4faaiCxWiY1rE
https://forum.unimining.net/viewtopic.php?t=4
https://github.com/phm87
https://avatars0.githubusercontent.com/u/31578435?s=460&v=4
https://bitcointalksearch.org/user/phm87-1117726
---------
Mentions of the address DBfVheAAcBd5X6tA2YpZMyNBvcn434oGqR
https://verge-blockchain.info/address/DBfVheAAcBd5X6tA2YpZMyNBvcn434oGqR
https://bitcointalk.org/index.php?topic=2172845.860
D8Z2APfnC68K461amMR6v4faaiCxWiY1rE - user phm87
https://verge-blockchain.info/address/D8Z2APfnC68K461amMR6v4faaiCxWiY1rE
https://forum.unimining.net/viewtopic.php?t=4
https://github.com/phm87
https://avatars0.githubusercontent.com/u/31578435?s=460&v=4
https://bitcointalksearch.org/user/phm87-1117726
---------
Mentions of the address DBfVheAAcBd5X6tA2YpZMyNBvcn434oGqR
https://verge-blockchain.info/address/DBfVheAAcBd5X6tA2YpZMyNBvcn434oGqR
https://bitcointalk.org/index.php?topic=2172845.860
I skimmed the logs and saw the attacker started the new attack at around block 2014060 and stopped just now at block 2026196
..
12k blocks this time Lets say 10k... so additional 10.000 + 1560 = 15.600.000
..
12k blocks this time Lets say 10k... so additional 10.000 + 1560 = 15.600.000
Well, we know from their github that the dev can't do math but I'm sure they will show up and say it's some other low number of XVG for more damage control.
I skimmed the logs and saw the attacker started the new attack at around block 2014060 and stopped just now at block 2026196
..
12k blocks this time Lets say 10k... so additional 10.000 + 1560 = 15.600.000 XVG
..
12k blocks this time Lets say 10k... so additional 10.000 + 1560 = 15.600.000 XVG
only about 1.000.000.000 left and the maxsupply is reached and the issue gets solved its own :-)
The only profitable coin got hacked 
. Moved to raven which is 2nd most profitable.
. Moved to raven which is 2nd most profitable.
I skimmed the logs and saw the attacker started the new attack at around block 2014060 and stopped just now at block 2026196
..
12k blocks this time Lets say 10k... so additional 10.000 + 1560 = 15.600.000 XVG
..
12k blocks this time Lets say 10k... so additional 10.000 + 1560 = 15.600.000 XVG
Yes but not sure how this attack works because it showed I was still earning. Just no payment happening.
the blocks/shares on the legit pools get orphaned due the hack => no income
Yes but not sure how this attack works because it showed I was still earning. Just no payment happening.
The attack works like this:
The attacker replaces the legit blockchain, with legit high difficulty blocks, with his low diff blocks, invalidating all legit blocks (orphans).
That means no coins can be moved but his... He's not accepting any other transactions...
He'd need to stop in order to get the coins moved again.
The rest of the details is in post 1
And to think I was getting a good deal at .05 cents
u r getting amazing deal
really
Jump to: