Skip to content
DeFiLatest

Ethereum DeFi Security Tool Sparks Censorship Concerns

Published

A new security system developed by Phylax promises to empower decentralized finance (DeFi) protocols to intercept and block potentially harmful transactions before they are finalized on the blockchain.

MissedBlock Desk · 4 min read

New Security System Aims to Block Malicious DeFi Transactions, Sparks Censorship Debate

A new security system developed by Phylax promises to empower decentralized finance (DeFi) protocols to intercept and block potentially harmful transactions before they are finalized on the blockchain. While this innovation could significantly bolster cryptocurrency’s defenses against sophisticated threats, including state-sponsored hackers and sanctioned entities, it also raises complex questions about the potential for censorship and the increasing concentration within Ethereum’s block-building market.

The core of Phylax’s system allows decentralized applications to establish specific rules that can flag and exclude transactions deemed likely to result in negative outcomes during the block construction process. This proactive approach aims to prevent exploits from settling, moving beyond traditional post-attack monitoring or emergency interventions.

“Our mission: stop users from losing money to hacks and errors in DeFi,” Phylax stated in its announcement. The system is designed to act as a circuit breaker, capping the amount of funds that can be moved in a single transaction, thereby preventing the complete draining of vulnerable protocols. This could have been a crucial safeguard in major incidents like the $6.3 billion Binance hack or the $380 million Bitget exploit, where malicious actors successfully siphoned vast sums from exchange wallets.

Concerns Over Centralization and Control

However, digital assets lawyer Gabriel Shapiro has voiced concerns that the Phylax system could inadvertently create a mechanism for freezing smart contract functions without any single entity explicitly holding that power. He explained that if block builders, which are essential for processing transactions, were to cease providing necessary attestations, smart contracts configured to rely on these checks could reject all incoming transactions.

Phylax founder and CEO Odysseas Lamtzidis acknowledges this risk but asserts that protocols can mitigate it by allowing transactions to proceed even if the security checks are unavailable. He advocates for a “fail-open” default behavior, suggesting that protocols should prioritize availability. Nevertheless, this safeguard is optional, leaving individual protocols to weigh security against network liveness. Lamtzidis also noted that protocols can choose whether their smart contracts are immutable or subject to governance changes.

Shapiro argues that fail-open protections should be mandatory and that any changes to these safeguards should incorporate time delays to prevent immediate removal.

The Builder Market Dilemma

Beyond the immediate security implications, Phylax’s technology highlights a broader concern about the increasing concentration of power within Ethereum’s block-building market. Fan Zhang, an Ethereum researcher, noted that Phylax’s system is only becoming practically feasible due to this concentration. “We finally have a way to implement this effectively,” he said, “but sadly only because of how centralized Ethereum’s builder market has become.”

While Zhang recognizes the “appealing security benefits” of Phylax’s approach, particularly in an era of advanced AI-driven exploits, he warns that introducing additional code at such a critical juncture in transaction processing creates new potential failure points, including implementation errors and the compromise of builder signing keys. He expressed concern that these efforts to enhance security might inadvertently undermine ongoing community initiatives to address builder market centralization.

Ethereum researcher Sen Yang echoed these sentiments, stating that if major protocols become reliant on a small number of builders for security enforcement, it could grant those builders a competitive advantage and further exacerbate market concentration. He pointed out that while Ethereum’s proposed enshrined proposer-builder separation (ePBS) upgrade aims to reduce reliance on third-party relays, it does not directly tackle builder market concentration. Yang suggested that transactions excluded by dominant builders might still be processed by others, leading to delays rather than outright censorship.

Defining Censorship and Voluntary Filtering

Phylax maintains that its system does not introduce a new layer of authority over Ethereum transactions, as the rules are defined by the applications themselves. Lamtzidis described the technology as “explicitly opt-in,” drawing a parallel to existing “require()” statements within smart contracts. He argued that censorship implies arbitrary decision-making or coercion, which is not the case with Phylax’s system.

Zhang distinguished between applications voluntarily filtering transactions and external parties imposing censorship, stating, “Applications willingly signing up for filtering is fine, as a user can walk away from such applications. It’s externally forced censorship that’s the problem. That’s where I’ll draw the line.”

Stefanie Boss, a co-author of research on censorship resistance in Ethereum, believes that rules targeting a transaction’s outcome are less concerning than those targeting the sender. She considers the security objective legitimate, arguing that “the harm of those hacks is much higher than the harm of this type of exclusion.” However, she cautioned that such rules could also be exploited to enforce sanctions or politically motivated exclusions, emphasizing the need for robust safeguards to ensure fairness and security.

Ethereum DeFi Security Tool Sparks Censorship Concerns · MissedBlock