Security & Risks
Audits, safeguards, and risk considerations for mStable tokens.
mStable is built on a combination of audited infrastructure and leading DeFi protocols. While audits and safeguards reduce risk, using DeFi products always carries inherent risks that users should understand.
Product Audit
Sherlock Audit – mStable Pendled sUSDe (via dHEDGE)
Completed by Sherlock in September 2025.
Scope: integration of Ethena (sUSDe), Pendle PTs, Aave looping, and dHEDGE infrastructure.
Covers the strategy powering mStable Pendled sUSDe (mPT-USDe).
Infrastructure Audits
mStable tokens are built on dHEDGE smart contracts, which have undergone multiple audits. These contracts also support other products (e.g. Toros Finance) and have secured large amounts of TVL while processing billions in trading volume across chains.
Most relevant audits
Aave V3 Integration — audited by Santipu (Jan 2025)
EasySwapper V2 — audited by Santipu (Oct 2024)
Core Contracts — audited by Sherlock (June 2024)
Core Contracts — audited by CertiK (Jul 2021)
For the full audit history, see the dHEDGE Audits Timeline.
Partner Protocol Audits
As mStable integrates with external protocols, their security is equally important:
Operational Safeguards
Pause functions: emergency ability to halt deposits or rollovers.
Automation via bots: bots execute predefined strategies for rollovers, rebalancing, and securing Aave capacity. Bots are non-custodial and cannot access user funds.
Risks
Stablecoin risk: The strategy is built on Ethena’s sUSDe. If sUSDe (or its underlying USDe) diverges significantly from $1, it directly impacts performance and collateral safety.
sUSDe yield risk: The yield from sUSDe depends on perp funding markets. If yields compress or funding turns negative, overall returns may fall significantly.
Smart contract risk: Potential vulnerabilities in mStable, dHEDGE, or integrated protocols.
Borrowing risk: Looping increases exposure, amplifying both gains and losses.
Liquidity risk:
Aave caps may limit deposits or rollover capacity.
Pendle PT liquidity can thin near expiry, causing slippage during rollovers.
Oracle risk: Dependence on Aave oracles for pricing and collateral health calculations.
Last updated
Was this helpful?