|
| 1 | + |
| 2 | +# VFAT Position Analysis: Pools, Impermanent Loss, Profitability, Strategies |
| 3 | + |
| 4 | +--- |
| 5 | + |
| 6 | +## 1. Pools Analyzed |
| 7 | + |
| 8 | +Analysis was conducted across VFAT's top pools: |
| 9 | + |
| 10 | +- **wS/USDC.e** — 14,076 positions |
| 11 | +- **wS/stS** — 3,074 positions |
| 12 | +- **wS/WETH** — 2,820 positions |
| 13 | +- **SHADOW/stS** — 2,240 positions |
| 14 | +- **USDC.e/WETH** — 879 positions |
| 15 | +- **USDC.e/USDT** — 607 positions |
| 16 | +- **USDC.e/scUSD** — 211 positions |
| 17 | +- **WBTC/WETH** — 137 positions |
| 18 | + |
| 19 | +These are the most active pools by number of positions on VFAT. |
| 20 | + |
| 21 | +--- |
| 22 | + |
| 23 | +## 2. Impermanent Loss: How Dangerous It Is |
| 24 | + |
| 25 | +- In 50% of all positions, impermanent loss = 0%. |
| 26 | +- The average impermanent loss across the dataset ≈ 15.6% (distorted by rare catastrophic cases). |
| 27 | +- Main risks observed in: |
| 28 | + - **wS/stS** — many cases of 100% impermanent loss. |
| 29 | + - **USDC.e/WETH** — several critical cases. |
| 30 | + - Partially — **wS/USDC.e**. |
| 31 | +- Reason: auto-rebalance strategies on very short timeframes (<2 hours). |
| 32 | + |
| 33 | +Other pools generally show stable behavior. |
| 34 | + |
| 35 | +--- |
| 36 | + |
| 37 | +## 3. Most Profitable and Stable Pools |
| 38 | + |
| 39 | +Average **APR (30d)** by pool: |
| 40 | + |
| 41 | +- **SHADOW/stS** — 19.4% (high APR but volatile) |
| 42 | +- **wS/WETH** — 5.92% (stable and profitable) |
| 43 | +- **USDC.e/WETH** — 5.69% (balanced profitability) |
| 44 | +- **WBTC/WETH** — 5.66% (solid performance) |
| 45 | +- **USDC.e/scUSD** — 2.94% (stable, stablecoin pair) |
| 46 | +- **wS/stS** — 0.66% (low APR, high impermanent loss risk) |
| 47 | +- **USDC.e/USDT** — 0.26% (very low profitability) |
| 48 | +- **wS/USDC.e** — 0% (no meaningful profitability recorded) |
| 49 | + |
| 50 | +⚡ **Most stable pools:** **wS/WETH**, **USDC.e/WETH**, **WBTC/WETH**. |
| 51 | + |
| 52 | +--- |
| 53 | + |
| 54 | +## 4. Auto-Rebalance vs Non-Rebalance |
| 55 | + |
| 56 | +| | With Auto-Rebalance | Without Auto-Rebalance | |
| 57 | +|-------------------------------|---------------------|-------------------------| |
| 58 | +| Number of Positions | 19,628 | 4,416 | |
| 59 | +| Average APR (30d) | 2.07% | 6.36% | |
| 60 | +| Average Impermanent Loss (%) | 0.16% | 0.14% | |
| 61 | + |
| 62 | +**Conclusion:** |
| 63 | +Across all pools, **positions without auto-rebalance achieve 3x higher APR**. |
| 64 | + |
| 65 | +--- |
| 66 | + |
| 67 | +## 5. Best Strategy Settings |
| 68 | + |
| 69 | +For auto-rebalance strategies: |
| 70 | + |
| 71 | +- Best cutoff: **~887272** |
| 72 | +- Best buffer: **50–100 ticks** |
| 73 | + |
| 74 | +These settings provide the best profitability. |
| 75 | +Too large or negative buffers significantly reduce performance. |
| 76 | + |
| 77 | +--- |
| 78 | + |
| 79 | +## 6. How VFAT Positions Are Configured |
| 80 | + |
| 81 | +Grouped all VFAT position-settings by **cutoff** and **buffer**: |
| 82 | + |
| 83 | +- Most strategies **monitor the entire Uniswap price range** without restrictions (`cutoff ≈ 887272`). |
| 84 | +- Very often, **zero buffer** and **auto-rebalance** are enabled. |
| 85 | + |
| 86 | +Meaning: |
| 87 | +- The system **reacts instantly** when the price moves out of range. |
| 88 | +- This leads to frequent rebalances and higher risks of impermanent loss during sudden market moves. |
| 89 | + |
| 90 | +--- |
| 91 | + |
| 92 | +## Final Summary |
| 93 | + |
| 94 | +- Most stable pools: **wS/WETH**, **USDC.e/WETH**, **WBTC/WETH**. |
| 95 | +- Highest impermanent loss risks: **wS/stS**, partly **USDC.e/WETH**. |
| 96 | +- **Non-auto-rebalance** strategies are significantly more profitable. |
| 97 | +- Best auto-rebalance settings: **cutoff ~887272**, **buffer 50–100**. |
| 98 | +- Current VFAT strategies are very sensitive to price movements due to lack of buffer. |
| 99 | + |
| 100 | +Fine-tuning strategy settings can greatly improve overall profitability and stability. |
0 commit comments