Liquidity & Redemption
Redemption mechanics, stress scenarios, and withdrawal queue analysis for bizUSDT0.
Liquidity & Redemption
This document details the redemption mechanics, expected settlement timelines, and stress scenario analysis for bizUSDT0 withdrawals.
Redemption Mechanics
Redemptions follow a reserve-first, then sleeve unwind model:
Step-by-Step Redemption Flow
- Depositor submits a redemption request by calling
redeemon the Superform vault contract, specifying the number of vault shares to burn. - Reserve check: The vault checks if the reserve bucket holds sufficient USDT0 to cover the redemption amount.
- If reserve is sufficient:
- USDT0 is transferred from the reserve bucket to the depositor's wallet.
- Settlement is immediate (within the same transaction block).
- If reserve is insufficient:
- The vault initiates a withdrawal from the Mystic Core USDT0 V2 sleeve to cover the shortfall.
- If Mystic's withdrawal queue is not active, the withdrawal settles within the same transaction or the next block.
- If Mystic's withdrawal queue is active (high utilization), the vault enters the queue and settlement is delayed until the queue clears.
- Vault shares are burned upon successful settlement.
- Reserve is replenished on the next rebalance cycle if it has fallen below the 5% threshold.
Normal Conditions
Expected Settlement Time
| Redemption Size (as % of TVL) | Settlement Time |
|---|---|
| ≤ 8% of TVL (reserve-covered) | Immediate (same block) |
| 8-15% of TVL | 1-60 minutes (sleeve unwind) |
| 15-30% of TVL | 1-24 hours (sleeve unwind, possible queue) |
Reserve Coverage Ratio
At the 8% reserve target:
| TVL Level | Reserve (USDT0) | Covers Normal Daily Redemptions |
|---|---|---|
| $5M | $400,000 | Yes |
| $10M | $800,000 | Yes |
| $25M | $2,000,000 | Yes |
Assumes normal daily redemption flow of ≤ 4% of TVL.
Sleeve Unwind Timeline
The time required to unwind the Mystic Core USDT0 V2 sleeve depends on the Mystic protocol's utilization rate and withdrawal queue depth.
Estimated Unwind Times
| Unwind Size | Mystic Utilization | Expected Time |
|---|---|---|
| $500K | ≤ 80% | Immediate (same block) |
| $500K | 80-90% | 1-4 hours |
| $500K | 90-95% | 4-24 hours |
| $500K | ≥ 95% | 1-7 days (queue dependent) |
| $2M | ≤ 80% | Immediate to 1 hour |
| $2M | 80-90% | 1-8 hours |
| $2M | 90-95% | 8-48 hours |
| $2M | ≥ 95% | 1-14 days (queue dependent) |
| $5M+ | Any | Dependent on queue depth and borrower repayment dynamics |
Monitoring
- Mystic utilization is tracked in real-time on the operational dashboard.
- If utilization exceeds 90%, a preemptive alert is raised to the operations team.
- At ≥ 95%, the vault may voluntarily increase the reserve target to reduce sleeve exposure, pending manager approval.
Lock-Up Periods
- There are no lock-up periods for bizUSDT0.
- Depositors may redeem at any time, subject to reserve adequacy and Mystic withdrawal queue status.
- The vault does not impose minimum holding periods, redemption penalties, or gating mechanisms.
Important Caveats
- While the vault does not gate redemptions, the Mystic sleeve may impose withdrawal delays during periods of high utilization.
- The operations team does not have the ability to freeze or delay depositor redemptions beyond what is dictated by the underlying protocols.
Redemption Queue Monitoring
How Queue Depth Is Tracked
- The vault monitors the Mystic Core USDT0 V2 withdrawal queue via on-chain queries.
- Queue depth (total pending withdrawals, total USDT0 amount) is logged at each rebalance cycle.
- If the vault has an active withdrawal in the Mystic queue, its position and estimated clearing time are reported on the operational dashboard.
Reporting
- Queue status is included in the monthly operational report provided to allocators.
- Real-time queue depth is available on the monitoring dashboard (read-only access for allocators is planned).
Alerting
- SEV2 Alert: Mystic utilization exceeds 85%.
- SEV1 Alert: Mystic utilization exceeds 92% or vault withdrawal is queued for more than 4 hours.
- SEV0 Alert: Mystic utilization exceeds 98% or vault withdrawal is queued for more than 24 hours.