Onchain Atlas

Elastic Supply

A token design where the total number of tokens in every holder's wallet automatically expands or contracts to push the price back toward a target, instead of the price simply floating.

Also called: rebasing tokens · supply rebase · algorithmic supply adjustment

What it is

Most tokens have a fixed or slowly-changing supply, so all price adjustment happens through the market price alone. An elastic-supply token instead keeps a target price (often $1) and, on a schedule, changes the total supply up or down so that everyone's balance grows or shrinks proportionally. The goal is that your share of total supply stays the same, but the number of tokens you hold — and ideally the price — moves toward the target.

How it works

  1. The protocol defines a target price (e.g., one token = one dollar) and an oracle or price feed that reports the current market price at each rebase interval.
  2. On a fixed schedule (commonly daily), a rebase function compares market price to target price and computes a supply delta — a percentage increase or decrease to apply to total supply.
  3. If price is above target, the contract mints new tokens and distributes them proportionally to every holder's existing balance (a positive rebase); if price is below target, it burns tokens proportionally from every wallet (a negative rebase).
  4. Balances are usually tracked internally as a fraction of total supply rather than an absolute number, so a rebase is a single global multiplier update rather than millions of individual balance edits.
  5. Because everyone's holdings change by the same percentage, a holder's share of the network doesn't change from a rebase alone — only their nominal token count and, in theory, their assumption about future price does.
  6. The intended feedback loop is psychological and arbitrage-driven: minting supply when price is high should push price down toward target, and burning supply when price is low should push it up, though in practice this rests on market participants actually reacting the way the model assumes.

Why designers use it

  • Attempts to achieve price stability (or a price target) without collateral backing, unlike a fully collateralized stablecoin.
  • Keeps every holder's proportional ownership of the system unchanged, which can be framed as "fairer" than a mechanism that dilutes only some holders.
  • Provides an on-chain-native way to encode a monetary policy reaction to price without a central bank or off-chain issuer.

Failure modes

  • Rebasing does not reliably restore price to target: negative rebases (supply cuts, i.e. everyone gets poorer in token count) tend to trigger panic selling rather than buying, spiraling price further below target — a pattern seen repeatedly in early rebase-token experiments.
  • Composability breaks: DeFi contracts (lending pools, AMMs, other protocols) that assume balances only change via transfers can mishandle a token whose balance silently changes on every holder each day, causing accounting bugs or exploitable mismatches.
  • Holding an elastic-supply token in a contract that isn't rebase-aware (e.g., locked in a non-updating vault) can cause a holder to permanently lose their share of a rebase, or let others claim it.
  • The mechanism assumes rational, forward-looking market participants who understand rebase math; in practice most retail holders react to their visible token balance and price, producing behavior opposite to the model's assumption.
  • Oracle or price-feed manipulation right before a rebase can be gamed to trigger a favorable (or unfavorable, as an attack) mint/burn event.

What to check before using it

  • Verify every integrated contract (lending, AMM, vault, bridge) is explicitly built to handle a balance that changes without a transfer — most standard ERC-20 assumptions break here.
  • Stress-test the negative-rebase case: does the model account for holders selling into a supply cut rather than buying, and what happens to the target price then?
  • Check the price oracle used to trigger rebases for manipulation resistance (TWAP length, source diversity) since it directly controls minting and burning.
  • Confirm whether balances are tracked as a fraction of supply internally, and audit that math carefully — rounding and precision bugs in this pattern have caused real fund losses.
  • Ask whether the target-price mechanism has ever been shown to work in a live market for a comparable design, since the core stabilizing assumption is largely unproven empirically.

Experiments that used it · 2

Shown oldest first, so you can watch the design evolve.

Basis
A venture-backed algorithmic 'central bank' stablecoin that raised $133M but voluntarily shut down and returned all capital in 2018 before launch, citing regulatory constraints on its bond and share tokens.
2018 abandoned
Ampleforth
An uncollateralized rebasing cryptocurrency whose total supply expands and contracts daily so each holder keeps a fixed fraction of the network while the token targets the CPI-adjusted 2019 US dollar.
2019 technically successful commercially unsuccessful