Cross-Chain Liquidity Rebalance Keeper Trigger

WHAT IT DOES

This tool evaluates cross-chain liquidity rebalance trigger readiness for DeFi protocols, helping keepers determine if a rebalance should be triggered to move liquidity between chains. Given a rebalance keeper contract address, a cross-chain bridge contract address, a target chain ID, and a token address, it reads the current token balance on the target chain, the trigger threshold, whether a rebalance has already been triggered, the rebalance amount, the last rebalance timestamp, and the list of supported chains with their current balances. It also reads bridge state—whether the bridge is active and the bridge fee for the target chain—and the keeper's token balance. The tool then determines trigger readiness—Ready to trigger, Already triggered, Pending (conditions not met), Below threshold, or Cannot trigger. It displays a visual threshold bar showing the current chain balance versus the trigger threshold, a chain balances overview for all supported chains, a detailed breakdown of trigger readiness factors (chain balance >= threshold, bridge active, not already triggered, canTrigger true), and all relevant addresses with block explorer links. All data is pulled directly from the blockchain in real time, providing a transparent view before any rebalance transaction.

HOW TO USE

Connect your wallet using the Connect button in the header. Select the target network from the dropdown—Ethereum Mainnet, Polygon, Optimism, Arbitrum One, Base, or Sepolia testnet. Enter the rebalance keeper contract address, the cross-chain bridge contract address, the target chain ID (e.g., 137 for Polygon), and the token address to check. Click "Check trigger." The tool will fetch the target chain balance, trigger threshold, trigger status, rebalance amount, last rebalance time, supported chains with their balances, bridge state, bridge fee, and keeper token balance. Results appear in the card below with a prominent trigger readiness badge, a visual threshold bar showing the current balance vs threshold, a chain balances overview, detailed keeper and bridge information, and a breakdown of readiness factors with checkmarks or crosses. Use this information to decide whether to trigger a rebalance.

CROSS-CHAIN LIQUIDITY REBALANCE VERIFICATION WITH MULTI-CHAIN STATE ANALYSIS

The tool provides comprehensive cross-chain rebalance verification through multiple on-chain reads across the keeper and bridge contracts. First, it calls getChainBalance() for the target chain to retrieve the current token balance, and getTriggerThreshold() to get the balance level that would trigger a rebalance. The canTrigger() function verifies all conditions—sufficient balance on the target chain, bridge active, not already triggered, and any keeper-specific requirements. The tool also calls getSupportedChains() to retrieve the list of all chains the keeper monitors, then iterates through them to display each chain's current balance, highlighting the target chain. The bridge state is checked via isBridgeActive() and getBridgeFee() to ensure the bridge is operational and to display the cost of rebalancing. The getRebalanceAmount() function returns the amount that would be moved, and getLastRebalanceTime() provides the timestamp of the last rebalance event. The tool also reads the keeper's token balance to ensure it has sufficient funds for the rebalance. All factors are combined to provide a clear, actionable trigger readiness status with a visual threshold bar and chain balances overview.

WHAT IT CANNOT SEE

This tool cannot guarantee rebalance execution—on-chain conditions may change between the check and the transaction. It cannot predict cross-chain bridge latency or ensure that the bridge will process the rebalance within a specific timeframe. It cannot verify off-chain rebalance conditions or ensure that the rebalance amount is appropriate for market conditions. It cannot ensure bridge solvency or detect changes in bridge state that could affect rebalance execution. It cannot detect cross-chain manipulation risks, including bridge attacks, MEV, or other security issues. It cannot assure that the keeper contract or bridge contract is free from vulnerabilities, bugs, or malicious code. It cannot verify that the token address is correct or that the target chain ID is valid. It cannot detect errors in the balance or threshold calculations. It cannot provide financial advice or guarantee that triggering a rebalance is profitable. All data is provided as-is for informational purposes only; any reliance on the tool's output for rebalance decisions is the sole responsibility of the user.

PLEASE NOTE

This tool supports EVM-compatible chains only: Ethereum Mainnet (1), Polygon (137), Optimism (10), Arbitrum One (42161), Base (8453), and Sepolia testnet (11155111). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. The tool requires a Web3 provider (MetaMask or WalletConnect) and access to an RPC endpoint for the selected chain. It does not store any wallet data, token addresses, or rebalance records. All queries are performed directly against the blockchain in real time. The tool does not execute rebalances—it only provides read-only information. Trigger thresholds and chain balances are contract-defined values and do not guarantee rebalance outcomes. Always verify critical data independently through a block explorer and consult with security professionals before triggering any rebalances.