Skip to main content
This suite converts failure modes from Optimism’s security analysis into transaction assertions. See the Phylax fork for implementations.

Approach

Each assertion checks a condition identified by the failure mode analysis. For example, state-consistency checks can constrain withdrawals when AnchorStateRegistry reports incorrect state.

Assertion Collections Overview

FMA ETH Lockbox Assertions

This collection validates the ETHLockbox contract’s security properties, corresponding to the ETH Lockbox FMA document:

Key Checks:

  • FM1: Unauthorized Access Protection - Ensures only authorized portals can call lockETH and unlockETH functions
  • FM2: Drain Prevention - Prevents the lockbox from being drained to zero balance in a single transaction
  • FM3: Proxy Upgrade Protection - Monitors for unexpected proxy implementation address changes that could indicate buggy upgrades

Risk Context:

The FMA rates these failures as critical: high impact and low likelihood. Unauthorized access or bugs could drain the lockbox.

FMA Interop Portal Assertions

This collection validates the OptimismPortal2 and AnchorStateRegistry integration, corresponding to the Interop Portal FMA document:

Key Checks:

  • FM1: AnchorStateRegistry Integrity - Validates retirement timestamp updates, respected game type changes, anchor state transitions, and blacklist operations
  • FM2: Migration Logic Safety - Ensures ETH lockbox and portal migrations maintain fund safety and state consistency
  • FM4: SuperRoots Toggle Validation - Validates that superRootsActive flag changes follow proper authorization and state requirements

Risk Context:

The FMA rates these failures as low likelihood with high or critical impact. Incorrect state or migrations could compromise withdrawal safety or availability.

FMA L2 Message Passing Assertions

This collection validates cross-chain message passing contracts, corresponding to the Message Passing FMA document:

Key Checks:

  • FM1: Destination Chain Validation - Ensures messages aren’t sent to invalid destinations (same chain, zero chain ID, etc.)
  • FM2: Message Validation Integrity - Validates message identifiers and parameters for cross-chain message validation
  • FM3: Message Relay Completeness - Ensures sent messages are properly recorded and can be relayed
  • FM4: Replay Protection - Prevents duplicate message execution through proper successfulMessages tracking
  • FM5: Reentrancy Protection - Ensures message relay functions are atomic and non-reentrant
  • FM6: Repeated Identifier Validation - Prevents duplicate identifier usage within the same transaction

Risk Context:

The FMA rates these failures as medium likelihood with high or critical impact. Message errors could permit theft, duplicate minting, or lost funds.