Earn's Auto-Pilot checks eligible vaults every five minutes. It moves capital only when a candidate satisfies the strategy's yield, confirmation, liquidity, approval, and fee requirements.
- Check every five minutes. Auto-Pilot compares eligible vaults using share-price APY.
- Smooth short-term changes. The strategy's APY smoothing window determines the APY used for comparison.
- Require a sustained improvement. A candidate must clear the relevant Sensitivity threshold for the full Confirmation window.
- Use a higher cross-network threshold. Moving to another network must justify the additional bridge cost.
- Force exits when required. Hiding a held vault or falling below the liquidity floor bypasses the standard APY and confirmation gates.
How Earn scores vaults
Auto-Pilot ranks each eligible vault by its share-price APY, averaged over the strategy's APY smoothing window. MORPHO and partner-token rewards are claimed separately on Morpho and are excluded from this score because they do not increase the vault share price.
Vaults on every selected network use the same score. The network affects the threshold rather than the score: a candidate on the same network uses the same-network Sensitivity, while a candidate on another network must clear the higher cross-network Sensitivity because the move includes bridging.
Auto-Pilot compares the best eligible candidate with the lowest-APY position currently held by the strategy.
Requirements for a standard rebalance
A candidate must pass every applicable gate before Auto-Pilot executes a standard rebalance:
| Gate | Requirement |
|---|---|
| APY gap | The candidate must improve on the lowest-APY held vault by at least the applicable same-network or cross-network Sensitivity. |
| Confirmation window | The same source and destination vaults must remain qualified on consecutive five-minute checks for the complete window. If the advantage disappears, the counter resets. |
| Cooldown | After an on-chain move reverts, Earn excludes that move for one check. |
| No pending bridge | Earn skips the strategy while an earlier cross-chain transfer remains in progress. |
| Principal-erosion guard | Earn skips a move if its fee would reduce Net Value below the strategy's original capital. Forced exits are exempt. |
Auto-Pilot executes at most one move per strategy during each check, starting with the lowest-APY position. If same-network and cross-network moves both qualify, the cross-network move runs first.
After the first deposit, a new strategy waits for one complete Confirmation window before its first rebalance can execute.
Forced exits
Forced exits protect the strategy from a vault that is no longer allowed or no longer meets its liquidity rule. They do not wait for the standard APY gap or Confirmation window.
| Trigger | Result |
|---|---|
| A held vault is hidden | Earn attempts to exit the vault during the next check. |
| Liquidity falls below the configured floor | Earn attempts to exit the vault during the next check. |
Funds move to the best eligible replacement, even when it has a lower APY than the exited vault. To avoid moving near another liquidity limit, Auto-Pilot enters only a replacement holding at least twice the strategy's Minimum withdrawable liquidity floor.
When a forced move enters a lower-APY vault, Earn labels it Force Rebalance in the strategy history and notifications.
If no eligible replacement has been approved by your wallet, the strategy displays Action needed and leaves the position in place. Auto-Pilot retries the exit during each subsequent check.
When a position is Holding
If a vault's withdrawable liquidity cannot cover the position, Earn cannot redeem its shares. The position receives the Holding tag, remains in the vault, and continues earning yield.
While the tag is active, Auto-Pilot excludes that position from moves and evaluates the strategy's next-lowest position instead. The Holding tag clears automatically when sufficient liquidity returns.
Why a rebalance you expected didn't happen
If an expected move does not occur, check these possible causes:
| Possible cause | What it means |
|---|---|
| Strategy paused | Auto-Pilot does not execute rebalances while paused. |
| Sensitivity not met | The APY improvement is below the applicable threshold. A remote-network candidate must clear the higher cross-network value. |
| Top candidates are on other networks | If every current top candidate is remote, the cross-network Sensitivity is the threshold that applies. |
| Confirmation window incomplete | The candidate has not remained qualified for the entire window. Any failed check, including a liquidity drop, resets the counter. |
| Vault approval missing | Earn displays an Approve button and can send a notification when the winning vault is blocked only by a missing allowance. |
| Post-deposit grace period | The strategy has not completed its first Confirmation window after funding. |
| Bridge in progress | A CCTP transfer from an earlier move is still running. |
| Principal-erosion guard | The move fee would reduce Net Value below the original capital. This is more common before a strategy has accumulated much yield. |
| Cross-network move took priority | A qualifying cross-network move ran first, so the same-network move was deferred. |
Auto-Pilot revisits on the next check; there is no manual nudge.
Monitor a rebalance
The strategy page shows each stage of candidate confirmation and execution:
| Location | What you see |
|---|---|
| Auto-Pilot Status | The current state, a gauge from the lowest held APY to the trigger APY, the best candidate, and a progress bar for five-minute confirmation checks. |
| Rebalance in progress | A banner that tracks a same-network rebalance transaction. |
| Cross-network progress | A stepper showing Bridged, Attestation, Relaying, and Deposited. |
| Strategy history | The source vault, destination vault, moved amount, and fee after completion. |
See Cross-chain bridging for what happens during each cross-network stage.