<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:media="http://search.yahoo.com/mrss/" >

<channel>
	<title>governance control &#8211; Crypto Market Insights: Dive In with CryptoUpdate.io</title>
	<atom:link href="https://cryptoupdate.io/tag/governance-control/feed/" rel="self" type="application/rss+xml" />
	<link>https://cryptoupdate.io</link>
	<description>Latest cryptocurrency news, market updates and analysis</description>
	<lastBuildDate>Mon, 22 May 2023 08:09:42 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>Tornado Cash Attacker Proposes Returning Governance Control: Community Divided</title>
		<link>https://cryptoupdate.io/2023/05/22/tornado-cash-attacker-proposes-returning-governance-control-community-divided/</link>
					<comments>https://cryptoupdate.io/2023/05/22/tornado-cash-attacker-proposes-returning-governance-control-community-divided/#respond</comments>
		
		<dc:creator><![CDATA[Archire Tectre]]></dc:creator>
		<pubDate>Mon, 22 May 2023 08:09:40 +0000</pubDate>
				<category><![CDATA[Altcoins]]></category>
		<category><![CDATA[Cryptocurrency News]]></category>
		<category><![CDATA[Trading Signals]]></category>
		<category><![CDATA[attacker&#039;s proposal]]></category>
		<category><![CDATA[community response]]></category>
		<category><![CDATA[Crypto Hacks]]></category>
		<category><![CDATA[crypto mixer]]></category>
		<category><![CDATA[governance control]]></category>
		<category><![CDATA[malicious proposal]]></category>
		<category><![CDATA[TORN token]]></category>
		<category><![CDATA[Tornado Cash]]></category>
		<guid isPermaLink="false">https://cryptoupdate.io/?p=7016</guid>

					<description><![CDATA[<p>The attacker behind the Tornado Cash governance hijack has surprisingly proposed returning control, leaving the community divided. While some cautiously welcome this development, others suspect a hidden agenda. Explore the unfolding situation and the community's response to this unexpected turn of events.</p>
<p>The post <a rel="nofollow" href="https://cryptoupdate.io/2023/05/22/tornado-cash-attacker-proposes-returning-governance-control-community-divided/">Tornado Cash Attacker Proposes Returning Governance Control: Community Divided</a> appeared first on <a rel="nofollow" href="https://cryptoupdate.io">Crypto Market Insights: Dive In with CryptoUpdate.io</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Introduction</strong></p>



<p>A surprising turn of events has occurred in the Tornado Cash ecosystem, as the attacker responsible for hijacking the project&rsquo;s governance has put forth a proposal to reverse their actions. While some members remain skeptical about trusting the attacker, they find themselves with limited options.</p>



<p><strong>The Malicious Proposal and Community Response</strong></p>



<p>On May 21, the attacker successfully passed a malicious proposal, granting them complete control over Tornado Cash&rsquo;s governance. With this newfound power, the attacker had the ability to cause substantial losses by withdrawing locked votes, draining tokens from the governance contract, and disrupting the system.</p>



<p>Reacting swiftly, community member Mr. Tornadosaurus Hex took proactive measures to mitigate potential damages. They published a subsequent proposal, urging all members to withdraw their funds locked in the governance contract. However, the effectiveness of this proposal remained uncertain due to the attacker&rsquo;s firm grip on governance.</p>



<p><strong>The Surprising Twist: Attacker&rsquo;s Proposal to Return Governance Control</strong></p>



<p>Amid the unfolding situation, to everyone&rsquo;s astonishment, the attacker reached out to the Tornado Cash community with a new proposal. This proposal hinted at their willingness to relinquish control over governance. Mr. Tornadosaurus Hex shared this development with the community, expressing a belief that the attacker might execute the proposal.</p>



<p>While the community finds itself compelled to comply with the attacker&rsquo;s chosen method of returning governance control, doubts remain. Nevertheless, Hex conducted due diligence to verify the storage layouts, providing some reassurance.</p>



<p><strong>Community Speculation and Caution</strong></p>



<p>While many community members embrace optimism regarding the attacker&rsquo;s change of heart, there are those who suspect ulterior motives. Some speculate that this move could be an attempt to artificially inflate the price of the TORN token before the attacker cashes out.</p>



<p>Despite the recent decline in overall hacks within the <a class="lar-automated-link" href="https://accounts.binance.com/register?ref=42224911" rel="nofollow noopener" target="_blank" 4536>crypto</a> ecosystem during the first quarter of 2023, caution remains essential. Past experience has shown that complacency can lead to a surge in <a class="lar-automated-link" href="https://accounts.binance.com/register?ref=42224911" rel="nofollow noopener" target="_blank" 4536>crypto</a> hacks after a period of relative calm.</p>

<p>The post <a rel="nofollow" href="https://cryptoupdate.io/2023/05/22/tornado-cash-attacker-proposes-returning-governance-control-community-divided/">Tornado Cash Attacker Proposes Returning Governance Control: Community Divided</a> appeared first on <a rel="nofollow" href="https://cryptoupdate.io">Crypto Market Insights: Dive In with CryptoUpdate.io</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://cryptoupdate.io/2023/05/22/tornado-cash-attacker-proposes-returning-governance-control-community-divided/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
