Should you use Phylax?
Work through the questions your team will have, from the first call to live protection.
Explore an Example Policy
Optionally run a local example to see how assertions behave.
Write and Test a Policy
Define a rule and its exceptions, implement its assertions, and prepare test evidence.
Review and Operate Releases
Review a prepared release, authorize deployment, and investigate invalidations.
What You Can Protect
Policies can constrain asset outflows, administrative changes, collateralization, oracle deviations, and relationships between balances or positions. The appropriate rules depend on your protocol and its normal operations. For example, a rule that rejects every ownership change would also reject a planned transfer to a new governance contract. Policy design must account for legitimate exceptions as well as harmful behavior. The Use Cases Book describes patterns and their limits.How Ethereum Enforcement Works
Builders that agree to run the Assertion Enforcer evaluate candidate transactions against your active assertions and exclude violating transactions from the blocks they build. Your team defines and approves the rules through the configured Protocol Manager and signer set. The deployed contracts also define governance, operator, and guardian powers, including manager revocation or assertion removal; review those administrative boundaries before activation. Once you protect functions with Phylax circuit breakers, an onchain guard checks that each protected call executes in a credible block. Calls included in a non-participating builder’s block revert while the guard’s enforcement gate is active. Protection depends on the agreed policies, covered execution paths, deployed guards, and operational configuration. Learn about Ethereum enforcement and its trust and recovery assumptions.From Evaluation to Operation
Our forward deployed engineers (FDEs) work closely with your team to define, implement, and thoroughly test your circuit breakers. We study your protocol and existing mitigations, then work through the failure scenarios, legitimate exceptions, and thresholds that matter to you. Within the agreed integration scope, we write assertions, prepare contract and transaction-routing changes for your review, and test a replica of your protocol on a fork of Ethereum. We run backtests, test legitimate and violating transactions, investigate false positives, and rehearse recovery. Your team reviews the policies and evidence, approves protocol changes, and controls production signing. We prepare and simulate activation transactions for your signers to authorize and execute, then verify the live protection. Monitoring, incident response, and ongoing policy changes follow the operating plan agreed with your team. Use Prepare for Your Integration to gather the information for that discussion. The Enforcement FAQ covers builder behavior, routing, transaction rejection, and recovery.Technical Documentation
The technical guides remain available throughout evaluation and integration:- Ethereum Architecture explains the components and execution path.
- Integration Planning covers guards, routing, authority, and recovery.
- Release Review Checks explains the evidence attached to a release.
- CLI and API references support engineers implementing the agreed plan.

