f(x) USD Saving (fxSAVE) stablecoin analytics
fxSAVE is the yield-bearing vault receipt over f(x) Protocol's fxUSD savings strategy, inheriting fxUSD's WBTC and wstETH CDP collateral risk.
Static Profile
Static stablecoin profile
f(x) USD Saving (fxSAVE) static profile: governance model CeFi-Dependent; backing model Crypto-Collateralized; peg US Dollar.
Variant Relationship
f(x) USD Saving (fxSAVE) is modeled as a strategy vault variant of fxUSD (fxUSD). Pharos treats parent stress, redemption, mint authority, and dependency context as relevant to this variant before interpreting its own live metrics.
AI summary / Updated Jun 12, 2026
fxSAVE is an auto-compounding ERC-4626 receipt over f(x) Protocol's Stability Pool, not a simple parked fxUSD balance. The exit path runs through fxSP into a fxUSD-and-USDC mix, then onward into fxUSD's CDP machinery backed by WBTC and wstETH. That gives holders strategy yield...
AI summary · drafted by gpt-5-codex · reviewed by Codex data review on Jun 12, 2026 · facts as of Jun 12, 2026
- Collateral
- ERC-4626 vault receipt over the f(x) Protocol V2 Stability Pool (fxSP / FxUSDBasePool), whose direct underlying is fxUSD plus a USDC reserve leg (currently fxUSD-dominant); auto-compounds wstETH/WBTC and Aave yield into more fxUSD and USDC. Backing inherits fxUSD's WBTC and wstETH CDP collateral base plus the USDC leg and strategy/oracle execution risk
- Peg Mechanism
- fxSAVE is an auto-compounding ERC-4626 vault over the f(x) Protocol V2 Stability Pool (fxSP); holders redeem shares for fxSP and exit the pool to a fxUSD+USDC mix, then inherit fxUSD's CDP redemption and liquidation mechanics (Stability Pool arbitrages the USDC/fxUSD Curve pool to defend the peg)
- Jurisdiction
- Not disclosed in the static profile.
- Proof Of Reserves
- No proof-of-reserves entry in the static profile.
- Contracts
- 1 deployment tracked across Ethereum.
Snippet Answer
Is fxSAVE safe?
Pharos does not mark fxSAVE as absolutely safe. Static metadata says f(x) USD Saving uses a CeFi-Dependent governance model and Crypto-Collateralized backing, with live reserve feed configured; the main caveat is that freeze exposure is inherited through upstream collateral, custody, or wrapper dependencies. Treat the live peg, liquidity, reserve, dependency, and Safety Score sections below as the current risk read.
Next Actions
Exact bot target: /subscribe dews,depeg,safety fxsave-f-x-protocol
Source: checked-in StablecoinMeta profile fields. Live price, supply, reserve, liquidity, event, and safety data load in the interactive dossier below; the summary above was last updated Jun 12, 2026.
fxSAVE quick answers
What is f(x) USD Saving (fxSAVE)?
fxSAVE is the yield-bearing vault receipt over f(x) Protocol's fxUSD savings strategy, inheriting fxUSD's WBTC and wstETH CDP collateral risk. The static profile records its US Dollar peg mechanism as: fxSAVE is an auto-compounding ERC-4626 vault over the f(x) Protocol V2 Stability Pool (fxSP); holders redeem shares for fxSP and exit the pool to a fxUSD+USDC mix, then inherit fxUSD's CDP redemption and liquidation mechanics (Stability...
What backs fxSAVE?
Pharos classifies fxSAVE backing as Crypto-Collateralized. Collateral, per the static profile: ERC-4626 vault receipt over the f(x) Protocol V2 Stability Pool (fxSP / FxUSDBasePool), whose direct underlying is fxUSD plus a USDC reserve leg (currently fxUSD-dominant); auto-compounds wstETH/WBTC and Aave yield into more fxUSD and... Reserve evidence: live reserve feed configured.
Can fxSAVE be frozen or blacklisted?
Based on tracked contract metadata and blacklist coverage, freeze exposure is inherited through upstream collateral, custody, or wrapper dependencies. Live freeze and blacklist events for fxSAVE, when applicable, appear in the dossier below.