2 min read
Add as a preferred source on Google

Phylax Lets Ethereum Apps Screen Transactions During Block Building

The opt-in checks can limit some exploit losses, but they raise concerns about availability and builder concentration.

Mentioned assets
A metal circuit breaker sits beside a solid block-shaped component / TokenPost.ai (macro)
A metal circuit breaker sits beside a solid block-shaped component / TokenPost.ai (macro)

Phylax’s integration with Titan Builder lets Ethereum applications screen transactions during block construction, offering protocols a way to limit some exploit losses while raising concerns about outages, security and builder concentration.

Announced Nov. 10, the opt-in system lets applications define rules Titan checks before including transactions in its blocks. Phylax says Titan produces one in every two Ethereum blocks.

The checks are designed to stop transactions that violate an application’s rules before they settle. In one example, a vulnerable vault could release $1 million to a user whose shares are worth $1,000. A circuit breaker could cap the amount leaving the vault in one transaction, limiting that transaction’s loss without guaranteeing that every exploit would be stopped.

The system’s reliance on builder attestations creates a potential availability trade-off. If a protocol requires attestations from builders that performed the checks, its smart contract could reject protected transactions when those attestations stop arriving. The transactions could remain blocked until attestations resume.

Phylax founder and CEO Odysseas Lamtzidis says the company provides and recommends a “fail-open” setting that allows transactions to proceed when security checks are unavailable. Protocols choose whether to enable it, weighing transaction access against the protection the checks are meant to provide. Lamtzidis compared the rules to a require() statement in a smart contract.

Digital assets lawyer Gabriel Shapiro says fail-open protections should be mandatory. He also argues that changes to safeguards should face time delays to prevent protocols from removing them immediately.

Ethereum researcher Fan Zhang said the system is practical partly because the builder market is concentrated. Zhang sees security benefits in adding the checks but warned that extra code at a critical transaction-processing stage could lead to implementation errors or expose builder signing keys to theft, loss or impersonation.

Ethereum researcher Sen Yang warned that major protocols relying on a small number of builders to enforce security could strengthen those builders’ competitive position. Transactions excluded by dominant builders could still be included by builders that do not apply the same exclusion, but inclusion could be delayed.

Phylax says applications opt in and set their own rules. Zhang distinguishes this voluntary filtering from censorship imposed by outside parties, while research co-author Stefanie Boss said rules based on a transaction’s outcome are often considered less risky than rules targeting the person making it. Boss also warned that such rules could be used for sanctions or politically motivated exclusions, and said safeguards are needed to keep them fair and focused on security.

Simon Yoon

Reporter

Simon Yoon reports on blockchain technology for TokenPost. Send corrections or tips to info@tokenpost.com.

Loading…