Skip to content
Logo

Risk is isolated per currency vault

The protocol is designed to contain a failure within one market, but isolation does not remove risk. Every action depends on deployment-specific controls and verifiable state.

Material risks and controls

RiskWhy it mattersCapped-pilot control
FXA target currency appreciating against USD raises the USD owed per synthetic tokenMarket caps, spread controls, isolated vaults, pause authority
OracleStale or incorrect prices can misprice mint and redeem actionsFreshness checks, approved signers, disagreement handling, fail-closed quotes
CollateralUSDC can depeg or become unavailableApproved-collateral registry, exposure caps, pause and reconciliation procedures
LiquidityRedemptions can exceed liquid collateral during stressReserve buffer, capacity limits, strategy liquidity limits, pro-rata insolvency policy
StrategyAn allowlisted yield venue can lose funds or become illiquidConservative allocation, explicit allowlist, monitoring, withdrawal and pause procedures
AdministrationPrivileged keys can change sensitive settings2-of-3 Safe, delayed risk increases, scoped roles, recorded release evidence

Loss waterfall

  1. Synthetic-holder liabilities remain senior claims on vault assets.
  2. A stable-plus-buffer position uses its dedicated protocol-owned first-loss buffer; counterparty capital participates only where that position model explicitly approves it.
  3. A full-range position absorbs its own isolated losses first and then the protocol-owned buffer.
  4. Regular-user principal is not silently consumed by a full-range loss. It is exposed only through the approved protocol-wide insolvency process.
  5. If liabilities still exceed eligible collateral, redemption becomes pro-rata under the documented insolvency policy.

Minting and new quotes should pause before redemption when a control degrades. That ordering reduces new exposure but cannot guarantee full recovery.

Review deployment registry requirements before treating any environment as provisioned.