Phylax has introduced a new security layer for Ethereum DeFi through an integration with block builder Titan Builder, aiming to block transactions during block construction if they could lead to harmful outcomes. The approach is designed to prevent certain exploit-related or logic-error scenarios from ever settling—shifting protection earlier in the transaction lifecycle rather than relying on monitoring and post-incident response.
Yet legal and research voices interviewed around the announcement warn that the same mechanism could be repurposed into an effective freeze tool. The concern hinges on how the system depends on builders providing specific attestations and whether protocols choose “fail-open” or “fail-closed” behavior when those checks are unavailable.
Key takeaways
- Phylax’s circuit-breaker concept filters transactions during block construction by having Ethereum applications define rules that builders must enforce.
- The system can theoretically prevent some losses from settling, but it also raises a risk that protected contract functions could be blocked if builders stop providing required attestations.
- Observers argue that Ethereum’s already concentrated builder market could amplify centralization concerns, creating new failure modes and potential competitive advantages for dominant builders.
- Debate centers on where legitimate security ends and censorship begins—especially for rules that target outcomes versus rules that target parties.
How Phylax’s “circuit breakers” work in practice
Announced on Nov. 10, Phylax says its integration with Titan Builder lets Ethereum applications specify rules that exclude transactions with potentially harmful outcomes while blocks are being assembled. According to Phylax, Titan Builder produces one in every two Ethereum blocks, and it checks transactions against those rules before including them.
Phylax frames the goal as a preventive control: stop users from losing money to hacks and errors before funds can move. In a blog describing the integration, Phylax uses a hypothetical “vulnerable vault” scenario where a contract mistakenly releases funds that should not be withdrawable. The company’s circuit breaker is meant to cap the amount that can leave the vault in a single transaction, preventing the full drain in the moment the vulnerable execution would otherwise occur.
The logic is intended to carry over to real-world exploit patterns. The announcement points to major hacks—such as the $6.3 billion Binance hack and the $380 million Bitget exploit—as examples where attackers moved large amounts through decentralized systems. In those cases, Phylax’s pitch is that “hacks should not settle,” with harmful execution halted earlier by design.
The freeze risk: when security checks become a bottleneck
Even if the intent is defensive, lawyer Gabriel Shapiro warned that applications using the system could become effectively freezable. His argument is technical: smart contracts can be programmed to reject transactions unless they are included in blocks from builders that have performed the required security checks. If those builders stopped providing the necessary attestations, the protected functions could continue rejecting transactions until normal conditions return.
Phylax founder and chief executive Odysseas Lamtzidis said protocols can mitigate this by allowing transactions to proceed when the system’s checks are unavailable. He described the “sane default” his team suggests as “fail-open” behavior—prioritizing availability if enforcement cannot be verified.
However, fail-open is presented as optional. Lamtzidis said protocols ultimately decide how to weigh security against liveness, noting that some may choose “safety over liveness.” He also said protocols can determine whether their smart contracts are immutable or adjustable through governance.
Shapiro’s counterpoint is that fail-open protections should not be optional. He argued that time delays should apply to changes to the safeguards, to prevent protocols from quickly removing protections once they are no longer politically or operationally convenient.
For DeFi participants, this is not a purely academic debate. A fail-closed design could turn an external dependency—builder attestation availability—into a direct user-facing outage risk during periods of disruption, upgrades, or builder policy changes.
Builder concentration and new failure modes
Beyond freeze dynamics, researchers raised concerns about Ethereum’s builder market concentration and how Phylax’s approach depends on it. Fan Zhang, an Ethereum researcher, suggested the technology is becoming feasible only now because of that concentration. In his view, that concentration is precisely what makes the system practical, but it is also what intensifies centralization worries.
Zhang highlighted a tradeoff: adding more code and logic into a critical point of transaction processing can increase the number of things that can go wrong, including implementation mistakes and risks around builder signing keys—such as theft, loss, or impersonation.
Ethereum researcher Sen Yang echoed the centralization angle from another direction. If major protocols rely on a small number of builders for security enforcement, those builders could gain competitive advantages and further worsen market concentration. Even if builders exclude certain transactions, Yang noted that the network could still include those excluded by relying on non-censoring builders—potentially causing delays rather than permanent denial, but still creating uneven user experience depending on which builders dominate.
Yang also referenced Ethereum’s proposed enshrined proposer-builder separation (ePBS) upgrade, slated for inclusion in the upcoming Glamsterdam upgrade. While he said ePBS may reduce reliance on some third-party relays, he argued it does not directly solve builder market concentration. That leaves open the question of whether security enforcement will remain tied to a narrow slice of block-building infrastructure.
Security versus censorship: where the line may be drawn
Phylax argues its mechanism does not create a new authority over Ethereum transactions. In its framing, applications themselves define the rules, making the system explicitly opt-in. Lamtzidis compared the checks to conditions already embedded in smart contracts, likening it to a “require()” statement. From that perspective, censorship would imply arbitrary decision-making or coercion by an external party, whereas Phylax’s system is meant to be constrained by application-defined logic.
Zhang drew a similar distinction, arguing that voluntary filtering by applications is acceptable because users can choose not to use those applications. The problematic scenario, in his view, is external coercion—censorship imposed from outside the application layer.
Stefanie Boss, co-author of research on censorship resistance and compliance behavior in Ethereum’s consensus mechanism, suggested that rules tied to transaction outcomes may be less concerning than those tied to who originates the transaction. She considered the security goal legitimate given that the harm from major hacks is often far larger than the harm of excluding certain transactions. At the same time, she cautioned that similar rules could be used to enforce sanctions or other politically motivated exclusions, so safeguards are important to keep the filtering fair and security-oriented.
As Phylax’s system moves from announcement to real deployments, readers should watch how protocols configure fail-open versus fail-closed behavior, whether builders consistently provide attestations, and how the approach interacts with ongoing Ethereum efforts around proposer-builder separation—especially in a builder market that many researchers say is already too concentrated.






