Overview
Auto-deployment is the process by which Yield Router moves idle capital to yield-generating protocols. This happens automatically, requiring no user action.Deployment Flow
Step 1: Idle Detection
Capital is considered idle when:- Lend order placed but not matched
- Vault has excess cash buffer
- Position matured, awaiting re-deployment
- Order cancelled, funds pending return
Step 2: Delay Period
Capital waits in holding before deployment:| Scenario | Delay | Reason |
|---|---|---|
| New lend order | 5 minutes | Allow time for quick matches |
| Vault buffer | 1 hour | Absorb normal withdrawal flow |
| Post-maturity | 5 minutes | Allow for auto-rollover |
Why the delay? Deploying and recalling has overhead. Brief delays prevent unnecessary churn for capital that matches quickly.
Step 3: Protocol Selection
Yield Router selects the optimal protocol:Step 4: Deployment Execution
Capital is deposited to the selected protocol:Protocol Selection Algorithm
Scoring Factors
| Factor | Weight | Description |
|---|---|---|
| Current APY | 50% | Higher yield preferred |
| Available Liquidity | 25% | Must support instant recall |
| Protocol Health | 15% | Utilization, reserves |
| Diversification | 10% | Avoid over-concentration |
Example Scoring
Diversification Rules
To avoid concentration risk:| Rule | Limit |
|---|---|
| Max single protocol | 60% of user’s idle capital |
| Max protocol utilization | No deployment if >90% utilized |
| Min protocols for large amounts | >$500k splits across 2+ |
Deployment Monitoring
Real-Time Tracking
Dashboard shows deployment status:Deployment Events
Track all deployment activity:| Timestamp | Action | Amount | Protocol | APY |
|---|---|---|---|---|
| Mar 15 14:32 | Deploy | $25,000 | DSR | 4.0% |
| Mar 15 09:15 | Recall | $10,000 | Aave | 3.5% |
| Mar 14 16:45 | Deploy | $10,000 | Aave | 3.5% |
| Mar 14 11:20 | Deploy | $15,000 | DSR | 4.0% |
Yield Accrual
How Yield Accumulates
Yield accrues continuously:Claiming Yield
Yield is automatically claimed when:- Capital is recalled for order matching
- You manually withdraw from order book
- Position matures
Gas Optimization
Batch Deployments
Multiple users’ capital batched together:Timing Optimization
Deployments scheduled during low-gas periods when possible:- Priority: Order matching always takes precedence
- Flexibility: Deployment timing flexible within delay window
- Monitoring: Gas price checked before deployment
Edge Cases
Protocol Rate Changes
If a protocol’s rate drops significantly:- Monitor detects rate change
- If better option available, rebalance triggered
- Capital moved to higher-yield protocol
- Rebalancing cost weighed against yield improvement
Protocol Incidents
If a deployed protocol has an incident:- Immediate pause of new deployments
- Recall of existing capital (if possible)
- Fallback to remaining protocols
- User notification
Insufficient Liquidity
If deployment amount exceeds protocol capacity:- Deploy maximum available
- Remainder stays in holding or splits to other protocol
- Continue monitoring for capacity
FAQs
Can I prevent my capital from being deployed?
Can I prevent my capital from being deployed?
Yes. Disable Yield Router in your settings. Your capital will remain idle in the order book earning 0%.
What if I want to use a specific protocol?
What if I want to use a specific protocol?
Individual users use protocol defaults optimized for safety and yield. Vault curators can customize protocol selection.
Is deployed capital still available for matching?
Is deployed capital still available for matching?
Yes, absolutely. Deployed capital is recalled instantly when your order matches. The deployment is transparent to the matching process.
How often does rebalancing happen?
How often does rebalancing happen?
Only when yield differential justifies the cost (typically >50bps difference sustained for 24+ hours).
Capital Recall
Learn how capital is instantly recalled for order matching