Bright enterprise passage with warm stone, soft greenery, and a calm compliance-operations feel.
Protocols

Frax AMO Keeper Operational Runbook

Details operational procedures for running keepers executing Algorithmic Market Operations strategies. Covers collateral rebalancing triggers, profit-cycling logic, and risk parameters for each AMO contract.
introduction
AMO KEEPER OPERATIONS

Introduction

Operational runbook for keepers executing Frax Algorithmic Market Operations, covering collateral rebalancing, profit cycling, and risk parameter enforcement.

The Frax AMO Keeper Operational Runbook defines the procedures and parameters for off-chain keeper bots that execute Algorithmic Market Operations (AMOs) on behalf of the Frax protocol. AMOs are autonomous, contract-controlled strategies that manage the protocol's collateral and FXS supply to maintain the FRAX peg and generate protocol revenue. Keepers are the operational link between on-chain AMO contracts and real-world market conditions, responsible for triggering rebalancing actions when predefined thresholds are met.

Each AMO contract—such as the Curve AMO, Uniswap V3 AMO, or Lending AMO—has distinct operational triggers, profit-cycling logic, and risk parameters. Keepers must monitor collateral ratios, pool imbalances, and oracle price deviations to determine when to mint or redeem FRAX, deploy idle collateral, or harvest profits. Misconfiguration or delayed execution can lead to peg instability, inefficient capital allocation, or missed revenue opportunities for veFXS holders. Operators must understand the specific rebalance() and mintRedeem() functions for each AMO type they support.

This runbook is essential for institutional operators, infrastructure providers, and protocol treasury managers who run keeper infrastructure for the Frax ecosystem. It complements the broader veFXS Keeper Network and Frax Oracle Keeper documentation by focusing specifically on the AMO strategy layer. Teams operating AMO keepers should validate their bot logic against the canonical Frax AMO contracts and maintain robust monitoring for trigger conditions, gas price volatility, and MEV exposure. Chainscore Labs can review keeper configurations, assess AMO-specific risk parameters, and provide independent verification of operational readiness before deploying capital to new AMO strategies.

AMO KEEPER OPERATIONAL PROFILE

Quick Facts

Core operational attributes and risk factors for keepers executing Frax AMO strategies. Operators should use this to validate their setup and understand failure impacts.

FieldValueWhy it matters

Keeper Role

Executes collateral rebalancing, profit cycling, and stabilization for AMO contracts

Directly enforces protocol monetary policy; misconfiguration causes economic loss or peg deviation

Primary Contracts

AMO-specific strategy contracts (e.g., Collateral Investor, Curve, Uniswap V3, Fraxlend)

Each AMO has unique triggers and risk parameters; operators must understand per-contract logic

Key Triggers

Collateral ratio thresholds, TWAP deviations, profit accumulation limits, rebalance intervals

Missed or incorrect trigger execution leads to stale positions, excess risk, or missed yield

Affected Assets

FRAX, FXS, sFRAX, USDC, DAI, Curve LP tokens, Fraxlend positions

Operators must manage inventory and gas for multi-asset transactions across strategies

Failure Mode

Keeper downtime, gas mispricing, oracle lag, or incorrect parameter interpretation

Can result in uncollateralized FRAX, bad debt accumulation, or protocol-owned liquidity loss

Operator Risk

Single-operator dependency or concentrated keeper set

Increases censorship and liveness risk; protocol teams should verify keeper decentralization

Monitoring Need

AMO contract balances, collateral ratios, keeper transaction success rate, gas costs

Operators must alert on execution gaps; Chainscore can design monitoring and alerting logic

Integration Impact

DeFi protocols relying on AMO-managed liquidity or FRAX stability

Unexpected AMO behavior can cascade to lending markets, DEX pools, and yield aggregators

technical-context
ALGORITHMIC MARKET OPERATIONS AUTOMATION

AMO Keeper Architecture and Trigger Logic

How Frax AMO keepers monitor protocol state and execute rebalancing strategies to maintain peg stability and collateral health.

Frax Algorithmic Market Operations (AMO) keepers are off-chain bots that execute permissioned strategy contracts, acting as the autonomic nervous system for the Frax stablecoin protocol. Unlike purely permissionless keeper networks, AMO keepers are operated by the Frax core team and authorized governance multisigs, as each AMO contract controls substantial protocol-owned liquidity and collateral. The keeper's primary function is to continuously monitor on-chain state—including FRAX price, collateral ratios, Curve pool balances, and lending market utilization—and submit transactions to AMO contracts when predefined thresholds are breached.

Each AMO contract implements a specific strategy with hardcoded trigger logic. For example, the Curve AMO monitors the FRAX/USDC pool balance and mints or redeems FRAX to maintain the pool's peg. The Fraxlend AMO monitors utilization rates and adjusts interest rates or supplies liquidity to keep borrowing costs within target bands. The Uniswap V3 AMO manages concentrated liquidity positions, rebalancing ranges when price moves outside active ticks. Keepers call workable() or equivalent view functions to check if a strategy requires action, then submit the appropriate execute() transaction. The operational risk lies in gas pricing, transaction ordering, and MEV exposure—a keeper that submits a rebalance too slowly or at unfavorable gas prices can leak value or fail to restore peg pressure.

Operators running AMO keepers must maintain reliable RPC connections to both Fraxtal and Ethereum L1, as many AMOs bridge liquidity across domains. Monitoring infrastructure should track not only keeper liveness but also strategy-specific metrics: Curve pool imbalance percentages, Fraxlend utilization rates, and Uniswap position range proximity. Chainscore Labs can review keeper configurations, gas strategies, and monitoring dashboards to ensure teams maintain protocol stability without introducing operational blind spots. For teams integrating with AMO-managed liquidity, understanding these trigger patterns is essential for predicting liquidity depth and slippage during volatile market conditions.

AMO KEEPER OPERATORS AND DEPENDENT TEAMS

Affected Actors

Keeper Operators

You are directly responsible for executing AMO strategies on-chain. Your primary concerns are bot uptime, gas management, and correct strategy parameterization.

Immediate actions:

  • Verify your keeper is configured with the canonical AMO contract addresses for each active strategy (collateral rebalancing, profit cycling, FXS buybacks).
  • Confirm your keeper's profit threshold and slippage parameters match the latest governance-approved values.
  • Ensure your RPC endpoints can handle the transaction volume during volatile market conditions; fallback endpoints are critical.
  • Monitor keeper wallet balances for both gas tokens and the specific collateral assets required by each AMO.

Operational risks: Misconfiguration can lead to missed profit opportunities, failed transactions that waste gas, or executing trades at unfavorable prices that harm protocol stability. Chainscore can review your keeper configuration and transaction simulation logic.

implementation-impact
AMO KEEPER RISK AND CONTROL SURFACE

Operational Impact Areas

Operating an AMO keeper requires precise management of on-chain triggers, profit-cycling logic, and risk parameters. Misconfiguration can lead to protocol instability, value leakage, or failure to maintain the FRAX peg.

01

Collateral Rebalancing Trigger Management

Keepers must monitor and execute rebalancing operations when collateral ratios deviate from target thresholds defined in each AMO contract. A delayed response to a de-pegg can exacerbate FRAX discount, while premature execution during transient volatility can erode the surplus buffer. Operators should configure their bots with a deviation tolerance that accounts for gas costs and oracle latency. Chainscore can review your keeper's trigger logic and simulation environment to ensure it aligns with the protocol's expected economic invariants.

02

Profit-Cycling and Surplus Buffer Integrity

AMO strategies generate profit by minting FRAX against collateral, deploying it into yield venues, and recollateralizing the protocol. A keeper must correctly sequence these steps to avoid leaving the protocol undercollateralized between transactions. Atomic execution via a smart contract wallet or a flashloan-integrated contract is critical to prevent MEV extraction or sandwich attacks that capture the profit. Operators should stress-test their cycling logic against state bloat and gas spikes on Fraxtal.

03

Risk Parameter and Access Control Enforcement

Each AMO contract enforces specific risk limits, including maximum mint caps, collateral type allowlists, and timelock delays. A keeper misconfiguration that attempts to exceed these limits will result in reverted transactions and wasted gas, potentially during a critical market window. Operators must maintain a parameter registry that syncs with on-chain governance changes. Chainscore offers parameter-change monitoring services to alert keeper operators before a governance vote alters the bounds they are operating within.

04

Oracle Dependency and Data Quality

AMO keepers rely on Frax's oracle infrastructure for collateral pricing to determine minting and redemption validity. Stale prices, deviation across data sources, or a manipulation event can cause a keeper to act on invalid state, leading to protocol losses. Operators should implement a secondary price validation step against a time-weighted average price (TWAP) or a redundant oracle feed before submitting transactions. A kill-switch that halts operations during oracle heartbeat failures is a necessary safety control.

05

Multi-Network Key Management and Nonce Coordination

AMO strategies often span Fraxtal and Ethereum L1, requiring keepers to manage hot wallet keys across multiple networks. A stuck transaction on one chain can block the entire rebalancing cycle if nonce management is not handled asynchronously. Operators should use a transaction relayer architecture with per-network nonce queues and a gas escalation policy. Institutional operators should audit their key management against the Frax Ecosystem Key Management Best Practices to prevent a single point of compromise.

06

Operational Runbook and Failure Mode Testing

A documented runbook is the first line of defense against misoperation during a volatility event. It must define escalation paths for failed transactions, circuit-breaker conditions for pausing the keeper, and a communication protocol for the Frax core team. Operators should rehearse failure scenarios, including a sequencer outage on Fraxtal or a mass liquidation event on a collateral venue. Chainscore can facilitate a tabletop exercise to validate your team's response procedures against realistic AMO failure modes.

AMO KEEPER OPERATIONAL FAILURE MODES

Risk Matrix

Identifies key operational risks for keepers executing Algorithmic Market Operations, the failure modes that can arise from misconfiguration or inaction, and the actions operators should take to maintain protocol stability.

Risk AreaFailure ModeSeverityAffected ActorsMitigation and Action

Collateral Rebalancing

Keeper fails to execute a rebalancing transaction when a collateral ratio threshold is breached, leaving the protocol over or under-collateralized.

High

FRAX stablecoin holders, Frax protocol treasury, veFXS governance

Implement redundant keeper instances with independent RPC endpoints. Monitor on-chain collateral ratios against AMO contract parameters and set alerts for keeper inactivity.

Profit-Cycling Logic

Keeper misconfiguration causes profit-cycling transactions to execute at a loss due to stale oracle prices or incorrect slippage tolerance.

Medium

Frax protocol treasury, FXS holders

Validate oracle data freshness on-chain before transaction submission. Simulate profit-cycling transactions off-chain and enforce a minimum profit threshold in keeper logic.

AMO Contract Parameter Drift

Keeper operates with outdated risk parameters after a governance vote changes an AMO contract's maximum trade size or collateral bounds.

High

Frax protocol treasury, AMO contract users

Subscribe to veFXS governance events for parameter changes. Implement an automated keeper shutdown if the configured parameters do not match the on-chain AMO contract state.

Gas and Network Congestion

Keeper transaction is underpriced and stuck in the mempool during a period of high network activity, delaying a critical AMO operation.

Medium

Keeper operators, Frax protocol stability

Use a gas estimation oracle with a priority fee buffer. Maintain a transaction replacement and cancellation strategy. Monitor mempool pressure on the target network.

Single Keeper Centralization

A single keeper instance or operator is responsible for all AMO execution, creating a liveness risk if it goes offline.

High

Frax protocol liveness, veFXS governance

Decentralize keeper operations across multiple independent operators. Governance should incentivize a diverse keeper set to avoid a single point of failure.

RPC and Data Feed Reliability

Keeper loses connectivity to its primary RPC or oracle data feed, causing it to miss execution windows based on stale or unavailable data.

Medium

Keeper operators

Configure multiple failover RPC URLs and oracle data sources. Implement health checks that halt keeper operations if data freshness falls below a safe threshold.

Multi-Sig Key Compromise

The operator key for the keeper's transaction signer is compromised, allowing an attacker to submit malicious AMO transactions.

Critical

Frax protocol treasury, all FRAX and FXS holders

Secure keeper keys in an HSM or MPC environment. Implement transaction simulation and allowlisting for AMO contract interactions. Conduct regular security audits of the keeper infrastructure.

PRE-FLIGHT VALIDATION

Keeper Operator Deployment Checklist

A structured checklist for operators deploying or updating Frax AMO keeper bots. Each item confirms a critical readiness signal before the keeper is allowed to interact with live AMO contracts. Failure to validate these points can lead to misconfigured rebalancing, profit-cycling failures, or unintended protocol risk.

Confirm the keeper is targeting the canonical AMO contract addresses for the specific strategy (e.g., Collateral Investor, Curve, Uniswap V3). Verify the ABI against the official Frax contract repository or the specific Frax Improvement Proposal (FIP) that deployed the contract.

  • What to check: The AMO_STRATEGY_ADDRESS environment variable or config file entry matches the audited deployment address on the target network.
  • Why it matters: Interacting with a deprecated or incorrect contract can lead to transaction failure or, in a worst-case scenario, loss of funds if interacting with a malicious imposter contract.
  • Readiness signal: The keeper logs a successful contract.code.length > 0 check on startup without reverting.
Chains We Build On

Looking to build on a specific blockchain?

We build smart contracts, DeFi applications, wallets, tokenization platforms, and blockchain infrastructure across the major ecosystems teams choose today. That includes Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Solana, Sui, Aptos, Hedera, Stellar, and NEAR, with support for additional EVM and non-EVM networks based on your product requirements.

EVM ecosystems

  • Ethereum logo
    Ethereum
  • Arbitrum logo
    Arbitrum
  • Optimism logo
    Optimism
  • Polygon logo
    Polygon
  • Avalanche logo
    Avalanche
  • Cronos logo
    Cronos

Non-EVM ecosystems

  • Solana logo
    Solana
  • Sui logo
    Sui
  • Aptos logo
    Aptos
  • Hedera logo
    Hedera
  • Stellar logo
    Stellar
  • NEAR logo
    NEAR

Additional ecosystems

  • Polkadot logo
    Polkadot
  • Cosmos logo
    Cosmos
  • TON logo
    TON
  • Cardano logo
    Cardano
  • Algorand logo
    Algorand
  • Tempo logo
    Tempo

Also available for Base, appchains, custom EVM networks, and cross-chain product architecture.

AMO KEEPER OPERATIONS

Frequently Asked Questions

Common operational questions for teams running keepers that execute Frax Algorithmic Market Operations (AMO) strategies. Covers rebalancing triggers, profit-cycling logic, and risk parameter verification.

Before activating, verify the following:

  • Contract address confirmation: Ensure the keeper is pointed at the correct, canonical AMO contract address for the target chain. Cross-reference against the official Frax documentation or governance-approved deployment list.
  • Collateral balance and allowance: Confirm the keeper's wallet holds sufficient collateral tokens and has granted the necessary approve() allowance to the AMO contract. A dry-run simulation should succeed without allowance errors.
  • Profit-cycling parameters: Validate that the keeper's configured minProfitBps and slippage tolerances match the current governance-set parameters. An overly aggressive configuration can cause transaction reverts; an overly conservative one can cause missed opportunities.
  • Oracle liveness: Check that the price oracle the AMO depends on (e.g., Chainlink or Frax-specific oracle) is reporting fresh data within the heartbeat interval. Stale prices will cause all AMO transactions to revert.
  • Gas strategy: Ensure the keeper's gas pricing model accounts for the target chain's current base fee and priority fee dynamics. A keeper that underbids will never get included.
Trusted by Industry Leaders

Delivering blockchain solutions for 5+ years.

We have partnered with 50+ leading DeFi protocols, NFT ecosystems, and fintech innovators to build secure, scalable, and capital-efficient blockchain products.

Selected Partners & Clients

ChainVote logo
Reax logo
Sokail logo
Swapsicle logo
SyntheX logo
Tekika logo
Telos logo
Zexe logo
ChainVote logo
Reax logo
Sokail logo
Swapsicle logo
SyntheX logo
Tekika logo
Telos logo
Zexe logo
ChainVote logo
Reax logo
Sokail logo
Swapsicle logo
SyntheX logo
Tekika logo
Telos logo
Zexe logo
ChainVote logo
Reax logo
Sokail logo
Swapsicle logo
SyntheX logo
Tekika logo
Telos logo
Zexe logo
I've been working with Chainscore Labs for last 3+ years, they've consistently delivered with strong ownership across multiple projects. The team is reliable and detail-oriented.
L
Lee Erswell
CEO, Telos Foundation
how to get started

How to get started?

If you're looking for blockchain integration, ChainScore Labs has 5+ years of experience helping teams build and integrate exchanges, wallets, smart contracts, tokenization solutions, and protocol-connected products, we can help you choose the right path, integrate securely, and get to production faster. Our team consists of experienced blockchain developers and architects who can help you with your blockchain integration needs.

01

Exploration & Strategy

Define your product goals and choose the right blockchain architecture for your use case.

02

Architecture & Design

Design the smart contracts, tokenomics, and security parameters of your system.

03

Development & Integration

Build and integrate with wallets, oracles, and front-end dApps for a seamless experience.

04

Security & Launch

Comprehensive audits followed by a risk-managed mainnet deployment to protect your users.

Start a build

Need a blockchain engineering team?

Send the project context and we will respond with next steps, scope questions, and a practical path to delivery.