f(x) USD Saving

fxsave
CoinYQ Dossier

The savings account that buys the peg when it bends

fxSAVE calls itself saving, but its work is closer to an automatic peg desk. Depositors receive a compounding share; beneath it, fxUSD and USDC are swapped, rewards are harvested, leveraged positions are protected, and exit speed is priced against arbitrage risk.

A second token sits above the stablecoin

CoinGecko’s fx-usd-saving is 0x7743e50F534a7f9F1791DdE7dCD89F7783Eefc39, not fxUSD. It began as a TransparentUpgradeableProxy on 2025-03-17. At review it showed 65,023,994.453686079836564869 shares across 382 holder addresses and delegated to 0xE4031e271809d20074E4bef1caeEfEc5f710e8A6.

The share’s ERC-4626 asset is 0x65C9A641afCEB9C0E6034e558A319488FA0FA3be. That fxSP base pool holds the protocol’s fxUSD/USDC Stability Pool position. fxSAVE is therefore two layers away from the collateral that ultimately supports fxUSD.

The exchange rate grows when reinvested rewards increase assets per share. It is not a rebasing balance, bank interest or fixed coupon. A falling base-pool NAV can also pull the share value down.

This extra wrapper also changes accounting language: holders measure shares, while the pool measures fxSP assets and the stablecoin system measures collateral NAV. Confusing those three units can make an apparent yield or loss look larger than it is.

Yield is payment for standing beside the peg

When fxUSD trades below its threshold, the Stability Pool spends USDC to buy it; above one dollar, it sells fxUSD for USDC. Depositors supply inventory for this peg arbitrage.

Income arrives from collateral yield, trading and funding fees, unused slippage, Aave positions and reward emissions. Governance decides distributions among Stability Pool, leveraged positions, treasury and veFXN.

A keeper triggers harvest. The contract removes a bounty and expense share, hands rewards to a harvester for conversion, and restakes the resulting base assets. “Automatic” still depends on callable code, liquid conversion routes and privileged addresses.

An hour separates patient and atomic exits

The patient path burns fxSAVE and moves corresponding 0x65C9A641afCEB9C0E6034e558A319488FA0FA3be into a deterministic LockedFxSaveProxy owned operationally by the fxSAVE contract. It requests the base-pool unlock; after the published 60-minute period the user calls claim for fxUSD and USDC.

The router offers an atomic route that burns shares and converts components to a chosen output. Documentation says this fast route charges a withdrawal/redemption fee and uses min-out protections, so its result depends on liquidity and slippage. The published Stability Pool cooldown is 60 minutes. The Fees page lists a 1% early-exit fee; the separate 0.5% redemption entry is under pegging risk parameters and is not established as the fxSAVE exit fee. These are adjustable documented settings, not a fresh live quote.

The delay prevents a user from entering or leaving against stale pool composition at everyone else’s expense. It is a risk control, but during depeg or congestion it also traps the user in the pool for that interval.

The admin is outside the share ledger

SavingFxUSD gives DEFAULT_ADMIN_ROLE the power to change treasury, harvester, expense ratio, bounty ratio and batching threshold, and to grant a role that claims for another account. The TransparentUpgradeableProxy admin can change implementation 0xE4031e271809d20074E4bef1caeEfEc5f710e8A6. A CLAIM_FOR_ROLE holder can claim another account’s unlocked assets to a receiver it chooses; claimFor does not require the affected depositor’s signature. This affects pending withdrawals even though ordinary share transfers lack a blacklist. Current holders of this role were not independently established.

The share code does not pause or blacklist ordinary transfers. That fact should not be stretched to the full system: new USDC deposits into the base pool can stop when its oracle price reaches 0.995 or below, routers choose conversions, gauges and Convex-style vaults custody positions, and governance can adjust fees.

The published community multisig lists nine signers, but the reviewed sources did not establish which threshold, delay and current accounts hold every fxSAVE admin or proxy-admin role. Holders do not gain those powers by owning the share.

Bad debt reaches the story through fxUSD

The f(x) invariant allocates collateral value between low-volatility fxUSD and leveraged xPOSITION/sPOSITION claims. Rebalancing begins at 88% LTV and hard liquidation at 95% in the published global parameters.

If rebalancing and liquidation leave bad debt, a reserve fund is the first buffer; documentation says remaining bad debt is redistributed among leveraged positions. Even so, fxSAVE relies on fxUSD’s peg and on USDC, and its pool actively changes composition during stress.

No official source reviewed identifies fxSAVE as an obligation of a legal issuer or an insured deposit. The enforceable mechanics we can see are contract shares, withdrawal calls and governance-controlled parameters. “Saving” is a product label, not a statutory protection.

How the project changed

  1. 2025-03-17
    fxSAVE proxy deployed

    Ethereum records the ERC-4626 wrapper for the Stability Pool.

Evidence and primary sources

Last evidence review: 2026-09-05

What is f(x) USD Saving?

fxSAVE is the transferable ERC-4626 share at 0x7743e50F534a7f9F1791DdE7dCD89F7783Eefc39, deployed on Ethereum on 2025-03-17. It wraps the f(x) Stability Pool share 0x65C9A641afCEB9C0E6034e558A319488FA0FA3be, not a bank deposit and not the fxUSD stablecoin at 0x085780639CC2cACd35E474e71f4d000e2405d8f6. Its exchange rate can grow as protocol fees, collateral yield, Aave yield and reward tokens are harvested back into the pool.

A holder owns a smart-contract share of pooled assets. The share has no fixed interest rate or maturity; no offchain redemption promise was identified in the reviewed materials. Its value depends on the fxUSD/USDC Stability Pool, reward conversion, governance-set fees and the solvency machinery behind fxUSD.

What problem does f(x) USD Saving solve?

The Stability Pool must perform two jobs that can pull against each other. It earns income for depositors, but it also buys fxUSD below peg and sells it above peg to absorb imbalance. fxSAVE automates compounding so users do not repeatedly harvest and redeposit; in exchange, their “savings” capital becomes part of the peg defense.

Exit cannot be both fully instant and immune to stale-price arbitrage. The normal path burns fxSAVE, locks the corresponding fxSP in a user-specific proxy, requests redemption and later claims fxUSD plus USDC after the pool cooldown. A router can exit atomically but charges a governance-adjustable fee and introduces swap/slippage execution.

How does f(x) USD Saving work?

Deposits enter 0x65C9A641afCEB9C0E6034e558A319488FA0FA3be, the mixed fxUSD/USDC base pool, then are staked through a Convex-style vault in its gauge. Anyone can call harvest. Pending reward tokens are split among a keeper bounty, treasury expense ratio and reinvestment; remaining tokens are converted into base-pool assets and deposited again.

0x7743e50F534a7f9F1791DdE7dCD89F7783Eefc39 is a TransparentUpgradeableProxy pointing at 0xE4031e271809d20074E4bef1caeEfEc5f710e8A6 at review. DEFAULT_ADMIN_ROLE can change treasury, harvester, fee ratios and deposit threshold and can grant CLAIM_FOR_ROLE. The proxy admin can replace the implementation. Ordinary share transfers are permissionless in the reviewed implementation, but the underlying protocol can halt some deposits on USDC depeg and governance can change risk and fee parameters.

Key facts

  • Canonical fxSAVE: Ethereum 0x7743e50F534a7f9F1791DdE7dCD89F7783Eefc39, 18 decimals; it is distinct from fxUSD 0x085780639CC2cACd35E474e71f4d000e2405d8f6.
  • Underlying ERC-4626 asset is fxSP 0x65C9A641afCEB9C0E6034e558A319488FA0FA3be, the fxUSD/USDC Stability Pool share.
  • The proxy was deployed 2025-03-17 and resolved to SavingFxUSD implementation 0xE403…e8A6 at review.
  • Blockscout reported 65,023,994.453686079836564869 fxSAVE and 382 holder addresses at review.
  • fxSAVE is an autocompounding wrapper over the Stability Pool, not a fixed-rate note or guaranteed dollar balance.
  • Stability Pool revenue includes collateral yield, position fees, funding, unused slippage and Aave yield; allocation is governance-adjustable.
  • Harvest routes rewards through a harvester after deducting expense ratio and caller bounty, then reinvests into fxSP/gauge.
  • Documentation lists the current fxSAVE harvest bounty as 0.01%, while emphasizing that fee settings are adjustable.
  • Normal withdrawal is two-step: burn shares/request unlock, wait the base-pool cooldown, then claim fxUSD plus USDC.
  • The published Stability Pool cooldown is 60 minutes. The Fees page lists a 1% early-exit fee; the separate 0.5% redemption entry is under pegging risk parameters and is not established as the fxSAVE exit fee. These are adjustable documented settings, not a fresh live quote.
  • If USDC oracle price reaches 0.995 or below, new USDC deposits into the Stability Pool are disabled.
  • The pool automatically buys fxUSD below its threshold and sells it above one dollar, exposing deposit composition to peg defense.
  • DEFAULT_ADMIN_ROLE can alter treasury, harvester, fee ratios and thresholds; proxy admin can upgrade code.
  • FXN/veFXN governance affects economics, but owning fxSAVE alone grants no documented governance, equity or legal claim against an identified company.

Official links

Categories

Related coins

Frequently asked questions

Is fxSAVE the same token as fxUSD?

No. fxSAVE is a share wrapper whose value can rise or fall at 0x7743…fc39; fxUSD is the stablecoin at 0x0857…d8f6.

What backs one fxSAVE share?

A proportional amount of fxSP shares, themselves representing the mixed fxUSD/USDC Stability Pool and its accrued rewards.

Where does yield come from?

Protocol fees, collateral and Aave yield, funding and reward tokens assigned to the Stability Pool. Returns vary and can be reduced by losses and fees.

Can I withdraw instantly for free?

The normal route waits through the cooldown and then claims fxUSD plus USDC. Atomic router exits charge a fee and may require swaps with slippage.

Can fxSAVE lose value?

Yes. fxUSD or USDC can depeg, leveraged collateral can suffer bad debt, integrations can fail and governance can alter parameters.

Can administrators seize transfers?

The reviewed SavingFxUSD implementation has no blacklist or pause on ordinary share transfers. Admins do control fees, treasury, harvester, claim delegation and proxy upgrades; underlying pools have their own controls. A CLAIM_FOR_ROLE holder can claim another account’s unlocked assets to a receiver it chooses; claimFor does not require the affected depositor’s signature. This affects pending withdrawals even though ordinary share transfers lack a blacklist. Current holders of this role were not independently established.

Does fxSAVE give voting rights?

No such right is documented for the share. Governance uses FXN/veFXN; fxSAVE represents an ERC-4626 pool position.

Is this legally protected savings?

No bank, deposit insurer, issuer redemption undertaking or legal claim against a named company was identified in the reviewed official materials. Rights evidenced here are smart-contract rights.

External trackers

Choose a tracking site for f(x) USD Saving: