Summary: Phylax is security infrastructure for onchain finance centered on its “Credible Layer,” which lets protocol teams write Solidity assertions that define unacceptable protocol states and have network-integrated enforcement infrastructure block violating transactions before they execute. Its primary-source surface jointly exposes Solidity-authored rules, a sequencer or block-builder sidecar, an onchain registry, assertion data-availability and management tooling, and a public assertion-pattern / exploit-case-study corpus, so it is better cataloged as pre-execution exploit-prevention and risk-control infrastructure than as a conventional monitoring tool, audit shop, or post-incident response product.
What it does:
Lets protocol teams define security and operational rules as Solidity assertions without modifying the protected contracts themselves
Uses a network-integrated Assertion Enforcer sidecar to validate candidate transactions against deployed assertions during block production and drop transactions that violate those rules
Maintains an onchain registry plus an assertion data-availability layer so protected contracts, deployed assertions, and assertion bytecode/source remain discoverable and auditable
Provides developer tooling including the pcl CLI, a modified Foundry distribution (phoundry), standard libraries, an SDK, starter templates, and a management dashboard for deployment and incident monitoring
Publishes an Assertions Book that functions as both a reusable pattern catalog and an exploit-case-study library spanning topics like KYC whitelists, oracle freshness, ERC-4626 accounting, governance timelocks, and token-drain prevention
Markets the system to protocol teams, networks / sequencers, and capital / custody allocators as infrastructure for proving operational constraints rather than only detecting exploits after the fact
Key claims:
The official site frames Phylax as “risk, compliance, and exploit prevention infrastructure” and repeatedly emphasizes preventing exploits before execution rather than monitoring after settlement
The docs define the Credible Layer as security infrastructure that links smart-contract rules onchain and has the network validate every transaction against those rules, dropping invalidating transactions
The architecture docs make clear that this is a sidecar model operated by the network’s block builder or sequencer, not an external transaction simulation service bolted on after the fact
The platform-integration docs show Phylax as a full deployment and monitoring workflow with staging vs production modes, contract-to-assertion mapping, and public verification of active protections and incident history
The llms.txt documentation index is unusually high-signal because it reveals a broad exploit-pattern and invariant catalog, suggesting Phylax is building reusable security-policy infrastructure rather than only bespoke customer deployments
The public GitHub organization shows a substantial product surface: CLI tooling, a modified Foundry, standard libraries, SDKs, contracts, data-availability components, executors, templates, and example assertions
The homepage’s current reference to live deployment on Linea and case studies with teams like Euler, Lagoon, Arcadia, and Kyber suggests the product is already positioned as live financial-infrastructure middleware rather than a purely experimental security project
Whitepaper: No canonical standalone Phylax whitepaper or litepaper surfaced in this pass. The clearest current sources of truth are the official site, docs, llms.txt doc index, architecture and integration pages, and the public GitHub organization; see ../whitepapers/phylax-primary-sources-2026-04-28.md.