Rebasing Token Mechanism

What is a rebasing token, and how does it differ from ordinary token price appreciation?

Ordinary tokens usually reflect yield in the unit price — the number of tokens you hold stays fixed, but what each token is worth rises as the underlying asset appreciates, and you have to sell to realize the gain. On paper you'd see "10 tokens, unit price rose from $1.00 to $1.05."

A rebasing mechanism works the opposite way: the token's target unit price stays fixed (most tokenized money market funds set this target at $1.00), and accrued interest instead shows up through a smart contract periodically executing a transaction that proportionally increases the token balance in every registered wallet. You hold 100 tokens today; open your wallet tomorrow morning and it might read 100.012. The displayed price always stays at $1.00, but the token count itself is the record of your yield.

This difference looks like a mere interface choice, but it reflects two entirely different accounting logics underneath: the former is a capital gain, typically triggering a taxable event only on sale; the latter is continuous income, with each balance increase in principle representing a newly realized income event — with real consequences for tax reporting and for how DeFi protocols integrate the token.

Why design it as rebasing at all — wouldn't letting the price float be simpler?

The core motivation is maintaining a fixed benchmark price that works well both psychologically and institutionally. Tokenized money market funds are largely aimed at two use cases, institutional treasury management and DeFi collateral, and both strongly favor a fixed, easy-to-remember, easy-to-reconcile benchmark of one token equals one dollar that's also convenient to value directly as collateral. If the unit price floated daily, a finance department would have to re-convert the dollar value of its position every time it books an entry, and a DeFi protocol using it as collateral would need to wire up a live price oracle just to calculate the collateralization ratio cleanly — raising administrative and integration cost on both sides.

Rebasing separates "fixed price, floating quantity" from "floating price, fixed quantity" as two distinct choices, letting an issuer freely pick whichever suits its target audience better. BlackRock's BUIDL chose rebasing, holding a fixed $1.00 unit price, with interest accruing daily and distributed monthly as newly minted tokens. Ondo's OUSG line instead offers a fixed-supply version where the unit price appreciates daily (while also offering a rebasing variant, rOUSG), letting institutional clients decide which accounting presentation they prefer.

Worth noting: this isn't an invention unique to tokenization. Traditional money market funds have long maintained a stable one-dollar net asset value per share while distributing yield as additional shares — rebasing simply carries this existing fund accounting convention onchain, using a smart contract to automate the share-distribution action a fund administrator would otherwise calculate manually.

How does a rebase actually execute, and how does it differ from a fixed-supply, price-accrual model?

The typical rebasing workflow: the underlying assets (short-term Treasury bills, repurchase agreements, and so on) generate interest daily, and the fund administrator calculates and publishes accrued interest daily. A smart contract executes a global balance-adjustment transaction at a fixed cadence, usually daily or monthly, proportionally distributing the newly accrued tokens to every registered wallet address. You don't need to take any action or sign any transaction — the balance simply grows inside your wallet.

The counterpart model is fixed-supply, price-accrual: total token supply stays constant, but the underlying asset value each token can be redeemed for rises daily. Your token count always reads 100, but what it's worth in dollars climbs day by day, and you need to redeem or sell to realize that accumulated value.

The practical differences between the two sit mainly in three places. First, DeFi composability — a rebasing token's balance changes automatically, incompatible with many lending or liquidity pool contracts that assume a fixed balance, and typically needs an extra non-rebasing wrapper contract before it can be used there; a fixed-supply model, with its inherently unchanging balance, integrates more directly. Second, taxable event frequency — rebasing in principle realizes an income event on every balance increase, while a fixed-supply model usually triggers only one capital gains event upon redemption or sale, making tax treatment simpler for long-term holders. Third, accounting intuitiveness — institutional treasury management favors a book value that looks stable around a round number, and rebasing's constant unit price serves that presentation better.

What should an investor or treasury manager actually watch for when choosing a rebasing token?

First, confirm what you intend to use the token for. For straightforward institutional treasury idle-cash management, rebasing's fixed unit price and automatic monthly token distribution usually aligns most closely with accounting convention and carries the lowest administrative burden. For deploying into a DeFi protocol for liquidity mining or lending collateral, check first whether the target protocol natively supports rebasing tokens — most don't, and you may need to convert through a wrapper contract provided by the issuer or a third party (such as Ondo converting its rebasing version into a fixed-supply version) before it's actually usable there.

Second, get tax treatment confirmed in advance. Jurisdictions differ on whether an automatic increase in token balance constitutes taxable income; some may treat every rebase as a realized income event, meaning a long-held position rebasing daily could in principle generate a large number of granular taxable records, with an actual filing burden potentially far exceeding the single capital gains filing under a fixed-supply model.

Third, the rebase mechanism itself depends on a smart contract executing on schedule — verify whether that execution is fully automated with no room for human intervention, and whether the calculation basis for the balance adjustment (which document discloses the accrued interest) is publicly transparent. Although the rebase action itself is written into the contract, the number driving it — how much interest should be distributed today — still comes from an off-chain fund administrator, the same category of credibility question as NAV disclosure.

Fourth, don't equate an increase in token count directly with having earned extra money. The balance increase is your yield itself, not a gift bonus out of nowhere; when calculating actual return, convert the balance increase back into dollar terms at the target unit price, rather than looking only at the token count's growth rate.