Sparkfi
Sparkfi savings for Different Withdrawal Needs
Sparkfi savings can suit idle assets when the selected vault’s liquidity and redemption process match the intended access to funds. Savings vaults have no scheduled lockup, yet immediate withdrawal depends on available liquidity. Spark Savings V2 vaults generate yield through the Spark Liquidity Layer; sUSDS earns the Sky Savings Rate, while stUSDS carries separate lending exposure and liquidity constraints. The useful choice starts with the asset needed back, its network, and the acceptable settlement time. A balance meant for later use can tolerate conditions that make a vault unsuitable for an immediate payment. Vault shares, projected earnings, and funds already received in a wallet represent different quantities and states.
Last updated ·In short: A Savings Liquidity Intents confirmation records request creation; the withdrawal assets arrive only after fulfillment.
Vault Shares, Yield Sources, and Withdrawal Liquidity
Vault shares track ownership, yield sources generate earnings, and available liquidity supplies assets for withdrawals. These roles determine what a savings balance can earn and how its holder can access it.
Allocation Yield in Spark Savings V2
Spark Savings V2 includes spUSDC, spUSDT, spPYUSD, spETH, and spUSDG. These vaults earn through Spark Liquidity Layer (SLL) allocations, with rates managed by Spark Governance. They provide a way to earn on supported assets while accepting that allocation exposure. Capital deployed through the SLL and assets left idle in a vault serve different jobs: the former supports yield generation, while the latter supports immediate redemption. A savings position can therefore accrue yield even when its full underlying value is not sitting idle.
Savings Rates in Sky and Legacy Vaults
sUSDS provides exposure to the Sky Savings Rate. Legacy sUSDC V1 also uses that rate, while sDAI uses the DAI Savings Rate. Sky Governance sets those rates. stUSDS instead earns from USDS loans backed by SKY collateral. Selecting a vault changes the mechanism behind earnings, even when the funds have the same intended future use.
Savings for Balances Awaiting Use
Idle balances can earn vault yield when their next use leaves time for the applicable redemption process. Savings vault tokens represent shares of underlying assets under the ERC-4626 standard. Yield accrual increases the assets redeemable per share, rather than rebasing the wallet’s share count. Multiplying the share quantity by underlying tokens per share gives the holding’s underlying-token amount. That amount measures the asset claim; available liquidity separately limits immediate redemption.
Deposits produce vault shares that must remain available for redemption. The spendable balance appears only after an exit delivers the selected withdrawal asset.
Vault Entry and Withdrawal Settings
Vault entry and exit settings determine whether savings can meet a requirement for spendable funds by a particular time. If a payment requires assets already in the wallet, an unfulfilled intent leaves that requirement unmet. An immediate redemption and a liquidity intent serve the same access need through different settlement conditions.
| Parameter | Documented Setting | Access Limit |
|---|---|---|
| Savings vault lockup | No scheduled lockup | Settlement still depends on the chosen exit route |
| V2 direct redemption limit | Lower of idle assets and the holder’s redeemable assets | Share ownership alone does not supply withdrawal liquidity |
| Intent eligibility | Whitelisted vault and minimum/maximum underlying-asset amounts | Requests outside configured bounds cannot be created |
| Ethereum app intent timing | Usually a few minutes | Submission precedes asset delivery |
| Ethereum app intent cancellation | After one hour if still unfulfilled | The app disables cancellation during the first hour |
| V2 deposit cap | Configured total-asset ceiling | Limits new deposits separately from withdrawal liquidity |
When Can a V2 Withdrawal Settle Immediately?
A V2 withdrawal can settle immediately when idle liquidity covers the redeemable amount and the holder has enough shares. The Liquidity tab labels that available balance Idle.
Redemption From Idle Liquidity
The SLL replenishes liquidity after withdrawals use the buffer. Total value locked measures the size of the vault; it does not measure its instantly available withdrawal balance. A redemption may therefore exceed idle liquidity even when it represents a small share of total assets. The wallet receives the underlying asset after the redemption succeeds.
Requests Beyond Idle Liquidity
The Ethereum Mainnet app can use Savings Liquidity Intents for eligible spUSDC and spUSDT withdrawals above idle liquidity. The withdrawal dialog identifies the asynchronous route. The contract requires an enabled vault, an amount within configured bounds, and a valid request deadline. The Spark ALM Planner prepares liquidity before a relayer fulfills the request.
After creation, the app lists the request as Pending with an estimated completion time. Fulfillment usually takes a few minutes in this app flow. The assets then reach the wallet automatically. A request-confirmation screen records creation; the pending amount remains separate from the balance that the wallet has received.
Assets and Networks for the Intended Exit
Asset and network selection determine which vault position holds the funds and which exit routes are available. spUSDC deployments include Ethereum, Avalanche, and X Layer. spUSDT uses native USDT on Ethereum and USDT0 on Arbitrum and X Layer. spUSDG accepts USDG on Robinhood Chain. Those combinations preserve the difference between a vault’s displayed denomination and the token that its contracts use.
Savings Vault Intents contracts exist on Ethereum and X Layer, with permission set separately for each vault. Arbitrum spUSDT redemptions are limited to idle liquidity because that network lacks an intents deployment. X Layer spUSDC also remains limited to idle liquidity until governance enables its intent flow. A shared token name therefore does not establish identical withdrawal access across networks.
How Does stUSDS Change Withdrawal Planning?
stUSDS makes withdrawal planning depend on USDS lending backed by SKY collateral, which carries additional risk and potential liquidity constraints. Sky Governance sets its rate. The product has no automatic liquidations and can face restricted redemption liquidity. Its no-lockup status does not remove that constraint. A savings balance with a fixed spending deadline therefore needs to account for this lending exposure as well as the normal exit process.
sUSDS provides direct exposure to the Sky Savings Rate. stUSDS has a different lending use, so the two USDS-based choices carry distinct risk and liquidity conditions.
Backing Risk and Funds Needed on Demand
Backing risk affects what savings shares can return when funds are needed. Spark’s USD savings vaults carry USDS exposure even when the deposit uses another stablecoin. Risk-capital layers and token backstops absorb losses, but residual losses can reach USDS holders if those protections are exhausted. The V2 implementation has no built-in pause or recovery flag, although administrators can upgrade it. Liquidity availability and potential capital loss remain separate conditions of holding a savings balance.
Keeping the required asset directly in the wallet removes the vault-redemption dependency when immediate use takes priority over earning vault yield.
Frequently asked questions about Sparkfi savings
Can Savings Vault Tokens Keep Earning After a Transfer?
Savings vault shares continue accruing yield wherever they are held. Their ERC-4626 structure makes them transferable and compatible with other DeFi integrations. Moving the tokens changes where the claim is held, while the redemption rate continues to reflect accrued yield. A pending withdrawal intent still requires sufficient shares and allowance at fulfillment, so moving the required shares away can cause fulfillment to fail.
Does Depositing the Native Vault Asset Cause Slippage?
A deposit into its matching native-asset vault incurs no slippage. Supported examples include USDC into spUSDC or sUSDC, USDT into spUSDT, USDS into sUSDS, and ETH through the Savings app into spETH. This matching-deposit rule does not establish the price of a swap between different assets.
Are Spark Points Included With Every Savings Deposit?
Spark Points apply only to selected savings vaults under the relevant program’s eligibility terms. A vault’s rate and redeemable asset balance describe its savings position; campaign points are a separate benefit that may not apply to the chosen vault.
How Does a Rate Change Affect a One-Year Savings Projection?
A changed savings rate changes the future earnings that a one-year projection estimates. Spark Governance manages V2 rates, while Sky Governance sets rates for Sky and legacy products. The projection does not fix the future redemption value or the amount of liquidity available on a planned withdrawal date.
How Is Remaining V2 Deposit Capacity Calculated?
Remaining V2 deposit capacity is the configured deposit cap minus total assets, floored at zero. Both inputs use the vault’s underlying-asset units. This calculation gives room for new deposits; it does not measure the idle liquidity available to pay existing holders.
Is Native ETH the Asset Returned by an spETH Contract Redemption?
An spETH contract redemption transfers WETH, the vault’s underlying token. The Savings app supports ETH deposits, so app-level asset handling and the contract’s asset are distinct. The selected withdrawal dialog identifies the asset that the app route will deliver, which matters when the intended use requires native ETH.
Will Another Withdrawal Intent Add to an Existing Request for the Same Vault?
A new onchain withdrawal-intent request for the same account and vault replaces the active request. The replacement receives a new request ID, and a relayer must use that ID for fulfillment. This prevents a superseded request from being fulfilled under its old identifier.