Capshift moves your collateral across Aave, Compound, Morpho, and GMX — faster than the bots hunting it.
Real protocol. Real mechanic. Compressed to 8 seconds.
Your Aave position on Ethereum hits HF 1.18. Margin obligations on GMX Arbitrum spike too. Capital is fragmented across chains.
Cross-chain threshold (HF 1.4) triggered for GMX 8 minutes ago. LayerZero bridge already initiated. Capital is in transit.
Scans portfolio. WETH idle in Compound v3 at HF 2.4. Withdraws 0.84 WETH, approves Aave, deposits. Source HF settles at 1.91.
Bridge completes. USDC arrives, deposited as margin into GMX. Position safe with 18 minutes of buffer to spare.
Two log entries instead of two liquidation penalties. Estimated penalties avoided: $4,200 across both positions.
Capshift operates inside a permission scope you define and enforce at the smart account layer. Every action is bounded. Every step is auditable. The bot can only do what you've explicitly allowed.
By default, Capshift uses two thresholds derived from historical chart studies of liquidation events: same-chain rescue triggers at HF 1.2, cross-chain at HF 1.4 (earlier because bridges need lead time). Both thresholds are fully configurable per-position and per-protocol — set them based on asset volatility, your risk tolerance, or your own technical analysis. Conservative operators tend to widen the buffer; aggressive operators tighten it.
Every decision is rule-based and deterministic — no ML, no probability. Capshift won't drain a safe position to rescue another, won't spend more on gas than the collateral it's saving, and respects configurable movement caps you set. If no viable rescue exists, it alerts you instead of executing.
Capshift is currently in beta with no usage fees. You pay only the underlying protocol gas costs for executed rescues. Pricing for the production release will be published before beta ends.
Phase 1 supports Ethereum and Arbitrum, with adapters for Aave v3, Compound v3, Morpho Blue, and GMX. Cross-chain transfers run through LayerZero. Additional chains and protocols arrive in Phase 2.
You don't trust the bot — you grant it scoped permissions. Capshift can only do what you've explicitly authorized: which assets, which protocols, which amount limits. Your keys never leave your wallet. Account abstraction support arrives in Phase 2 to remove EOA key dependency entirely.
- stop losing collateral to slow hands