Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 16 submissions in the queue.
posted by martyb on Wednesday January 09 2019, @06:07AM   Printer-friendly
from the double-double-toil-and-trouble-fire-burn-and-caldron-bubble dept.

Submitted via IRC for SoyCow1984

Cryptocurrency trading portal Coinbase delisted today the Ethereum Classic (ETC) currency after detecting a series of double-spend attacks over the last three days.

In layman terms, double-spend attacks are when a malicious actor gains the majority computational power inside a blockchain, which they then use to enforce unauthorized transactions over legitimate ones.

According to a security alert published today by Coinbase security engineer Mark Nesbitt, this is exactly what's been happening on the Ethereum Classic blockchain for the past three days, since January 5.

[...] The ETC cryptocurrency was created in August 2016, shortly after the infamous DAO hack, and was one of the first forks of the more established Ether (ETH).

[...] Update, January 8, 06:00 AM ET: Bitfly, a fellow cryptocurrency trading platform, has also confirmed Coinbase's report. So did the Ethereum Classic team, which was immediately criticized for not spotting the attack on its own network in the first place. Coinbase, too, was criticized, but for failing to reveal the double-spend attacks on Saturday when they first happened, leaving ETC users at risk for three days, for no good reason. Coinbase also updated its original report with details on another 12 double-spend attacks, bringing the total of stolen funds to 219,500 ETC (~$1.1 million).

Source: https://www.zdnet.com/article/coinbase-suspends-ethereum-classic-etc-trading-after-double-spend-attacks/


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1, Funny) by Anonymous Coward on Wednesday January 09 2019, @06:21AM (1 child)

    by Anonymous Coward on Wednesday January 09 2019, @06:21AM (#784003)

    Be the attacker :O

    Starting Score:    0  points
    Moderation   +1  
       Funny=1, Total=1
    Extra 'Funny' Modifier   0  

    Total Score:   1  
  • (Score: 0) by Anonymous Coward on Wednesday January 09 2019, @06:38AM

    by Anonymous Coward on Wednesday January 09 2019, @06:38AM (#784006)

    Not kidding. At first glance it seems easy, just monitor the input hashes[1] in every new block for duplicates, but if no one involved here was monitoring for it there must be some issue.

    [1] https://en.bitcoin.it/wiki/Transaction [bitcoin.it]