Bitcoin Forum
September 19, 2019, 05:58:20 PM *
News: Latest Bitcoin Core release: 0.18.1 [Torrent]
 
   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 64 65 66 67 ... 88 »
  Print  
Author Topic: Network Attack on XVG / VERGE  (Read 28684 times)
samspaces
Legendary
*
Offline Offline

Activity: 1346
Merit: 1000


View Profile
April 05, 2018, 11:32:44 AM
 #321

Am I right in assuming that:

The network will see the longest chain in the network with sufficient nodes as the correct one, thereby validating the low difficulty blocks on the longest chain?
That would mean that the attacker has to have a lot of full nodes up and running, with which he/she privately mines.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
jl777B
Full Member
***
Offline Offline

Activity: 476
Merit: 133


View Profile
April 05, 2018, 11:34:38 AM
 #322

Am I right in assuming that:

The network will see the longest chain in the network with sufficient nodes as the correct one, thereby validating the low difficulty blocks on the longest chain?
That would mean that the attacker has to have a lot of full nodes up and running, with which he/she privately mines.
if just one node gets the attacker's longest chain, then it should propagate to all the other nodes. depending on the nature of the exploit, it is possible attacker doesnt have any large hashrate and is just using a single node to broadcast the blocks into the network

klimauk
Full Member
***
Offline Offline

Activity: 186
Merit: 103

Crypto maniac - HODL


View Profile
April 05, 2018, 11:34:42 AM
 #323

The most important thing is to fix it now. We can't change the past but we can change the future.

Hodler <> seller <> buyer
Nakasoshi
Member
**
Offline Offline

Activity: 156
Merit: 10

Ein Merit wäre wunderbar ;P


View Profile
April 05, 2018, 11:35:25 AM
 #324

I'm amazed at how bad the Devs have handled this important situation. Probs to OCMiner for letting us know about the hack/exploit  Smiley



Yeah so i am not so in the materia of programming so is this a bad thing for verge and how long will it take for their porgammers to fix that issue

kickboxer
Member
**
Offline Offline

Activity: 92
Merit: 10


View Profile
April 05, 2018, 11:35:40 AM
 #325

Hey Does this hard fork mean the verge lost on coinpuch attack can be claimed back???/
samspaces
Legendary
*
Offline Offline

Activity: 1346
Merit: 1000


View Profile
April 05, 2018, 11:37:23 AM
 #326

Am I right in assuming that:

The network will see the longest chain in the network with sufficient nodes as the correct one, thereby validating the low difficulty blocks on the longest chain?
That would mean that the attacker has to have a lot of full nodes up and running, with which he/she privately mines.
if just one node gets the attacker's longest chain, then it should propagate to all the other nodes. depending on the nature of the exploit, it is possible attacker doesnt have any large hashrate and is just using a single node to broadcast the blocks into the network



Seriously? Quite amazing that doesn't happen more often.
jl777B
Full Member
***
Offline Offline

Activity: 476
Merit: 133


View Profile
April 05, 2018, 11:43:44 AM
 #327

Am I right in assuming that:

The network will see the longest chain in the network with sufficient nodes as the correct one, thereby validating the low difficulty blocks on the longest chain?
That would mean that the attacker has to have a lot of full nodes up and running, with which he/she privately mines.
if just one node gets the attacker's longest chain, then it should propagate to all the other nodes. depending on the nature of the exploit, it is possible attacker doesnt have any large hashrate and is just using a single node to broadcast the blocks into the network



Seriously? Quite amazing that doesn't happen more often.
most coins dont have such an exploit available
chrysophylax
Legendary
*
Offline Offline

Activity: 1624
Merit: 1076


--- ChainWorks Industries ---


View Profile WWW
April 05, 2018, 11:50:15 AM
 #328

Looks like 2 * 15 sec, not 15 minutes.

Very funny. Are there some sort of code review in Verge?

Newbies at this thread are Verge code reviewers

hehehe ...

Ahem!

#crysx

Exchange - https://www.zapple.com/exchange/ . CWI-Thread - https://bitcointalk.org/index.php?topic=1563601 . EMail - crysx@gnxs.com . CWI-WebSite - https://chainworksindustries.com/ . CWI-Mine - http://chrysolite.chainworksindustries.com/ . CWI-Pyroxene (theMine) - http://pyroxene.chainworksindustries.com/ . GRN - Gfz2cXMkhMZYWSFvLEMnM8bXk7X5Mtq2J2
Dogedarkdev
Legendary
*
Offline Offline

Activity: 1428
Merit: 1005


$XVG - The Standard in Privacy Based Crypto


View Profile WWW
April 05, 2018, 12:16:54 PM
 #329

we were going to reduce the 2 hour drift to 15 minutes, then i brazenly chose 30 seconds. 2 * 15 is 30 seconds which is our blocktime. we decided not to go with that as blocktimes do vary a bit.

we've done a complete rewrite and will be pushing it shortly and contacting our pool ops and exchanges.

i love seeing so many people who aren't even involved in verge talking about it though ;]

_///// [XVG] ★★★★★WE ARE ON  THE VERGE ★★★★★ [MULTI-ALGO] /////_
_///// TOR // I2P // LINUX . WINDOWS . MAC . ANDROID . ELECTRUM . WEBWALLET . GITHUB // WEBSITE // RADIO // IRC /////_
sunc
Newbie
*
Offline Offline

Activity: 102
Merit: 0


View Profile
April 05, 2018, 12:25:46 PM
 #330

Well. Will these actions help to solve the problem so that it does not arise in the future. To break the chain it became impossible and the blocks met the conditions.
BillionDollarMan
Member
**
Offline Offline

Activity: 210
Merit: 10


View Profile
April 05, 2018, 12:30:35 PM
 #331

rip. will this mean the end of verge?

yes

P.S. Dont worry, Verge will be announcing the name of partnership on April 16th        Grin Grin                             
https://www.youtube.com/watch?v=7-LQoskTbqc&t=15s

Marketing and partnerships are more important than tech side, dont worry, hehe

Of course but don't forget to sell before actual announcement. Buy the rumor and sell the news as always  Grin
chrysophylax
Legendary
*
Offline Offline

Activity: 1624
Merit: 1076


--- ChainWorks Industries ---


View Profile WWW
April 05, 2018, 12:31:05 PM
 #332

Well. Will these actions help to solve the problem so that it does not arise in the future. To break the chain it became impossible and the blocks met the conditions.

Highly unlikely ...

Anyone that has enough hashpower and the knowledge to manipulate the blockchain in this way, CAN do this to almost any coin. Though I still believe that it could be miners that unwittingly set their farms to auto destruction mode and let loose.

No one can blame the devs AND expect them to be responsible for it when the hashpower is completely out of their hands. The devs only method of defense is to write code that will 'try' and combat this issue.

#crysx

Exchange - https://www.zapple.com/exchange/ . CWI-Thread - https://bitcointalk.org/index.php?topic=1563601 . EMail - crysx@gnxs.com . CWI-WebSite - https://chainworksindustries.com/ . CWI-Mine - http://chrysolite.chainworksindustries.com/ . CWI-Pyroxene (theMine) - http://pyroxene.chainworksindustries.com/ . GRN - Gfz2cXMkhMZYWSFvLEMnM8bXk7X5Mtq2J2
ocminer
Legendary
*
Offline Offline

Activity: 2408
Merit: 1233



View Profile WWW
April 05, 2018, 12:32:28 PM
Merited by maleemk (5)
 #333

Well. Will these actions help to solve the problem so that it does not arise in the future. To break the chain it became impossible and the blocks met the conditions.

Highly unlikely ...

Anyone that has enough hashpower and the knowledge to manipulate the blockchain in this way, CAN do this to almost any coin. Though I still believe that it could be miners that unwittingly set their farms to auto destruction mode and let loose.

No one can blame the devs AND expect them to be responsible for it when the hashpower is completely out of their hands. The devs only method of defense is to write code that will 'try' and combat this issue.

#crysx


This is totally wrong. This exploit has been used with myriad and digibyte already and can be patched successfully

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

Activity: 1
Merit: 0


View Profile
April 05, 2018, 12:33:19 PM
 #334

Well. Will these actions help to solve the problem so that it does not arise in the future. To break the chain it became impossible and the blocks met the conditions.

Highly unlikely ...

Anyone that has enough hashpower and the knowledge to manipulate the blockchain in this way, CAN do this to almost any coin. Though I still believe that it could be miners that unwittingly set their farms to auto destruction mode and let loose.

No one can blame the devs AND expect them to be responsible for it when the hashpower is completely out of their hands. The devs only method of defense is to write code that will 'try' and combat this issue.

#crysx

But how can you manipulate the blockchain?
metallicelmo
Sr. Member
****
Offline Offline

Activity: 826
Merit: 252



View Profile
April 05, 2018, 12:36:41 PM
 #335

Well. Will these actions help to solve the problem so that it does not arise in the future. To break the chain it became impossible and the blocks met the conditions.

Highly unlikely ...

Anyone that has enough hashpower and the knowledge to manipulate the blockchain in this way, CAN do this to almost any coin. Though I still believe that it could be miners that unwittingly set their farms to auto destruction mode and let loose.

No one can blame the devs AND expect them to be responsible for it when the hashpower is completely out of their hands. The devs only method of defense is to write code that will 'try' and combat this issue.

#crysx

But how can you manipulate the blockchain?

Well really attacking a blockchain could be done with a 51% attack but you need serious mining power. This way your mining rig is faster then anyone else mining at that moment and causes you to "win" all the blocks, something like that.
jl777B
Full Member
***
Offline Offline

Activity: 476
Merit: 133


View Profile
April 05, 2018, 12:40:59 PM
 #336

Well. Will these actions help to solve the problem so that it does not arise in the future. To break the chain it became impossible and the blocks met the conditions.

Highly unlikely ...

Anyone that has enough hashpower and the knowledge to manipulate the blockchain in this way, CAN do this to almost any coin. Though I still believe that it could be miners that unwittingly set their farms to auto destruction mode and let loose.

No one can blame the devs AND expect them to be responsible for it when the hashpower is completely out of their hands. The devs only method of defense is to write code that will 'try' and combat this issue.

#crysx


This is totally wrong. This exploit has been used with myriad and digibyte already and can be patched successfully
A lot of misinformation that this was a 51% hashrate attack. my understanding is that it isnt based on any massive hashrate and also that not any attempt to double spend is being made, just mining lots of blocks

you seem to know far more than anybody else here about this specific attack, can you confirm it is not based on 51%+ hashrate.
cryptotum88
Full Member
***
Offline Offline

Activity: 379
Merit: 100


View Profile
April 05, 2018, 12:42:36 PM
 #337

So this attack was basically fixed, stop adding FUD.

Now talking about important matters:

will suprnova start mining xvg/lyra again? any ETA?
coinfoundry
Full Member
***
Offline Offline

Activity: 252
Merit: 100

COINFOUNDRY.ORG


View Profile WWW
April 05, 2018, 12:45:43 PM
 #338

So this attack was basically fixed, stop adding FUD.

Now talking about important matters:

will suprnova start mining xvg/lyra again? any ETA?

It was not fixed correctly. The hastily commited fix was actually causing even more problems. Stop patronizing people if you don't know what you are talking about.

chrysophylax
Legendary
*
Offline Offline

Activity: 1624
Merit: 1076


--- ChainWorks Industries ---


View Profile WWW
April 05, 2018, 12:49:16 PM
 #339

Well. Will these actions help to solve the problem so that it does not arise in the future. To break the chain it became impossible and the blocks met the conditions.

Highly unlikely ...

Anyone that has enough hashpower and the knowledge to manipulate the blockchain in this way, CAN do this to almost any coin. Though I still believe that it could be miners that unwittingly set their farms to auto destruction mode and let loose.

No one can blame the devs AND expect them to be responsible for it when the hashpower is completely out of their hands. The devs only method of defense is to write code that will 'try' and combat this issue.

#crysx


This is totally wrong. This exploit has been used with myriad and digibyte already and can be patched successfully

Even after patching mate ...

With the right amount of hashrate and knowhow, you can force the blockchain to do it all over again.

#crysx

Exchange - https://www.zapple.com/exchange/ . CWI-Thread - https://bitcointalk.org/index.php?topic=1563601 . EMail - crysx@gnxs.com . CWI-WebSite - https://chainworksindustries.com/ . CWI-Mine - http://chrysolite.chainworksindustries.com/ . CWI-Pyroxene (theMine) - http://pyroxene.chainworksindustries.com/ . GRN - Gfz2cXMkhMZYWSFvLEMnM8bXk7X5Mtq2J2
cryptotum88
Full Member
***
Offline Offline

Activity: 379
Merit: 100


View Profile
April 05, 2018, 12:51:32 PM
 #340

So this attack was basically fixed, stop adding FUD.

Now talking about important matters:

will suprnova start mining xvg/lyra again? any ETA?

It was not fixed correctly. The hastily commited fix was actually causing even more problems. Stop patronizing people if you don't know what you are talking about.

Ok DEV get the C++ code (that I have already briefly reviewed) and EXPLAIN to me WHY this not fix the issue and what are these "more" problems because this: "It was not fixed correctly. The hastily commited fix was actually causing even more problems" is a FUD answer.
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 64 65 66 67 ... 88 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!