Skip to content
Ecosystem, Technology

Ethereum's new security system divides DeFi

Exploit prevention between stronger security and censorship risks

Author: Staff November 20, 2026 7 min read Subscribe to the newsletter

The integration announced on November 10, 2026, between Phylax and Titan Builder introduces a system on Ethereum that allows DeFi protocols to prevent potentially harmful transactions from being executed before they are recorded on the blockchain. The solution enables applications to establish security conditions that are checked during block construction, adding a layer of protection beyond monitoring tools and post-incident responses. However, the initiative raises questions about network neutrality, as enforcement depends on specialized operators that can influence transaction execution. The case highlights a tension between two priorities in decentralized finance: preventing losses caused by smart contract vulnerabilities and preserving the independence of applications from the infrastructure on which they rely.

Security before transaction execution

DeFi protocol security faces a structural challenge: a transaction can be valid under Ethereum’s rules while producing economic consequences that the application was not designed to allow. Vulnerabilities in collateral management, withdrawal calculations, or balance updates can enable transfers of value that compromise a protocol’s assets. Audits and formal verification help identify such issues before code deployment, while monitoring systems detect abnormal behavior during live operations. However, when an attack is completed within a single block, even prompt detection may come too late to prevent losses. The issue therefore concerns not only the ability to identify vulnerabilities but also the point at which protective measures take effect.

Phylax proposes moving some of these controls into the block construction process, where transactions can still be excluded before their effects become final. Its system, called Credible Layer, had already been operational on the Linea network since January 2026 and is now being extended to Ethereum through a partnership with Titan Builder. Applications cited by Phylax include Derive and Lighter, while the integration with Titan enables checks on blocks constructed by the operator. The solution does not change Ethereum’s consensus rules or automatically activate protection for every application. Adoption is voluntary, and effectiveness depends on the security conditions defined by individual protocols and the operators participating in the system.

How the controls work and their limitations

The mechanism relies on rules known as assertions, which identify outcomes that violate the risk limits established by an application. A protocol could, for example, prevent a withdrawal from exceeding a specified share of available assets or block an operation that would generate losses beyond a predetermined threshold. During block construction, the system checks transaction outcomes against these conditions and allows the builder to exclude transactions that violate them. This approach enables checks against a blockchain state closer to the point of actual execution and supports information or calculations that would be difficult to handle directly within smart contracts. Protection remains limited, however, to the risks that the rules can identify: an unforeseen vulnerability may evade detection, while overly restrictive conditions may prevent legitimate operations. Phylax therefore does not replace audits or automatically correct code vulnerabilities, but provides an additional tool for limiting their consequences.

The main operational challenge is that Titan does not construct every Ethereum block. An attacker could attempt to bypass the checks by using a builder that does not enforce the same rules. To address this possibility, smart contracts can be configured so that certain functions execute only in blocks accompanied by an attestation confirming the required checks. Enforcement is thus extended to the application, which can reject operations lacking the attestation even when the block itself is valid under Ethereum’s consensus rules. Under the system’s design, such an attestation indicates that the builder claims to have performed the checks, without necessarily providing cryptographic proof that they were executed correctly. This mechanism makes bypassing the protections more difficult, but introduces a dependency on the availability and reliability of the operators responsible for verification.

The boundary between protection and censorship

Dependence on builder attestations is the main source of concern regarding censorship resistance. If an application requires a verified block, the unavailability of authorized operators may prevent protected functions from executing even when transactions comply with the protocol’s economic conditions. This could result from a technical outage, configuration errors, or the failure to produce the required attestations. Digital asset attorney Gabriel Shapiro has warned that this model could make certain smart contract functions effectively blockable, even without introducing an explicit suspension mechanism. To limit this risk, Phylax recommends a fail-open configuration, which allows transactions to proceed when external security checks are unavailable. The alternative, fail-closed, prioritizes security by preventing protected functions from executing without the required verification. Individual protocols retain responsibility for this choice and must therefore balance asset protection against operational continuity.

The debate also concerns who can define and modify the rules being enforced. Phylax maintains that participating protocols authorize the conditions and that Titan Builder performs only a verification role, without independently deciding which operations to exclude. An important distinction nevertheless concerns the nature of the checks: blocking a transaction because it creates a financial imbalance is different from excluding it based on the identity of the party initiating it. The same infrastructure could potentially enforce restrictions targeting specific addresses or counterparties. A technical analysis published by ETHBEAT also highlighted that, in the implementation examined, Phylax retains administrative powers over the registries used for attestations, including the ability to update them without mandatory delays. This creates a further distinction between protocols controlling their security rules and the administration of the infrastructure used to enforce them. Assessing censorship risks therefore requires examining not only stated intentions but also the technical powers that can actually be exercised.

Builder concentration and new dependencies

The solution’s operation is closely linked to the structure of Ethereum’s block builder market. By separating block construction from the validator that proposes a block to the network, a significant share of transaction selection and ordering is delegated to specialized operators. According to Phylax, Titan Builder was constructing approximately half of Ethereum’s blocks at the time of the announcement, allowing security checks to be extended quickly to a substantial share of network activity. This concentration represents both an operational advantage and a potential concern. If numerous protocols made their functions dependent on attestations from a small group of builders, those operators could gain an additional competitive advantage, further reinforcing market concentration. Phylax states that its technology is also available to other builders, but technical access alone does not guarantee broad adoption across the ecosystem.

The integration also introduces new operational dependencies because protection relies on the reliability of verification software, attestations, and the systems used by builders. Implementation errors, compromised credentials, or operator outages could undermine the effectiveness of the controls or temporarily prevent access to protected functions. These risks are particularly relevant for essential operations, such as withdrawing funds, where dependence on an intermediary can materially reduce user autonomy. Planned developments in Ethereum, including the incorporation of proposer-builder separation into the protocol through the future Glamsterdam upgrade, could change certain infrastructure dependencies without automatically resolving economic concentration in the builder market. Phylax’s broader adoption should therefore also be assessed by examining how many operators actually enforce the rules, who controls the attestations, and what alternatives remain available when the service is unavailable.

Conclusions

The integration between Phylax and Titan Builder introduces a security approach designed to prevent the effects of exploits before they are recorded on the blockchain, intervening where traditional monitoring tools may prove insufficient. The potential benefit for DeFi protocols is significant, but depends on the quality of the adopted rules and the reliability of the infrastructure enforcing them. Making certain smart contract functions dependent on external verification introduces new dependencies whose impact varies according to protocol configurations and the powers exercisable by participating operators. The central issue is therefore whether stronger asset protection can be achieved without compromising application availability or neutrality in transaction execution. Assessing this model will require examining the distribution of controls across multiple builders, the transparency of enforcement rules, and the existence of procedures that allow users to continue operating when the verification service is unavailable. Additional security will represent a meaningful improvement only if accompanied by verifiable guarantees of autonomy and operational continuity.

Share:
Share LinkedInShare XShare FacebookShare WhatsAppShare Telegram