Before a pool is allowed
A protocol, its collaterals, and the pool itself are reviewed separately. The full gates are in the Risk Framework. In short:- Protocol. Audited contracts, no unresolved critical findings, tier-1 oracles, multisig control, and a minimum age and TVL for the strategy tier. Conservative requires 36 months live and $100M TVL. Aggressive requires 12 months and $25M TVL.
- Collateral. Backing, market cap, liquidity, volume, and depeg history. An asset missing data on two or more criteria is flagged as insufficient data and is not given a tier.
- Pool. TVL and liquidity thresholds for that tier, on a protocol and collateral set that already passed.
Conservative does not include stable/stable markets on a fixed-price oracle.
The six checks on every rebalance
The Agent moves funds only when all six pass. The detailed rules are on Rebalancing Rules.
Collateral health and TVL stability also run outside of rebalance decisions:
- A 50 bps move off the peg is a warning. A 100 bps move is flagged risky and the Agent rebalances away.
- If pool TVL falls below 40% of its 14-day high, the pool is flagged risky and the Agent rebalances away.
While the position is open
Lending markets are watched continuously, on top of the six checks. These rules are in Pool Monitoring. Alerts also fire when a pool drifts out of its strategy tier.
A live pool is also re-scored from the collateral it actually holds:
Share of a tier = exposure to collateral in that tier ÷ exposure to collateral that has been reviewed.
The pool takes the first tier it satisfies. Risky means collateral that fails the Yield Maxxing criteria. Shares of 0.5% or less are ignored as dust. A pool with less than 60% of its exposure reviewed is marked as having insufficient data. If the tier it now qualifies for is below the strategy you selected, it is flagged as drift.
When something breaks
Detection is automatic, and the quant team can also mark a pool not-live by hand. Once a pool is not-live, the Agent stops allocating to it and moves existing positions out. If no safer pool passes the checks, capital can sit unallocated in the Safe. The Emergency Response page records three cases where that exit happened before the loss reached Zyfai users:
Each case links transactions and a post-mortem on that page.
If the incident is in the Session Key layer itself, the kill switch pauses Agent execution. Your funds remain in the Safe.
Next: Choosing a strategy.