Ethereum Apps Gain Block-Level Transaction Checks
Titan Builder's checks cover only the blocks it builds, and no cryptographic proof yet confirms they ran.
Updated on Nov. 12, 2026 in Cybersecurity

Phylax and Titan Builder have added app-level transaction checks to Ethereum block assembly, letting applications write rules that Titan enforces while it builds a block. The capability is live as an opt-in on Linea since January, and the stub does not establish broader availability, so it is best described as shipped on a limited basis rather than as a settled network-wide standard.
Why it matters
The approach moves some protection for decentralized applications from after-the-fact responses into the block-building step itself, where a transaction that breaks an app's stated limit can be excluded. Titan's reach, which the stub puts at about 53% of externally built blocks accepted by validators in the 24 hours before Nov. 10, is what makes this a network-relevant change rather than a niche tool.
The figures reported are Titan's roughly 53% share of externally built accepted blocks and almost $1 billion in assets under Phylax protection, both as reported by the parties involved. Verification that each protected transaction was actually checked is not yet available, since no cryptographic proof has been published.
The players
Phylax
A protection-layer provider whose first customers are Lighter and Derive, with almost $1 billion under protection.
Titan Builder
An Ethereum block builder that built about 53% of externally built blocks validators accepted in the 24 hours before Nov. 10.
Denaria
An application that enrolled in Phylax on Linea and lost about $166,000 on April 5 in an accounting bug.
The details
Titan Builder runs a checker while it assembles a block, testing each Ethereum transaction against rules that an application has written and can exclude any transaction that breaks a stated limit, such as a cap on a single withdrawal from a vault. An app can configure its protected functions to fail whenever a block has not passed Titan's check, so the restriction is enforced at assembly rather than afterward. The checks run only on blocks Titan itself builds, which limits coverage to that builder's share of the chain.
Timeline
January: Phylax opt-in offered on Linea
April 5: Denaria lost about $166,000 in an accounting bug
24 hours before Nov. 10: Titan built about 53% of externally built blocks validators accepted
The Tech Race
The approach places application-level transaction rules inside the block-building layer that Titan already controls for a large share of Ethereum blocks. It contrasts with protections that act only after a transaction has been included, and the stub does not name a competing effort to compare directly.
Applications on Ethereum that opt in can have their protected functions fail on blocks that have not passed the check, which changes what users of those apps can expect for transactions that exceed a set limit. Availability beyond Linea and the Titan-built blocks is not stated in the source, so broader timing cannot be estimated.
The takeaway
Watch whether Phylax and Titan publish cryptographic proof that checks actually ran, since the system does not yet offer one. Titan's share of externally built blocks is the number to track as an indicator of how far this coverage can reach.
Further reading
For background on the security threats these block-level checks are meant to contain, see Cybersecurity coverage.
Source note: This article includes information reported by TokenPost.


