I support onboarding stcUSD with conservative initial parameters. Cap Protocol has real usage — $399M TVL, 113M cUSD in circulation, 81.7% stake rate, 5.26% 7-day APY — and there’s a clear product case for a yield-bearing stablecoin collateral type on MegaETH. MconnectDAO’s questions about circular dependency, oracle infrastructure, and liquidation readiness are the right ones, and they need answers before Snapshot.
The case for onboarding
Three things work in this proposal’s favor:
1. Cap Protocol has demonstrated product-market fit at scale. $399M TVL and an 81.7% stake rate into stcUSD means users are actively choosing the yield-bearing form over the base stablecoin. The 5.26% APY is competitive without being suspiciously high — it sits within a plausible range for stablecoin lending yield. This is organic demand, not airdrop-juiced TVL that evaporates after token distribution.
2. MegaETH needs yield-bearing collateral diversity. The instance launched with a limited asset set. Adding stcUSD gives suppliers a productive collateral option and creates incremental borrowing demand for stablecoins already listed on MegaETH. Lending markets grow when there’s a reason to borrow, and looping yield-bearing stablecoins against base stablecoins is one of DeFi’s most reliable demand drivers.
3. The deferral from initial launch was the right call — and so is revisiting now. stcUSD was in the original MegaETH review scope but deferred pending technical assessment. LlamaRisk has now completed that assessment. Proceeding through ARFC is the appropriate next step.
Where the risk concentrates
MconnectDAO identified the central structural issue: circular dependency between Cap Protocol and Aave. This deserves precise quantification, not just acknowledgment.
Circularity: Cap’s reserves live on Aave
Over 80% of Cap Protocol’s reserves (~$360M+) are deployed on Aave V3 Core on Ethereum. Over 90% of stcUSD yield comes from Aave. Onboarding stcUSD to Aave MegaETH creates a reflexive loop:
- stcUSD generates yield because its reserves earn on Aave.
- stcUSD is accepted as collateral on Aave.
- If Aave experiences a liquidity event or exploit on its Core instance, Cap’s yield drops or freezes, stcUSD’s value proposition degrades, and the collateral backing Aave MegaETH loans loses its yield anchor simultaneously.
This is a contagion path. The DAO should know exactly what percentage of stcUSD yield derives from Aave lending rates versus other sources, and whether Cap has a reserve diversification timeline. If 90%+ of yield comes from Aave and the collateral sits on Aave, the DAO is essentially underwriting its own risk in both directions.
When a protocol’s primary revenue source and its collateral venue are the same entity, the demand architecture scores poorly for independence — a single-source yield dependency creates a correlated failure mode that standard LTV and liquidation parameters don’t capture.
Rehypothecation depth
stcUSD stacks three wrapping layers:
- Layer 1: USD → cUSD (Cap Protocol mint)
- Layer 2: cUSD → stcUSD (staking wrapper)
- Layer 3: stcUSD as Aave collateral
Each layer introduces an independent failure vector. Combined with the circular yield dependency, the effective risk is higher than the factor score alone suggests.
Oracle infrastructure on a young chain
MconnectDAO’s oracle question is critical. MegaETH launched its Frontier mainnet in December 2025 — roughly six months ago. For a yield-bearing asset like stcUSD, the oracle needs to track the exchange rate between stcUSD and its underlying cUSD. Exchange rate manipulation on thin-liquidity chains is a documented attack vector (see: Euler v1 exploit, Mango Markets).
The risk assessment should specify:
- Whether Chainlink feeds are live for stcUSD on MegaETH
- What the heartbeat and deviation thresholds are
- Whether an exchange rate oracle or market price oracle is being used
- What fallback mechanism exists if the primary feed fails
Liquidation infrastructure maturity
Spocky’s concern about liquidation readiness on a young chain is valid. Aave’s liquidation model assumes competitive liquidator participation. On a six-month-old chain, the liquidator set may be shallow. The risk parameters should account for this:
- Lower LTV and higher liquidation bonus than equivalent assets on Ethereum mainnet
- Conservative supply caps that can be raised via Risk Stewards as liquidator coverage is validated
- Monitoring for liquidation latency and success rate post-launch
Recommendations for LlamaRisk’s parameter assessment
-
Quantify the circular dependency. What percentage of stcUSD yield derives from Aave V3 Core? What happens to the stcUSD exchange rate if Aave Core utilization spikes or reserves are frozen? Model the scenario explicitly.
-
Conservative initial caps. Both Spocky and MconnectDAO flagged this. Start low, scale via Risk Stewards. The asset is unproven on this chain.
-
Oracle specification before Snapshot. The community should see the oracle architecture — feed type, heartbeat, deviation threshold, fallback — before voting.
-
Liquidation readiness assessment. Confirm that liquidation bots are deployed, tested, and active on MegaETH for stcUSD before the AIP executes.
Position
Support with conditions. The product case is real, the usage is organic, and MegaETH benefits from the asset. But the circular dependency between Cap and Aave is a structural risk that standard LTV parameters don’t address. LlamaRisk’s assessment should explicitly model the reflexive loop, and initial parameters should reflect the young-chain premium — lower caps, lower LTV, higher liquidation bonus than Ethereum mainnet equivalents.
– Robby G. | Tokedex.org