{"id":6414,"date":"2019-01-08T12:30:55","date_gmt":"2019-01-08T12:30:55","guid":{"rendered":"https:\/\/forklog.media\/?p=6414"},"modified":"2019-01-08T12:30:55","modified_gmt":"2019-01-08T12:30:55","slug":"ethereum-classic-developers-hope-to-get-a-full-picture-of-a-potential-51-attack-soon","status":"publish","type":"post","link":"https:\/\/forklog.com\/en\/ethereum-classic-developers-hope-to-get-a-full-picture-of-a-potential-51-attack-soon\/","title":{"rendered":"Ethereum Classic Developers Hope to Get a Full Picture of a Potential 51% Attack Soon"},"content":{"rendered":"<p>Ethereum Classic\u2019s (ETC) development team admitted a malicious attack on the network had taken place and hopes the full extent of the incident will be known rather soon than later.<!--more--><\/p>\n<p>According to at least two different block explorers, <a href=\"https:\/\/twitter.com\/etherchain_org\/status\/1082329360948969472\" target=\"_blank\" rel=\"noopener\">Bitfly<\/a> and <a href=\"https:\/\/blockscout.com\/etc\/mainnet\/reorgs\" target=\"_blank\" rel=\"noopener\">Blockscout<\/a>, Ethereum Classic saw more than 100 blocks \u201creorganized\u201d during a potential 51 percent attack late Sunday. At the same time, it was <a href=\"https:\/\/www.coinness.com\/news\/198264\" target=\"_blank\" rel=\"noopener\">reported<\/a> on Monday that an abnormal hash rate going into a single mining pool had been detected, potentially causing mass reorganizations (reorgs) of mined blocks.<\/p>\n<p>Ethereum Classic developers initially refuted such claims, however had to admit a cause for concerns at a later stage, urging exchanges and mining pools to increase the number of transaction confirmations.<\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"en\">\n<p dir=\"ltr\" lang=\"en\">To all exchanges and mining pools please allow a significantly higher confirmation time on withdrawals and deposits (+400)<\/p>\n<p>cc <a href=\"https:\/\/twitter.com\/OKEx?ref_src=twsrc%5Etfw\">@OKEx<\/a> <a href=\"https:\/\/twitter.com\/ExchangeXGroup?ref_src=twsrc%5Etfw\">@ExchangeXGroup<\/a> <a href=\"https:\/\/twitter.com\/HuobiGroup?ref_src=twsrc%5Etfw\">@HuobiGroup<\/a> <a href=\"https:\/\/twitter.com\/digifinex?ref_src=twsrc%5Etfw\">@digifinex<\/a> <a href=\"https:\/\/twitter.com\/binance?ref_src=twsrc%5Etfw\">@binance<\/a> <a href=\"https:\/\/twitter.com\/bitfinex?ref_src=twsrc%5Etfw\">@bitfinex<\/a> <a href=\"https:\/\/t.co\/m5cxcKBVXa\">https:\/\/t.co\/m5cxcKBVXa<\/a><\/p>\n<p>\u2014 Ethereum Classic (@eth_classic) <a href=\"https:\/\/twitter.com\/eth_classic\/status\/1082153023265112064?ref_src=twsrc%5Etfw\">January 7, 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>In a later deleted twit, ETC developers also said that ASIC manufacturing firm Linzhi had confirmed testing of the new 1,400\/Mh Ethash machines and that no double spends had been detected.<\/p>\n<p>Commenting on the situation, U.S.-based crypto exchange Coinbase wrote:<\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"en\">\n<p dir=\"ltr\" lang=\"en\">On 1\/5\/2019, Coinbase detected a deep chain reorganization of the Ethereum Classic blockchain that included a double spend. In order to protect customer funds, we immediately paused movements of these funds on the ETC blockchain. Read more here: <a href=\"https:\/\/t.co\/vCx89dz44m\">https:\/\/t.co\/vCx89dz44m<\/a><\/p>\n<p>\u2014 Coinbase (@coinbase) <a href=\"https:\/\/twitter.com\/coinbase\/status\/1082364714246582274?ref_src=twsrc%5Etfw\">January 7, 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Coinbase also said in its blog post that it detected some 88,500 ETC being double-spent (totaling some $460,000).<\/p>\n<p>Moreover, CoinDesk\u2019s reporter Nikhilesh De wrote on Monday evening that Linzhi director of operations Wolfgang Spraul refuted claims that Linzhi is involved in the reorg:<\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"en\">\n<p dir=\"ltr\" lang=\"en\">UPDATE: Linzhi Shenzhen director of ops Wolfgang Spraul refuted claims that Linzhi is involved in the reorg: &#8220;We are categorically denying such claims, they are entirely baseless and may be part of the attack itself.&#8221;<a href=\"https:\/\/t.co\/ZMUrzazr2p\">https:\/\/t.co\/ZMUrzazr2p<\/a><\/p>\n<p>\u2014 Nikhilesh De (@nikhileshde) <a href=\"https:\/\/twitter.com\/nikhileshde\/status\/1082388621133529091?ref_src=twsrc%5Etfw\">January 7, 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Ethereum Classic responded to Coinbase\u2019s claims saying that the exchange \u201cunfortunately did not connect with ETC personnel regarding the attack.\u201d<\/p>\n<p>On Tuesday morning the developers said that they made \u201cno attempt to hide or downplay recent events,\u201d adding that they hope to \u201cget a full picture of what actually took place.\u201d<\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"en\">\n<p dir=\"ltr\" lang=\"en\">To be clear we are making no attempt to hide or downplay recent events.<\/p>\n<p>Facts are facts and as the situation develops we&#8217;ll soon get a full picture of what actually took place.<br \/>\nLinzhi is testing ASICS. Coinbase reported double spends; both may be true.<\/p>\n<p>In time we will see. <a href=\"https:\/\/t.co\/bbq6eqIoiS\">https:\/\/t.co\/bbq6eqIoiS<\/a><\/p>\n<p>\u2014 Ethereum Classic (@eth_classic) <a href=\"https:\/\/twitter.com\/eth_classic\/status\/1082392663314202624?ref_src=twsrc%5Etfw\">January 7, 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>In response to the deep reorg, Kraken announced in an <a href=\"https:\/\/status.kraken.com\/incidents\/n31wl183hqmc\" target=\"_blank\" rel=\"noopener\">incident report<\/a> that it was increasing the number of confirmations required to make an ETC deposit. The same action was taken by Bitfly.<\/p>\n<p>Poloniex announced it was <a href=\"https:\/\/twitter.com\/Poloniex\/status\/1082374403185430528\" target=\"_blank\" rel=\"noopener\">disabling ETC wallets<\/a>, and it does not currently have a firm timeline on when they will be re-enabled.<\/p>\n<p>Follow ForkLog on <span style=\"text-decoration: underline;\"><a href=\" https:\/\/twitter.com\/forklog_en\/\" target=\"_blank\" rel=\"nofollow noopener\">Twitter<\/a><\/span> and <span style=\"text-decoration: underline;\"><a href=\"https:\/\/www.facebook.com\/forklogen\/\" target=\"_blank\" rel=\"nofollow noopener\"> Facebook<\/a><\/span>!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ethereum Classic\u2019s (ETC) development team admitted a malicious attack on the network had taken place and hopes the full extent of the incident will be known rather soon than later.<\/p>\n","protected":false},"author":1,"featured_media":6417,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"select":"1","news_style_id":"","cryptorium_level":"","_short_excerpt_text":"","creation_source":"human_written","_metatest_mainpost_news_update":false,"footnotes":""},"categories":[3],"tags":[941,476,148],"class_list":["post-6414","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news-and-analysis","tag-51-attack","tag-ethereum-classic","tag-security"],"aioseo_notices":[],"amp_enabled":true,"views":"639","promo_type":"1","layout_type":"","short_excerpt":"","is_update":"","_links":{"self":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/6414","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/comments?post=6414"}],"version-history":[{"count":3,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/6414\/revisions"}],"predecessor-version":[{"id":6418,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/6414\/revisions\/6418"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media\/6417"}],"wp:attachment":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media?parent=6414"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/categories?post=6414"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/tags?post=6414"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}