Coinbase Halts Ethereum Classic Trading - Revision history

Azoundria at 18:57, 1 May 2023

2023-05-01T18:57:27Z

← Older revision		Revision as of 12:57, 1 May 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/coinbasehaltsethereumclassictrading.php}}		{{Imported Case Study 2\|source=https://www.quadrigainitiative.com/casestudy/coinbasehaltsethereumclassictrading.php}}
	{{Unattributed ~~Citations~~}}		{{Unattributed Sources}}

	[[File:Coinbase.jpg\|thumb\|Coinbase]]The Ethereum Classic blockchain is vulnerable to 51% attacks due to the low hash power. Unknown victims (which may include some exchange platforms) fell victim to the attack and lost $5m.		[[File:Coinbase.jpg\|thumb\|Coinbase]]The Ethereum Classic blockchain is vulnerable to 51% attacks due to the low hash power. Unknown victims (which may include some exchange platforms) fell victim to the attack and lost $5m.
Line 8:		Line 8:
	While any customers holding Ethereum Classic would have temporarily lost access, there were no funds lost in this case.		While any customers holding Ethereum Classic would have temporarily lost access, there were no funds lost in this case.

	This exchange or platform is based in United States, or the incident targeted people primarily in United States.		This exchange or platform is based in United States, or the incident targeted people primarily in United States.<ref name="coindesk-3005" /><ref name="coindesk-3585" /><ref name="coinbaseblog-55" /><ref name="etherchainorgtwitter-3586" /><ref name="pastebin-3587" /><ref name="ethclassictwitter-3588" /><ref name="ethclassictwitter-3589" /><ref name="ethereumclassic-3006" /><ref name="newsdotbitcoin-3007" />
	<ref name="coindesk-3005" /><ref name="coindesk-3585" /><ref name="coinbaseblog-55" /><ref name="etherchainorgtwitter-3586" /><ref name="pastebin-3587" /><ref name="ethclassictwitter-3588" /><ref name="ethclassictwitter-3589" /><ref name="ethereumclassic-3006" /><ref name="newsdotbitcoin-3007" />

	== About Coinbase ==		== About Coinbase ==
Line 77:		Line 76:
	!Description		!Description
	\|-		\|-
	\|January 5th, 2019 ~~12:00:00 AM~~		\|January 5th, 2019
	\|Main Event		\|Main Event
	\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
Line 85:		Line 84:
	\|		\|
	\|}		\|}

			== Technical Details ==
			This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?

	== Total Amount Lost ==		== Total Amount Lost ==
Line 104:		Line 106:
	== Ongoing Developments ==		== Ongoing Developments ==
	What parts of this case are still remaining to be concluded?		What parts of this case are still remaining to be concluded?
			== General Prevention Policies ==
	== Prevention Policies ==
	The solution to mitigate 51% attacks is to increase block confirmation times and institute checkpoints, where all miners agree that transactions up to that point are valid. If a large reorganization occurs, it will be rejected by miners, and the attacker will simply lose the funds spent on the attack.		The solution to mitigate 51% attacks is to increase block confirmation times and institute checkpoints, where all miners agree that transactions up to that point are valid. If a large reorganization occurs, it will be rejected by miners, and the attacker will simply lose the funds spent on the attack.

Line 111:		Line 112:

	Platforms can protect themselves against 51% attacks by ensuring that they only deal with coins which aren't vulnerable to 51% attacks or use checkpoints, and have sufficient block confirmation requirements on deposits.		Platforms can protect themselves against 51% attacks by ensuring that they only deal with coins which aren't vulnerable to 51% attacks or use checkpoints, and have sufficient block confirmation requirements on deposits.
			== Individual Prevention Policies ==
			{{Prevention:Individuals:Placeholder}}

			{{Prevention:Individuals:End}}

			== Platform Prevention Policies ==
			{{Prevention:Platforms:Placeholder}}

			{{Prevention:Platforms:End}}

			== Regulatory Prevention Policies ==
			{{Prevention:Regulators:Placeholder}}

			{{Prevention:Regulators:End}}

	== References ==		== References ==
	<references><ref name="coindesk-3005">[https://www.coindesk.com/markets/2020/09/08/crypto-investors-have-ignored-three-straight-51-attacks-on-etc/ Crypto Investors Have Ignored Three Straight 51% Attacks on ETC] (Sep 10, 2021)</ref>		<references><ref name="coindesk-3005">[https://www.coindesk.com/markets/2020/09/08/crypto-investors-have-ignored-three-straight-51-attacks-on-etc/ Crypto Investors Have Ignored Three Straight 51% Attacks on ETC] (Sep 11, 2021)</ref>

	<ref name="coindesk-3585">[https://www.coindesk.com/markets/2019/01/07/coinbase-suspends-ethereum-classic-after-blockchain-history-rewrites/ CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data] (Sep 10, 2021)</ref>		<ref name="coindesk-3585">[https://www.coindesk.com/markets/2019/01/07/coinbase-suspends-ethereum-classic-after-blockchain-history-rewrites/ CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data] (Sep 11, 2021)</ref>

	<ref name="coinbaseblog-55">[https://blog.coinbase.com/ethereum-classic-etc-is-currently-being-51-attacked-33be13ce32de Deep Chain Reorganization Detected on Ethereum Classic (ETC)] (Feb 6, 2020)</ref>		<ref name="coinbaseblog-55">[https://blog.coinbase.com/ethereum-classic-etc-is-currently-being-51-attacked-33be13ce32de Deep Chain Reorganization Detected on Ethereum Classic (ETC)] (Feb 7, 2020)</ref>

	<ref name="etherchainorgtwitter-3586">[https://twitter.com/etherchain_org/status/1082329360948969472 @etherchain_org Twitter] (Sep 10, 2021)</ref>		<ref name="etherchainorgtwitter-3586">[https://twitter.com/etherchain_org/status/1082329360948969472 @etherchain_org Twitter] (Sep 11, 2021)</ref>

	<ref name="pastebin-3587">[https://~~pastebin~~.com/xtu1a1Kg 2019-01-08 04:00:33 UTC Reorg to #7261516 7cdf…dd47 (436f…f5fa a6c6…e657 1068…07 - Pastebin.com] (Sep 10, 2021)</ref>		<ref name="pastebin-3587">[https://pastebin.com/xtu1a1Kg 2019-01-08 04:00:33 UTC Reorg to #7261516 7cdf…dd47 (436f…f5fa a6c6…e657 1068…07 - Pastebin.com] (Sep 11, 2021)</ref>

	<ref name="ethclassictwitter-3588">[https://twitter.com/eth_classic/status/1082045223310483457 @eth_classic Twitter] (Sep 10, 2021)</ref>		<ref name="ethclassictwitter-3588">[https://twitter.com/eth_classic/status/1082045223310483457 @eth_classic Twitter] (Sep 11, 2021)</ref>

	<ref name="ethclassictwitter-3589">[https://twitter.com/eth_classic/status/1082313711027507200 @eth_classic Twitter] (Sep 10, 2021)</ref>		<ref name="ethclassictwitter-3589">[https://twitter.com/eth_classic/status/1082313711027507200 @eth_classic Twitter] (Sep 11, 2021)</ref>

	<ref name="ethereumclassic-3006">[https://ethereumclassic.org/ Ethereum Classic] (Sep 10, 2021)</ref>		<ref name="ethereumclassic-3006">[https://ethereumclassic.org/ Ethereum Classic] (Sep 11, 2021)</ref>

	<ref name="newsdotbitcoin-3007">[https://news.bitcoin.com/ethereum-classic-suffers-51-attack-again-delisting-risk-amplified/ Ethereum Classic Suffers 51% Attack Again: Delisting Risk Amplified – Security Bitcoin News] (Sep 10, 2021)</ref></references>		<ref name="newsdotbitcoin-3007">[https://news.bitcoin.com/ethereum-classic-suffers-51-attack-again-delisting-risk-amplified/ Ethereum Classic Suffers 51% Attack Again: Delisting Risk Amplified – Security Bitcoin News] (Sep 11, 2021)</ref></references>

Azoundria at 07:52, 17 February 2023

2023-02-17T07:52:17Z

← Older revision		Revision as of 01:52, 17 February 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/coinbasehaltsethereumclassictrading.php}}		{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/coinbasehaltsethereumclassictrading.php}}
			{{Unattributed Citations}}

	[[File:Coinbase.jpg\|thumb\|Coinbase]]The Ethereum Classic blockchain is vulnerable to 51% attacks due to the low hash power. Unknown victims (which may include some exchange platforms) fell victim to the attack and lost $5m.		[[File:Coinbase.jpg\|thumb\|Coinbase]]The Ethereum Classic blockchain is vulnerable to 51% attacks due to the low hash power. Unknown victims (which may include some exchange platforms) fell victim to the attack and lost $5m.
Line 8:		Line 9:

	This exchange or platform is based in United States, or the incident targeted people primarily in United States.		This exchange or platform is based in United States, or the incident targeted people primarily in United States.
			<ref name="coindesk-3005" /><ref name="coindesk-3585" /><ref name="coinbaseblog-55" /><ref name="etherchainorgtwitter-3586" /><ref name="pastebin-3587" /><ref name="ethclassictwitter-3588" /><ref name="ethclassictwitter-3589" /><ref name="ethereumclassic-3006" /><ref name="newsdotbitcoin-3007" />

	== About Coinbase ==		== About Coinbase ==
Line 55:		Line 57:

	Don't Include:		Don't Include:

	* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.		* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
	* Anything that wasn't reasonably knowable at the time of the event.		* Anything that wasn't reasonably knowable at the time of the event.
Line 77:		Line 78:
	\|-		\|-
	\|January 5th, 2019 12:00:00 AM		\|January 5th, 2019 12:00:00 AM
	\|~~First~~ Event		\|Main Event
	\|~~This is an expanded~~ description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
	\|-
	\|
	\|
	\|
	\|-		\|-
	\|		\|
Line 90:		Line 87:

	== Total Amount Lost ==		== Total Amount Lost ==
	~~The total amount~~ lost ~~is unknown~~.		No funds were lost.

	How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?		How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?
Line 101:		Line 98:

	== Total Amount Recovered ==		== Total Amount Recovered ==
	~~It is unknown how much was~~ recovered.		There do not appear to have been any funds recovered in this case.

	What funds were recovered? What funds were reimbursed for those affected users?		What funds were recovered? What funds were reimbursed for those affected users?
Line 116:		Line 113:

	== References ==		== References ==
	[https://www.coindesk.com/markets/2020/09/08/crypto-investors-have-ignored-three-straight-51-attacks-on-etc/ Crypto Investors Have Ignored Three Straight 51% Attacks on ETC] (Sep 10)		<references><ref name="coindesk-3005">[https://www.coindesk.com/markets/2020/09/08/crypto-investors-have-ignored-three-straight-51-attacks-on-etc/ Crypto Investors Have Ignored Three Straight 51% Attacks on ETC] (Sep 10, 2021)</ref>

	[https://www.coindesk.com/markets/2019/01/07/coinbase-suspends-ethereum-classic-after-blockchain-history-rewrites/ CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data] (Sep 10)		<ref name="coindesk-3585">[https://www.coindesk.com/markets/2019/01/07/coinbase-suspends-ethereum-classic-after-blockchain-history-rewrites/ CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data] (Sep 10, 2021)</ref>

	[https://blog.coinbase.com/ethereum-classic-etc-is-currently-being-51-attacked-33be13ce32de Deep Chain Reorganization Detected on Ethereum Classic (ETC)] (Feb 6)		<ref name="coinbaseblog-55">[https://blog.coinbase.com/ethereum-classic-etc-is-currently-being-51-attacked-33be13ce32de Deep Chain Reorganization Detected on Ethereum Classic (ETC)] (Feb 6, 2020)</ref>

	[https://twitter.com/etherchain_org/status/1082329360948969472 @etherchain_org Twitter] (Sep 10)		<ref name="etherchainorgtwitter-3586">[https://twitter.com/etherchain_org/status/1082329360948969472 @etherchain_org Twitter] (Sep 10, 2021)</ref>

	[https://pastebin.com/xtu1a1Kg 2019-01-08 04:00:33 UTC Reorg to #7261516 7cdf…dd47 (436f…f5fa a6c6…e657 1068…07 - Pastebin.com] (Sep 10)		<ref name="pastebin-3587">[https://pastebin.com/xtu1a1Kg 2019-01-08 04:00:33 UTC Reorg to #7261516 7cdf…dd47 (436f…f5fa a6c6…e657 1068…07 - Pastebin.com] (Sep 10, 2021)</ref>

	[https://twitter.com/eth_classic/status/1082045223310483457 @eth_classic Twitter] (Sep 10)		<ref name="ethclassictwitter-3588">[https://twitter.com/eth_classic/status/1082045223310483457 @eth_classic Twitter] (Sep 10, 2021)</ref>

	[https://twitter.com/eth_classic/status/1082313711027507200 @eth_classic Twitter] (Sep 10)		<ref name="ethclassictwitter-3589">[https://twitter.com/eth_classic/status/1082313711027507200 @eth_classic Twitter] (Sep 10, 2021)</ref>

	[https://ethereumclassic.org/ ~~https://ethereumclassic.org/~~] (Sep 10)		<ref name="ethereumclassic-3006">[https://ethereumclassic.org/ Ethereum Classic] (Sep 10, 2021)</ref>

	[https://news.bitcoin.com/ethereum-classic-suffers-51-attack-again-delisting-risk-amplified/ Ethereum Classic Suffers 51% Attack Again: Delisting Risk Amplified – Security Bitcoin News] (Sep 10)		<ref name="newsdotbitcoin-3007">[https://news.bitcoin.com/ethereum-classic-suffers-51-attack-again-delisting-risk-amplified/ Ethereum Classic Suffers 51% Attack Again: Delisting Risk Amplified – Security Bitcoin News] (Sep 10, 2021)</ref></references>

Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/coinbasehaltsethereumclassictrading.php}} CoinbaseThe Ethereum Classic blockchain is vulnerable to 51% attacks due to the low hash power. Unknown victims (which may include some exchange platforms) fell victim to the attack and lost $5m. In the 51% attack, a single group or individual purchases or repurposes a massive amount of hashing power. This enables them to produ..."

2023-01-24T21:42:02Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/coinbasehaltsethereumclassictrading.php}} thumb|CoinbaseThe Ethereum Classic blockchain is vulnerable to 51% attacks due to the low hash power. Unknown victims (which may include some exchange platforms) fell victim to the attack and lost $5m. In the 51% attack, a single group or individual purchases or repurposes a massive amount of hashing power. This enables them to produ..."

New page

{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/coinbasehaltsethereumclassictrading.php}}

[[File:Coinbase.jpg|thumb|Coinbase]]The Ethereum Classic blockchain is vulnerable to 51% attacks due to the low hash power. Unknown victims (which may include some exchange platforms) fell victim to the attack and lost $5m.

In the 51% attack, a single group or individual purchases or repurposes a massive amount of hashing power. This enables them to produce a blockchain history in which they didn't make an accepted payment, and feed that back to the network. As a result, they keep their funds, and whatever they received for their payment.

While any customers holding Ethereum Classic would have temporarily lost access, there were no funds lost in this case.

This exchange or platform is based in United States, or the incident targeted people primarily in United States.

== About Coinbase ==
"Ethereum Classic is a decentralized computing platform that executes smart contracts. Applications are ran exactly as programmed without the possibility of censorship, downtime, or third-party interference. Ethereum Classic is a distributed network consisting of a blockchain ledger, native cryptocurrency (ETC) and robust ecosystem of on-chain applications and services." "Ethereum Classic is the product of a hard fork after the Ethereum network split in different ways following an infamous hack in 2016."

"“[Grayscale] holds a sizable percentage of the circulating supply in Ethereum Classic, which is locked up in the trust that will never be liquidated,” [Meltem Demirors, the chief strategy officer at CoinShares] said. “So I think some of those natural factors, which can drain the supply of Ethereum Classic on the market, have a dampening impact on the price.”" "Grayscale started its ETC Trust in April 2017."

“It would be very difficult for us to comment or point to our operating a vehicle around a particular protocol as being influential to the prices,” Michael Sonneshein, managing director of Grayscale, said in a phone interview with CoinDesk, pointing out his company also has large positions in bitcoin and ether. Grayscale, like CoinDesk, is a unit of Digital Currency Group.

"The “honest[y]” of more than half of miners is a core requirement for the security of Bitcoin and any proof-of-work cryptocurrencies based on Bitcoin. Honest action, in this context, means following the behavior described in the Bitcoin white paper. This is sometimes described as a “security risk” or “attack vector,” but is more accurately described as a known limitation to the proof-of-work model."

"Failure to meet this requirement breaks several core guarantees of the Bitcoin protocol, including the irreversibility of transactions. Many other cryptocurrencies, such as Ethereum Classic, have also adopted proof-of-work mining."

"For the Ethereum Classic blockchain, 51% attacks have been a threat for a long time. Unlike Ethereum, from which it was hard forked, the Ethereum Classic network is committed to the Proof-of-Work (PoW) consensus algorithm, which is also used by [bi]tcoin. But for large networks like Bitcoin, a 51% attack is prohibitively expensive to do given the enormous amount of computational power required by PoW to successfully do it. Ethereum Classic’s hashrate is much smaller, making it far more vulnerable to 51% attacks."

"The Ethereum Classic network also suffered a 51% attack in early 2019."

"Media publication Coinness reported Monday that an in-house analyst had detected an abnormal hash rate (or computation energy) going into a single mining pool, potentially causing mass reorganizations (reorgs) of mined blocks. Though initially refuted by the core proponents behind ethereum classic on Twitter, the official account has now affirmed potential cause for concern."

"The duration of the attack seems to [have been] in dispute [at the time]. Blockscout reported block reorganizations occurring at 02:00 UTC and 05:00 UTC Monday, while Bitfly said in a Tweet at 17:00 UTC that the attack was potentially "ongoing." In its note, Coinbase wrote that "the attacks are ongoing." Blockscout project lead Andrew Cravenho affirmed to CoinDesk that although the last recorded reorg attack was seen 14 hours ago, the network is constantly "fluctuating and people are always switching their hashing power," suggesting the potential for continued disruption under "the perfect circumstances."

The attack "led crypto exchange Coinbase to halt all ETC transactions, withdrawals and deposits at the time." "Coinbase has halted all ethereum classic transactions, withdrawals and deposits due to a series of blockchain history reorganizations on the network." "In a blog post, Coinbase said it first noticed the reorg on Jan. 5, two days before other reports began."

"Late on the evening of Saturday 1/5, our systems alerted us to a deep reorg in ETC that contained a double spend. Our on-call engineers responded to the alert and worked to confirm the report through the night. We determined that we would temporarily halt send/receive interaction with the ETC blockchain in order to safeguard customer funds. This meant that customers who tried to send or receive ETC on Coinbase Consumer or Pro were unable to complete their transactions."

"On the morning of Sunday 1/6 we posted an update on status.coinbase.com stating (that) “Due to unstable network conditions on the Ethereum Classic network, we have temporarily disabled all sends and receives for ETC. Buy and sell is not impacted. All other systems are operating normally.”"

Ethereum Classic reported to be "working with Slow Mist and many others in the crypto community. [They] recommend[ed] exchanges and pools significantly increase confirmation times (400-4000+)"

"Updated Jan. 7, 2019–10:27pm PT: At time of writing, we have identified a total of 15 reorganizations, 12 of which contained double spends, totaling 219,500 ETC (~$1.1M). No Coinbase accounts have been impacted by the attack."

"Updated March 11, 2019–11:20am PT: We have now re-enabled sends and receives of ETC. Please note that transactions may take 24 hours, or longer, to be processed by the network due to the large number of confirmations required. Current ETC network status can be found here."

This exchange or platform is based in United States, or the incident targeted people primarily in United States.

The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.

Include:

* Known history of when and how the service was started.
* What problems does the company or service claim to solve?
* What marketing materials were used by the firm or business?
* Audits performed, and excerpts that may have been included.
* Business registration documents shown (fake or legitimate).
* How were people recruited to participate?
* Public warnings and announcements prior to the event.

Don't Include:

* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
* Anything that wasn't reasonably knowable at the time of the event.
There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.

== The Reality ==
This sections is included if a case involved deception or information that was unknown at the time. Examples include:

* When the service was actually started (if different than the "official story").
* Who actually ran a service and their own personal history.
* How the service was structured behind the scenes. (For example, there was no "trading bot".)
* Details of what audits reported and how vulnerabilities were missed during auditing.

== What Happened ==
The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.
{| class="wikitable"
|+Key Event Timeline - Coinbase Halts Ethereum Classic Trading
!Date
!Event
!Description
|-
|January 5th, 2019 12:00:00 AM
|First Event
|This is an expanded description of what happened and the impact. If multiple lines are necessary, add them here.
|-
|
|
|
|-
|
|
|
|}

== Total Amount Lost ==
The total amount lost is unknown.

How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?

== Immediate Reactions ==
How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?

== Ultimate Outcome ==
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?

== Total Amount Recovered ==
It is unknown how much was recovered.

What funds were recovered? What funds were reimbursed for those affected users?

== Ongoing Developments ==
What parts of this case are still remaining to be concluded?

== Prevention Policies ==
The solution to mitigate 51% attacks is to increase block confirmation times and institute checkpoints, where all miners agree that transactions up to that point are valid. If a large reorganization occurs, it will be rejected by miners, and the attacker will simply lose the funds spent on the attack.

Attacks are relatively easy to spot because they result in massive chain reorganizations, which miners can easily decide to reject.

Platforms can protect themselves against 51% attacks by ensuring that they only deal with coins which aren't vulnerable to 51% attacks or use checkpoints, and have sufficient block confirmation requirements on deposits.

== References ==
[https://www.coindesk.com/markets/2020/09/08/crypto-investors-have-ignored-three-straight-51-attacks-on-etc/ Crypto Investors Have Ignored Three Straight 51% Attacks on ETC] (Sep 10)

[https://www.coindesk.com/markets/2019/01/07/coinbase-suspends-ethereum-classic-after-blockchain-history-rewrites/ CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data] (Sep 10)

[https://blog.coinbase.com/ethereum-classic-etc-is-currently-being-51-attacked-33be13ce32de Deep Chain Reorganization Detected on Ethereum Classic (ETC)] (Feb 6)

[https://twitter.com/etherchain_org/status/1082329360948969472 @etherchain_org Twitter] (Sep 10)

[https://pastebin.com/xtu1a1Kg 2019-01-08 04:00:33 UTC Reorg to #7261516 7cdf…dd47 (436f…f5fa a6c6…e657 1068…07 - Pastebin.com] (Sep 10)

[https://twitter.com/eth_classic/status/1082045223310483457 @eth_classic Twitter] (Sep 10)

[https://twitter.com/eth_classic/status/1082313711027507200 @eth_classic Twitter] (Sep 10)

[https://ethereumclassic.org/ https://ethereumclassic.org/] (Sep 10)

[https://news.bitcoin.com/ethereum-classic-suffers-51-attack-again-delisting-risk-amplified/ Ethereum Classic Suffers 51% Attack Again: Delisting Risk Amplified – Security Bitcoin News] (Sep 10)