Winds of Change

It’s been a stormy summer for DeFi.

After two painful market crashes, and with a gloomy macro outlook, all our hopes are pinned on the success of the recently confirmed Ethereum merge.

But the US Treasury’s sanctioning of Tornado Cash has forced us to face certain questions about Ethereum’s future.

Is the protocol sufficiently decentralised? Can the actions of a single government affect the entire network? How much, if any, censorship is acceptable?

And why were we not prepared for this?

Just as the most important update yet is about to take place on the Ethereum protocol, the path ahead suddenly seems treacherous…

Will the censorship-resistant, permissionless dream survive, or is OFAC’s influence an existential threat?

Tornado Cash developer Alexey Pertsev has been jailed (without charge) for up to three months in the Netherlands.

Though his expected legal case; that the tool was developed “for the sole purpose of committing criminal acts” may be difficult to prove, authorities are making an example of Pertsev, and using him to send a message to the industry.

Faced with possible jail time, certain doxxed teams behind DAOs and their legal entities have opted to comply with OFAC’s rules, at least on the front-end. However, front-end screening was not enough to save Tornado Cash.

TRM Labs, a compliance organisation which usesadvanced intelligence to investigate wallets and blockchain transaction activity”, has come under the spotlight since the sanctions, as they have presented themselves as a way for protocols to remain compliant and for developers to stay out of jail.

But at what cost to the user?

Blacklists from the likes of TRM classify addresses in terms of “ownership”, “counterparty” and “indirect risk”. However, many legit addresses have been blocked via just a couple of degrees of separation from a Tornado user.

Hack victims, whitehats from the Nomad incident, and addresses targeted by dusting attacks have reported issues because of their on-chain proximity to the Tornado contracts.

A cursory glance at a block explorer would be sufficient to confirm these users’ claims, but the “block first, ask questions later” model of compliance doesn’t do much to help those affected.

Censored front-ends don’t stop the underlying protocols from functioning, they simply make things harder for regular users, while more sophisticated blackhats will have no problem with skirting the sanctions.

Regardless of their accuracy, the wide-net approach seems to be working. Blocks including transactions to/from sanctioned addresses have fallen significantly since the ruling:

But an even greater threat lies in the immediate future…

Given that OFAC’s rules apply to US-linked persons and organisations, it appears that the majority of validators will be forced to comply. Not only that, but block builders will be using mev-boost post-merge, and Flashbots has stated they are, and will continue to be, OFAC-compliant.

That said, PoW is not necessarily any better. While better globally distributed, decentralisation is lower overall. And mining giant Ethermine has begun blanket censorship at the consensus layer.

But if, under Proof of Stake, top validators implement such large-scale censorship, Ethereum has surely failed, in an idealistic sense.

Progress”, at least in Coinbase’s eyes, also sounds eerily similar to the system that crypto set out to disrupt.

And with such over-zealous compliance sweeping over DeFi, are we sleepwalking into a CeDeFi future?

All hope is not lost.

Tether is crypto’s largest stablecoin, and they’ve made it clear that they won’t be preemptively freezing funds, which which hopefully instill confidence in smaller teams.

While the ‘won’t comply until we’re told to’ attitude is a pretty low bar, Tether comes across as a beacon of resistance compared to the many others in the industry, who have immediately dropped their principles and bent over for OFAC.

Uniswap is currently weighing up the situation in a transparent and nuanced discussion, rather than implementing blanket blacklisting.

And perhaps most surprisingly, after being called out, Coinbase CEO Brian Armstrong stated the company’s intent to resist censorship at the validator level. However, it would be naive to think such a large business would take a stand if that also represented an existential legal or financial threat.

Aside from Flashbots, who have opensourced their code to allow for relayer diversity in preparation for the merge, other relayers are available, with Manifold making their mission bluntly clear.

Even Vitalik has stated a preference for punishing validators who comply with sanctions, and the case for social slashing via UASF is promising.

Overall these past weeks have brought many questions into the spotlight.

Questions which had never urgently needed an answer, instead brushed to the side during bull market mania or bear market apathy.

Now, after years of work, Ethereum is facing the beginning of a new era while undergoing a true test of its resilience.

Established powers have timed their crackdown to weaken a movement they cannot fully control via a classic tactic: divide and conquer.

Have corporate interests put Ethereum in an impossible position?

Or are there still enough real cypherpunks to resist the attack?

share this article

REKT serves as a public platform for anonymous authors, we take no responsibility for the views or content hosted on REKT.

donate (ETH / ERC20): 0x3C5c2F4bCeC51a36494682f91Dbc6cA7c63B514C


REKT is not responsible or liable in any manner for any Content posted on our Website or in connection with our Services, whether posted or caused by ANON Author of our Website, or by REKT. Although we provide rules for Anon Author conduct and postings, we do not control and are not responsible for what Anon Author post, transmit or share on our Website or Services, and are not responsible for any offensive, inappropriate, obscene, unlawful or otherwise objectionable content you may encounter on our Website or Services. REKT is not responsible for the conduct, whether online or offline, of any user of our Website or Services.