A stability fee is the variable protocol charge that accrues on debt generated against eligible collateral in Maker/Sky vault accounting.
A stability fee is a governance-set borrowing charge that accrues on debt generated against a specific collateral type in Maker/Sky protocol accounting. It resembles a variable annualized interest rate, but smart contracts apply it to the debt balance; it is not the same as a savings rate, liquidation penalty, token-swap fee, or blockchain gas fee.
The term is protocol-specific rather than a general label for every stablecoin charge. Maker and Sky names, tokens, interfaces, and product structures have changed over time, so a reader should verify the current documentation and parameters for the exact vault or facility being analyzed.
flowchart LR
A["User supplies eligible collateral"] --> B["Vault or facility generates protocol debt"]
G["Governance sets collateral-specific rate parameters"] --> C["Stability Fee accrues on debt"]
B --> C
C --> D["Debt balance increases over time"]
D --> E["User adds collateral or repays debt"]
D --> F["Position may face liquidation if requirements are breached"]
The basic economic relationship is familiar: collateral supports borrowing, and borrowing has a carrying cost. The implementation is unusual because protocol contracts maintain a rate accumulator for each collateral category. When the relevant accounting is updated, accrued fees are reflected in debt and protocol surplus accounting.
This distinction matters. A user may not receive a monthly invoice or make periodic cash payments, yet the obligation can still grow. A dashboard is only an interface to the protocol state; analysts should verify the current position balance and applicable parameters rather than relying on an old screenshot or remembered rate.
For a reader-level estimate, assume the displayed rate is an effective annual rate that remains constant over the period. Then:
Where:
This is an approximation for interpretation, not a substitute for the protocol’s on-chain calculation. The technical implementation uses fixed-point rate parameters and elapsed time. Its result can differ from a simple estimate when the quoted rate convention differs, governance changes the rate, the position changes, or the relevant contract state is updated at a different timestamp.
Suppose a vault has a debt balance of 10,000 units, the applicable annual effective Stability Fee is 6%, and the balance remains unchanged for 90 days apart from fee accrual.
The estimated debt after 90 days is 10,144.71, so the fee component is about 144.71 units. This example excludes gas, liquidation charges, swap costs, and any change in principal or rate.
Now assume the same 10,000 starting debt accrues at 5% for 60 days and then at 8% for 30 days. Applying each rate only to its own interval:
The estimated fee is 144.49 units. It would be wrong to apply the final 8% rate to the entire 90 days. A historical cost analysis needs the effective date of every relevant governance change.
The core protocol documentation describes a Jug rates module that maintains two relevant inputs:
duty, a collateral-specific rate component; andbase, a component that can apply across collateral types.The module’s public drip function calculates fee accumulation since the previous update for a collateral type and updates the accumulated debt recorded by the core accounting system. The implementation uses per-second fixed-point compounding, so adding displayed percentage rates by hand may not reproduce the contract result.
These contract details help explain two practical points. First, a Stability Fee is attached to a particular collateral category, often identified by an ilk, rather than universally to every protocol position. Second, changing a governance parameter and updating accumulated debt are distinct operations in the technical system.
A simple collateral ratio is:
Assume collateral worth 15,000 supports initial debt of 10,000. The starting ratio is 150%. Using the first 90-day example, debt grows to 10,144.71 while collateral value is unchanged:
Fee accrual alone reduced the ratio by about 2.14 percentage points. Whether that creates liquidation risk depends on the position’s current liquidation rules, oracle price, collateral value, and any debt or collateral changes. The example does not assume a universal liquidation threshold.
| Parameter or cost | What it represents | Who is primarily affected | Main question to verify |
|---|---|---|---|
| Stability Fee | Carrying cost that accrues on eligible protocol debt | Vault owner or debt position | Which collateral type, what rate, and from what effective time? |
| Savings rate | Return mechanism for eligible stablecoin supplied to a savings product | Stablecoin holder or supplier | Is the rate variable, and what access or contract terms apply? |
| Liquidation ratio | Minimum collateralization requirement before liquidation can occur | Collateralized borrower | Which oracle value and collateral category govern the threshold? |
| Liquidation penalty | Additional amount applied through the liquidation process | Liquidated position | What penalty and auction or settlement rules currently apply? |
| Debt ceiling | Maximum debt permitted for a collateral category or facility | New and existing borrowers, indirectly | How much capacity remains, and can governance change it? |
| Swap fee or spread | Cost of exchanging through a peg or liquidity mechanism | Trader or liquidity user | Which route, asset pair, direction, and amount apply? |
| Network gas | Blockchain transaction cost paid to process an action | Transaction sender | What network conditions and transaction complexity apply? |
The labels can appear together in one interface, but they answer different questions. A low Stability Fee does not imply a low liquidation penalty, a generous debt ceiling, cheap gas, or low-risk collateral.
Governance may adjust a collateral-specific Stability Fee as part of broader risk, liquidity, supply, or position-management decisions. A lower fee generally reduces the carrying cost of affected debt; a higher fee increases it. The actual response is uncertain because users also consider collateral volatility, liquidation risk, alternative funding costs, transaction costs, liquidity, and confidence in the protocol.
The fee is therefore one influence on borrowing demand and stablecoin supply, not a mechanical price-control switch. Market prices also depend on redemption or conversion mechanisms, reserves and collateral, liquidity venues, counterparty behavior, and broader market conditions.
Governance actions can also be conditional. A published proposal may need approval, execution, and a pause delay before parameters change. Analysts should distinguish a discussion or vote from an executed on-chain change.
For financial reporting or treasury analysis, retain the transaction history, wallet and vault identifiers, block or timestamp evidence, rate history, token balances, valuation source, and accounting policy. A protocol dashboard alone may not provide a complete audit trail.
Digital assets and DeFi positions can be volatile and operationally complex. Overcollateralization and protocol controls do not guarantee redemption, liquidity, solvency, or protection from loss.
Jug rates module explains collateral-specific duty, system-wide base, drip, per-second compounding, and debt accumulation.Vat core accounting documentation describes the protocol’s collateral, debt, and rate-accumulator accounting.This article provides general financial and technical education. It is not individualized investment, borrowing, custody, tax, accounting, or legal advice and does not recommend using any token, vault, protocol, or strategy.