Network Attack on XVG / VERGE

[bododk]

Looking at the blockexplorer still no fix. 5 days of instamining and counting. gg wp

can u justify what u say ?

[1714042261]

1714042261

[Hoshingen]

Looking at the blockexplorer still no fix. 5 days of instamining and counting. gg wp

can u justify what u say ?

The blockexplorer still shows large amounts of blocks being added every minute: https://verge-blockchain.info/

[siege3967]

Code:

2042609	1560	1
Sun, 08 Apr 2018 06:21:39 GMT	1560	1
1fa29cfe23032fe5b58ef659bd64225259806be88086c7c604408d19cbfb7d31	1560	1
2042608	1560	1
Sun, 08 Apr 2018 06:21:38 GMT	1560	1
419a3343c0a29a4504de657ce23cd526bb8ac504bd1a79c9f61f973e4ce07718	1560	1
2042607	1560	1
Sun, 08 Apr 2018 06:21:37 GMT	1560	1
04da4f094bd24c962ac829051203c21d7355a3dfd1df81b4b3f50a048e37fe58	1560	1
2042606	1560	1
Sun, 08 Apr 2018 06:22:59 GMT	1560	1
3021c04b82228e1283b2ba522da25fc07e9ea92e9ee296eed2cc54956cbc2acc	1560	1
2042605	1560	1
Sun, 08 Apr 2018 06:20:58 GMT	1560	1
087bdfcc9f4ae669a4af66ebd6bee3a691d3d79a5f4d630e6d856163a08e2163	1560	1
2042604	3120	10
Sun, 08 Apr 2018 06:22:31 GMT	3120	10
7fc1437e81fefba53d86d822b4f4a5dfc05ef3270e7999fc08680b5e1611b2ec	1560.1	1
a150f697a39f5e832ac368f5039f30e0ecd50f91b8506f6389ade25bf8c31127	1559.9	9
2042603	1560	1
Sun, 08 Apr 2018 06:20:05 GMT	1560	1
45c948012f013ffbab90bc088edf2fa2c1393a6607d4800321b9dec6306dfdd1	1560	1
2042602	1560	1
Sun, 08 Apr 2018 06:22:01 GMT	1560	1
355bcbd439294bed7d4e3ddbc47ec807429462ff7ca2c40355c2ece521c00902	1560	1
2042601	1560	1
Sun, 08 Apr 2018 06:21:54 GMT	1560	1
1b26a58d58edaba660153f0735e9a01df63b0ca24551ec21145dea644c6fe338	1560	1
2042600	1560	1
Sun, 08 Apr 2018 06:21:48 GMT	1560	1
fe530f4e0f36043d102a021ae2dc2d8c671621878ea8fe06d8c510345bafa845	1560	1

The timestamp of the blocks are everywhere...lower blockheight have future time than higher block height, and the blocks 2042605,2042606 as well as 2042607~2042609 all have 1s difference...sure it's fixed?

Dev said on vergecurrency reddit that "drifts are allowed. blocks are moving on time, and all different algos. the attack was only scrypt blocks, with a difficulty of 0.001"

9 blocks in around 2 minutes. Is that okay...? And lots of blocks 1 second away from each other.

[allavett]

Looking at the blockexplorer still no fix. 5 days of instamining and counting. gg wp

can u justify what u say ?

The blockexplorer still shows large amounts of blocks being added every minute: https://verge-blockchain.info/

You mean blocks or transactions?

[pnh_old]

The timers are allowed to drift, as you can see here:
http://antminepool.com/explorer/XVGB

things look great.

as you can see here, from the attack, they did not look so great:
http://antminepool.com/explorer/XVGB?start=2030000

you need to look at the difficulty the blocks are being mined with, they use to be 0.001 and now they are correct. no longer exploited so the fork has worked and it fixed the exploit.

After the update went out to the pools and exchanges at block 2040000 you will see that the exploit is no longer working.

http://antminepool.com/explorer/XVGB?start=2040000

the fork has been successfully completed at block 2042000 but if you check the blockchain one can tell that no more blocks have been mined using the exploit from 2040000 onward.
http://antminepool.com/explorer/XVGB?start=2040000

if you were to assume that all the block from when the attack started at block 2021000 up to block 2040000 that would mean 19000 blocks have been mined using the exploit.

19000 * 1560 (block reward size) = 29640000 XVG maximum that could have been mined. Again this assumed that all blocks were stolen which isn't the case.

Hopefully this answers some of your questions, as for what happens to the addresses where all these exploited blocks went to....we will have to wait for the official update from the verge team.

As i understand it some addresses might have been blocked with the exchanges and possibly as part of the fork. (don't quote me on this)

[Hellracer]

When does the Suprnova Pool start again with myriad-groestl?

There are only bad pools to dismantle suprnova pool was good.

The pool http://xvg-mg.idcray.com/ is constantly out of order.

Can anyone happen to tell the port for the Baikal Gaint X10 via the http://xvg-mg.idcray.com/ pool with the correct difficulty. 

Hope Suprnova will be back online soon

[ocminer]

When does the Suprnova Pool start again with myriad-groestl?

There are only bad pools to dismantle suprnova pool was good.

The pool http://xvg-mg.idcray.com/ is constantly out of order.

Can anyone happen to tell the port for the Baikal Gaint X10 via the http://xvg-mg.idcray.com/ pool with the correct difficulty. 

Hope Suprnova will be back online soon

Won't happen.

[vitaminas]

Problem was fixed indeed!

[Heguli97]

It's fixed guys! 

[Hellracer]

When does the Suprnova Pool start again with myriad-groestl?

There are only bad pools to dismantle suprnova pool was good.

The pool http://xvg-mg.idcray.com/ is constantly out of order.

Can anyone happen to tell the port for the Baikal Gaint X10 via the http://xvg-mg.idcray.com/ pool with the correct difficulty. 

Hope Suprnova will be back online soon

Won't happen.

The problems are already solved where is the problem now.

Can someone say the settings for the other pool for an X10 Miner difficulty port???

[vitaminas]

Problem was that he was spoofing the blocks and manage to lower their diff to almost 0 as you can see in this pic http://prntscr.com/j2gj3a. He started to exploit at block 2010040 and mined until around block 2038300 so around 28k blocks 43.6 million verge and not the ridiculous numbers that people where mentioning.

Now if you check http://antminepool.com/explorer/XVGB you can see that Diff as normalized it was actually already normal since block 2038300 around that. Either way the exploit is over and hopefully wont happen again. Let this be an example for other coins out there that i know they have the same issue and at least 1 of them is above Verge in marketcap. Cheers

[Slemicek]

When does the Suprnova Pool start again with myriad-groestl?

There are only bad pools to dismantle suprnova pool was good.

The pool http://xvg-mg.idcray.com/ is constantly out of order.

Can anyone happen to tell the port for the Baikal Gaint X10 via the http://xvg-mg.idcray.com/ pool with the correct difficulty. 

Hope Suprnova will be back online soon

Won't happen.

Not surprised after how xvg dev reacted.

[Deff]

He deceived time!

[boxalex]

Out of curiousity as i'am not a pool owner, but only a trader, miner and holder.

How did this attack effect the XVG pools?

For us miners its clear that we lost all the orphaned blocks we mined in this time.
How is it for the pools? Is it like they pay for nodes/blocks and lost all these from the attack?

Seriously, never looked further how the pool thingie, nodes and blocks actually work on the pool side.

[Hellracer]

XVG-MG pool mining different was changed for X10 ,plz check your miner.
http://xvg-mg.idcray.com 
#Vergecurrency #XVG #cryptocurrency

Algo=Myriad-Groestl


port        diff
10061     1-10000
10062     10-10000
10063     20-10000
10064     50
10065     100

What kind of shit, can someone help me find the right port for my Gaint X10

[typeplus]

It's fixed guys! 

Wow what a comforting peice of information   Crazy situation this, some people are just too damn smart.

[BitPotus]

Out of curiousity as i'am not a pool owner, but only a trader, miner and holder.

How did this attack effect the XVG pools?

For us miners its clear that we lost all the orphaned blocks we mined in this time.
How is it for the pools? Is it like they pay for nodes/blocks and lost all these from the attack?

Seriously, never looked further how the pool thingie, nodes and blocks actually work on the pool side.

We lost $12,800 plus an unknown opportunity cost that I estimate around $50,000 as a result of this issue.

It affected the pool because our pay-per-share rates are calculated using, in addition to coinbase value, transaction fees, and orphan rate, the difficulty.  Shares were worth hundreds of dollars during that time and the orphan rate was 100%.  We had to exercise our policy of paying customers LTC + 15% during the 4 hours we earned nothing, which amounted to $12,000 in losses, plus about $300 in salaries answering 150 support tickets about the issue, plus about $500 in developer time spent addressing the problem instead of preparing for the upgrades to our servers this weekend.

There was also a large opportunity cost caused by the negative publicity of exercising our LTC + 15% policy, and we now have about 10% fewer customers than we did before the Verge incident.  I'd estimate the lost profit by the bad publicity will be around $50,000 over the lifetime of the pool.

It's not surprising that pools aren't mining Verge anymore.  This is probably the worst thing to happen to us since Cryptsy's theft.  We were 17% of the Verge network before this happened.

As to the issue being "fixed," I hope people can understand our reluctance to mine this coin again.  We'll reevaluate in a few weeks or in May if there are no issues.

so honest pool operators get shafted while the "hacker" has been rewarded with millions of coins.

Lovely.

[boxalex]

Out of curiousity as i'am not a pool owner, but only a trader, miner and holder.

How did this attack effect the XVG pools?

For us miners its clear that we lost all the orphaned blocks we mined in this time.
How is it for the pools? Is it like they pay for nodes/blocks and lost all these from the attack?

Seriously, never looked further how the pool thingie, nodes and blocks actually work on the pool side.

We lost $12,800 plus an unknown opportunity cost that I estimate around $50,000 as a result of this issue.

It affected the pool because our pay-per-share rates are calculated using, in addition to coinbase value, transaction fees, and orphan rate, the difficulty.  Shares were worth hundreds of dollars during that time and the orphan rate was 100%.  We had to exercise our policy of paying customers LTC + 15% during the 4 hours we earned nothing, which amounted to $12,000 in losses, plus about $300 in salaries answering 150 support tickets about the issue, plus about $500 in developer time spent addressing the problem instead of preparing for the upgrades to our servers this weekend.

There was also a large opportunity cost caused by the negative publicity of exercising our LTC + 15% policy, and we now have about 10% fewer customers than we did before the Verge incident.  I'd estimate the lost profit by the bad publicity will be around $50,000 over the lifetime of the pool.

It's not surprising that pools aren't mining Verge anymore.  This is probably the worst thing to happen to us since Cryptsy's theft.  We were 17% of the Verge network before this happened.

As to the issue being "fixed," I hope people can understand our reluctance to mine this coin again.  We'll reevaluate in a few weeks or in May if there are no issues.

thx for the detailed and honest answer. Its about as i thought, but wasn't exactly sure about it.

[boxalex]

so honest pool operators get shafted while the "hacker" has been rewarded with millions of coins.

Lovely.

Seems like pool operators and most miners suffered the most on this.
The hacker(s) and Verge seem to be fine 

Too bad when a given company/product/project forgets about their backbone .....

[Gongolo]

so honest pool operators get shafted while the "hacker" has been rewarded with millions of coins.

Lovely.

Seems like pool operators and most miners suffered the most on this.
The hacker(s) and Verge seem to be fine 

Too bad when a given company/product/project forgets about their backbone .....

Exactly.
Imho the annoying thing is just this.