Bitcoin Forum
November 13, 2024, 07:37:44 PM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 ... 88 »
  Print  
Author Topic: Network Attack on XVG / VERGE  (Read 29513 times)
Hunterwolfie
Full Member
***
Offline Offline

Activity: 294
Merit: 101


View Profile
April 05, 2018, 06:39:47 AM
 #241

Yes but not sure how this attack works because it showed I was still earning. Just no payment happening.

***triple facepalm***
misospider
Newbie
*
Offline Offline

Activity: 96
Merit: 0


View Profile
April 05, 2018, 06:39:53 AM
 #242

Devs' incompetency... Angry
skagos
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
April 05, 2018, 06:41:43 AM
 #243

Yes but not sure how this attack works because it showed I was still earning. Just no payment happening.

Just FYI, the attack is active again since hours:

etBestChain: new best=0000000014199bb479e4  height=2024581  trust=2024582  date=04/05/18 04:12:23
ProcessBlock: ACCEPTED (scrypt)
received block 0000000005ea72a30c18
SetBestChain: new best=0000000005ea72a30c18  height=2024582  trust=2024583  date=04/05/18 05:45:42
ProcessBlock: ACCEPTED (scrypt)
received block 000000000cc5ddc0c405
SetBestChain: new best=000000000cc5ddc0c405  height=2024583  trust=2024584  date=04/05/18 04:12:24
ProcessBlock: ACCEPTED (scrypt)
received block 000000001e3596e79f46
SetBestChain: new best=000000001e3596e79f46  height=2024584  trust=2024585  date=04/05/18 05:45:43
ProcessBlock: ACCEPTED (scrypt)
received block 000000000bc74932f097
SetBestChain: new best=000000000bc74932f097  height=2024585  trust=2024586  date=04/05/18 04:12:25
ProcessBlock: ACCEPTED (scrypt)
received block 0000000018b6b325f06e
SetBestChain: new best=0000000018b6b325f06e  height=2024586  trust=2024587  date=04/05/18 05:45:44
ProcessBlock: ACCEPTED (scrypt)
received block 000000000415c5743e39
SetBestChain: new best=000000000415c5743e39  height=2024587  trust=2024588  date=04/05/18 04:12:26
ProcessBlock: ACCEPTED (scrypt)
received block 000000000a26a20a9739
SetBestChain: new best=000000000a26a20a9739  height=2024588  trust=2024589  date=04/05/18 05:45:45
ProcessBlock: ACCEPTED (scrypt)
received block 0000000016f52c223832
SetBestChain: new best=0000000016f52c223832  height=2024589  trust=2024590  date=04/05/18 04:12:27
ProcessBlock: ACCEPTED (scrypt)
received block 000000000e03064ef101
SetBestChain: new best=000000000e03064ef101  height=2024590  trust=2024591  date=04/05/18 04:12:28
ProcessBlock: ACCEPTED (scrypt)
received block 000000001db8e8120873
SetBestChain: new best=000000001db8e8120873  height=2024591  trust=2024592  date=04/05/18 04:12:29
ProcessBlock: ACCEPTED (scrypt)
received block 000000000a5d54a57c66
SetBestChain: new best=000000000a5d54a57c66  height=2024592  trust=2024593  date=04/05/18 05:45:48
ProcessBlock: ACCEPTED (scrypt)
received block 000000000fb646d4be87
SetBestChain: new best=000000000fb646d4be87  height=2024593  trust=2024594  date=04/05/18 04:12:30
ProcessBlock: ACCEPTED (scrypt)
received block 000000000483413c5790
SetBestChain: new best=000000000483413c5790  height=2024594  trust=2024595  date=04/05/18 05:45:49
ProcessBlock: ACCEPTED (scrypt)
received block 000000001bd339af32af
SetBestChain: new best=000000001bd339af32af  height=2024595  trust=2024596  date=04/05/18 04:12:31
ProcessBlock: ACCEPTED (scrypt)
received block 0000000008a51eee47a9
SetBestChain: new best=0000000008a51eee47a9  height=2024596  trust=2024597  date=04/05/18 05:45:50
ProcessBlock: ACCEPTED (scrypt)
received block 000000001fb6b0083e10
SetBestChain: new best=000000001fb6b0083e10  height=2024597  trust=2024598  date=04/05/18 04:12:32
ProcessBlock: ACCEPTED (scrypt)
received block 00000000088392c64556
SetBestChain: new best=00000000088392c64556  height=2024598  trust=2024599  date=04/05/18 05:45:51
ProcessBlock: ACCEPTED (scrypt)
received block 000000000a9fc220f36a
SetBestChain: new best=000000000a9fc220f36a  height=2024599  trust=2024600  date=04/05/18 04:12:33

I've stopped all suprnova pools
invisiblefriend321
Member
**
Offline Offline

Activity: 174
Merit: 10


View Profile
April 05, 2018, 06:49:06 AM
 #244

And to think I was getting a good deal at .05 cents Cheesy

u r getting amazing deal

really

ocminer (OP)
Legendary
*
Offline Offline

Activity: 2688
Merit: 1240



View Profile WWW
April 05, 2018, 06:56:31 AM
 #245

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

suprnova pools - reliable mining pools - #suprnova on freenet
https://www.suprnova.cc - FOLLOW us @ Twitter ! twitter.com/SuprnovaPools
boxalex
Member
**
Offline Offline

Activity: 420
Merit: 13


View Profile
April 05, 2018, 06:58:45 AM
 #246

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
ocminer (OP)
Legendary
*
Offline Offline

Activity: 2688
Merit: 1240



View Profile WWW
April 05, 2018, 07:01:28 AM
 #247

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

suprnova pools - reliable mining pools - #suprnova on freenet
https://www.suprnova.cc - FOLLOW us @ Twitter ! twitter.com/SuprnovaPools
shubham412302
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
April 05, 2018, 07:05:59 AM
 #248

The only profitable coin got hacked Cry Cry Cry. Moved to raven which is 2nd most profitable.
boxalex
Member
**
Offline Offline

Activity: 420
Merit: 13


View Profile
April 05, 2018, 07:07:39 AM
 #249

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

only about 1.000.000.000 left and the maxsupply is reached and the issue gets solved its own :-)
Ghrand
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
April 05, 2018, 07:10:10 AM
 #250

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

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.  Roll Eyes

idolism
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
April 05, 2018, 07:13:01 AM
 #251

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://bitcointalk.org/index.php?action=profile;u=1117726


---------

Mentions of the address DBfVheAAcBd5X6tA2YpZMyNBvcn434oGqR


https://verge-blockchain.info/address/DBfVheAAcBd5X6tA2YpZMyNBvcn434oGqR

https://bitcointalk.org/index.php?topic=2172845.860

BlackPrapor
Hero Member
*****
Offline Offline

Activity: 628
Merit: 504



View Profile WWW
April 05, 2018, 07:20:59 AM
 #252

Could've just turn off scrypt algo support for now, until its all got fixed.

There is no place like 127.0.0.1
In blockchain we trust
testingtester
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
April 05, 2018, 07:25:15 AM
 #253

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)
ocminer (OP)
Legendary
*
Offline Offline

Activity: 2688
Merit: 1240



View Profile WWW
April 05, 2018, 07:25:39 AM
 #254

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

suprnova pools - reliable mining pools - #suprnova on freenet
https://www.suprnova.cc - FOLLOW us @ Twitter ! twitter.com/SuprnovaPools
sxott72
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
April 05, 2018, 07:25:52 AM
 #255

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?
ocminer (OP)
Legendary
*
Offline Offline

Activity: 2688
Merit: 1240



View Profile WWW
April 05, 2018, 07:28:37 AM
 #256

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 ...

suprnova pools - reliable mining pools - #suprnova on freenet
https://www.suprnova.cc - FOLLOW us @ Twitter ! twitter.com/SuprnovaPools
andro hac
Sr. Member
****
Offline Offline

Activity: 574
Merit: 254



View Profile
April 05, 2018, 07:31:46 AM
 #257

Verge Is Forced to Fork After Suffering a 51% Attack https://news.bitcoin.com/verge-is-forced-to-fork-after-suffering-a-51-attack/ …  Cheesy
yeswepump
Legendary
*
Offline Offline

Activity: 1162
Merit: 1011



View Profile
April 05, 2018, 07:33:02 AM
 #258

Just found out about this event. So is the attack still ongoing and the chain is at risk?
siege3967
Jr. Member
*
Offline Offline

Activity: 42
Merit: 1


View Profile
April 05, 2018, 07:39:39 AM
 #259

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.
Surging Chaos
Newbie
*
Offline Offline

Activity: 46
Merit: 0


View Profile
April 05, 2018, 07:41:14 AM
 #260

Verge Is Forced to Fork After Suffering a 51% Attack https://news.bitcoin.com/verge-is-forced-to-fork-after-suffering-a-51-attack/ …  Cheesy

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?
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 ... 88 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!