Phylax announced on Nov. 10 that its security system is integrated with Ethereum block builder Titan Builder. Applications can set rules for screening transactions during block construction, aiming to stop harmful outcomes before they settle. Phylax says Titan produces one in every two Ethereum blocks.
The approach could help prevent DeFi losses, but critics warn it may make protected functions effectively freezeable and deepen reliance on a concentrated builder market. Its safeguards are optional, and application developers choose whether to use them.
The system checks transactions against application-defined rules before Titan includes them in a block. Phylax said: “Our mission: stop users from losing money to hacks and errors in DeFi.” Its example is a vulnerable vault that could release $1 million to someone whose shares are worth only $1,000; a circuit breaker could cap withdrawals per transaction. The article also cites possible loss prevention in the $6.3 billion Binance hack and $380 million Bitget exploit, where attackers drained exchange wallets and moved crypto through decentralized protocols.
Gabriel Shapiro warned that contracts could reject transactions unless they are included in blocks from builders that perform the required checks. If those builders stop providing attestations, the protected functions could continue rejecting transactions. Phylax CEO Odysseas Lamtzidis said protocols can allow transactions through when checks are unavailable: “The sane default we provide and suggest to protocols is a fail-open behavior.” That option is not mandatory: “Some protocols might choose to prioritize safety over liveness,” he said. Protocols can also choose whether their contracts are immutable or changeable through governance. Shapiro recommends making fail-open protection compulsory and delaying changes to safeguards so they cannot be removed immediately.
Fan Zhang said the system is practical in part because Ethereum’s builder market is concentrated: “We finally have a way to implement this effectively,” he said, “but sadly only because of how centralized Ethereum’s builder market has become.” He sees “appealing security benefits, especially in the age of AI bots being able to find bugs faster than ever,” but cautions that adding code at a critical transaction-processing stage brings risks such as implementation errors and stolen, lost or impersonated builder signing keys. “I think the community is very concerned about centralized builders and is making efforts to address them. So I’m concerned that these efforts may undermine each other,” he added.
Ethereum researcher Sen Yang said reliance by major protocols on a few builders could advantage those firms and worsen concentration. The proposed enshrined proposer-builder separation (ePBS), slated for the upcoming Glamsterdam upgrade, may lessen dependence on third-party relays, Yang said, “but it does not directly address builder market concentration.’’ Transactions rejected by dominant builders might still be included by builders that do not censor, potentially causing delays instead of permanent exclusion.
Phylax argues that applications—not a new Ethereum-wide authority—set the checks, and Lamtzidis called the system “explicitly opt-in.” He said: “It’s no different than a ‘require()’ statement,” and “Censorship implies arbitrary decision-making or coercion.” Zhang said: “Applications willingly signing up for filtering is fine, as a user can walk away from such applications,” while “It’s externally forced censorship that’s the problem. That’s where I’ll draw the line.”
Stefanie Boss, co-author of research on censorship resistance and compliance in Ethereum’s consensus mechanism, said: “The question is not just whether there is risk, but if it’s acceptable risk,” and “In this case, I’d lean toward that it is acceptable, as the goal is to make the network safer and more aligned with the network and application values.” She considers outcome-based rules less concerning than rules targeting who makes a transaction: “In this case, it is also result-driven, which is often considered less risky,” she said. She argued that “the harm of those hacks is much higher than the harm of this type of exclusion,” while warning that such rules could also be used for sanctions or politically motivated exclusions. “It is important to ensure that there are proper safeguards in place to make sure that these rules will remain fair and designed for security,” she said.




