Phylax lets Ethereum apps block suspicious transactions — and critics see a freeze switch
Phylax's new security system, integrated with block builder Titan Builder, lets Ethereum apps write rules that filter out risky transactions before blocks are built. It could stop exploits mid-flight — but a lawyer and Ethereum researchers warn it may also create a way to freeze smart contracts and deepen the network's block-builder concentration.
- Original source: ct.com.
- The source published it on Nov 19, 2026 at 2:30 PM.
- No second outlet has reported it yet. Treat it as a single-source claim.
Phylax announced on Nov. 10 that its security system is now integrated with block builder Titan Builder, letting Ethereum applications define rules that exclude transactions likely to produce harmful outcomes during block construction. Titan checks transactions against those rules before putting them in its blocks, and Phylax says the builder produces one in every two Ethereum blocks. The pitch is prevention rather than cleanup: kill exploits before they settle instead of watching for them or rushing in after an attack starts. “Our mission: stop users from losing money to hacks and errors in DeFi,” the announcement said.
Phylax's blog sketches a vulnerable vault that mistakenly releases $1 million to a user whose shares are worth $1,000. With the system running, a circuit breaker could cap how much leaves the vault in a single transaction, keeping the funds from being drained. Phylax says similar safeguards could have limited losses in the $6.3 billion Binance hack and the $380 million Bitget exploit, where attackers drained exchange wallets and moved large amounts of crypto through decentralized protocols.
Digital assets lawyer Gabriel Shapiro warned that apps using the system could become effectively freezable if builders stopped providing the required attestations. Smart contracts can be configured to reject any transaction not included in blocks from builders that performed the security checks, he explained — so protected functions would keep rejecting until attestations resumed. Phylax founder and CEO Odysseas Lamtzidis says protocols can sidestep that by failing open and letting transactions through when the checks are unavailable. “The sane default we provide and suggest to protocols is a fail-open behavior,” he says. But that choice is optional, and he concedes some protocols “might choose to prioritize safety over liveness.” Shapiro argues fail-open protections should be mandatory and any changes to the safeguards should carry time delays.
Ethereum researcher Fan Zhang says the technology is only practical now because of how concentrated the network's block-building market has become. “We finally have a way to implement this effectively, but sadly only because of how centralized Ethereum's builder market has become,” he says, calling the security benefits appealing in an era when AI bots hunt bugs faster than ever. His worry: extra code at such a critical point in transaction processing opens new failure modes, including implementation errors and builder signing-key theft, loss or impersonation. Fellow researcher Sen Yang says major protocols leaning on a small set of builders for security enforcement would hand those builders a competitive edge and worsen concentration. Yang notes Ethereum's proposed enshrined proposer-builder separation upgrade, slated for the Glamsterdam upgrade, may cut reliance on third-party relays but doesn't directly tackle builder market concentration — and transactions excluded by dominant builders could still land through non-censoring builders, causing delays rather than permanent exclusion.
Phylax rejects the idea that it adds a new authority over Ethereum transactions, since applications write the rules themselves and the technology is “explicitly opt-in,” according to Lamtzidis. He compares the checks to conditions already baked into smart contracts: “It's no different than a 'require()' statement. Censorship implies arbitrary decision-making or coercion.” Zhang draws a similar line, saying apps that voluntarily sign up for filtering are fine because users can walk away — “It's externally forced censorship that's the problem,” he says. Stefanie Boss, co-author of research on censorship resistance and compliance behavior in Ethereum's consensus mechanism, says outcome-driven rules bother her less than rules aimed at who is sending a transaction, and she leans toward the risk being acceptable given that hacks do more harm than this kind of exclusion. She still cautions the rules could be used to enforce sanctions or politically motivated exclusions, and says safeguards must keep them fair and security-focused.
TopicsPhylax · Titan Builder · Odysseas Lamtzidis · Gabriel Shapiro · Fan Zhang · Sen Yang · Stefanie Boss · Ethereum
Source: ct.com
Written by AI from verified reporting. Not financial advice.
More stories
- Web3 & Crypto x.com 0 viewsCointelegraph AMA Breaks Down How Bitbase Points Program Works
- Web3 & Crypto New launch cryptopotato.com 2 sources 0 viewsHashi Goes Live on Sui Mainnet With 20-Plus Bitcoin Finance Partners
- Web3 & Crypto thedefiant.io 0 viewsBitcoin Alerts Were Garbage, CoinMarketCap Admits Investigation
- Web3 & Crypto crypto.news 0 viewsBitcoin ETFs lose $975M in a week as BlackRock's IBIT leads the exit

