Skip to main content
Use the Phylax platform to review and deploy circuit-breaker releases. Your Protocol Manager signs deployments and removals. Assertions are managed as a complete release; you cannot remove them individually from an active release.

​
Check Active Policies

Open Assertions to review circuit-breaker activity against its window and threshold. Select an assertion to check its enforcement status and linked contracts.
Assertions page showing two production circuit breakers, their outflow windows and thresholds, and the full assertion list

Review each circuit breaker's environment, window, threshold, and current activity

​
Review a Release

Open the release marked Needs Review under Latest Releases on the project overview, or select it under Releases → Needs your review. All passed reports completed checks; the release still needs your review and deployment authorization.
Project overview with Release 3 marked Needs Review and Release 2 still active

Open the new release marked Needs Review

Check the environment, target contracts, and Release Diff against the approved changes. Review Assertion verification, Source code, and Backtesting. Investigate unexpected results with your FDE before signing.
Inactive production release with three passed checks, its Release Diff, and the Deploy to Production button

Review the release contents and completed checks before selecting Deploy to Production

Review and Deploy Policies explains each check. Backtesting Results shows how to assess the tested history and findings.

​
Authorize the Change

  1. Connect your assigned Protocol Manager and confirm the release’s environment.
  2. Select Deploy to Production for the production release shown here.
  3. Review and authorize the transaction in your wallet. For a multisig, collect the required approvals and execute it.
  4. Wait for transaction confirmation, then check activation in the platform.
Wallet showing a signed and confirmed Ethereum deployment transaction alongside the platform release list

Confirm the deployment transaction in your wallet, then check policy activation

In Assertions, newly added policies can show Awaiting activation with a remaining block count. Wait for that delay to finish and confirm their enforcement status. A deployment notification or an Active release badge alone does not establish that every new assertion is enforcing.
Production circuit breaker showing Awaiting activation with eight blocks remaining

This circuit breaker still has eight blocks remaining before activation

Your FDE verifies production protection with you. See live enforcement checks. Project access and deployment authority are separate.

​
Replace or Remove a Release

To change or remove an individual assertion, prepare a replacement release with your FDE, developer, or AI coding agent. Include the complete set of policies you intend to keep. Review its diff and checks, then deploy it through the same signing process. Changes take effect after their configured delays. To remove the entire release:
  1. Open the active release and select Remove Release.
  2. Check the network and the full Assertions to remove list.
  3. Confirm Remove Release and authorize the onchain transaction with the Protocol Manager.
  4. Wait for the indexed deactivation blocks and confirm that removal has taken effect.
Remove Release 3 confirmation listing the network and eight assertions to remove, with a notice that enforcement continues until their deactivation blocks

Remove Release schedules removal of all assertions in the release

Assertions remain enforced until their deactivation blocks. A removed release cannot be reactivated. To restore policies after removal takes effect, create and deploy a new release. For an emergency, follow your agreed fallback and recovery procedure. For invalidation analysis, follow Investigate a Rejected Transaction.