Rebasing changes bridge amounts as token balances update

A rebasing token changes holders’ displayed balances when its protocol adjusts supply, which can make the amount shown on a bridge differ from the amount represented on another chain. The change happens through the token’s accounting, not a transfer into or out of the wallet.

Lido’s stETH is one example: its balance updates with staking reports, while its underlying shares track a holder’s portion of the pool. For the route and execution steps, see this ParaSwap guide to bridging and swapping crypto in one flow.

What does a rebase change?

A rebase changes the number of token units assigned to each holder, usually in proportion to their share of the total supply. A positive rebase raises balances; a negative one lowers them. The holder’s proportional ownership can stay the same even as the unit count changes.

Protocols use different rules. Lido’s documentation says stETH balances change as oracle reports update pooled ether and shares. Ampleforth’s documentation describes AMPL supply adjustments that expand or contract balances in response to its price policy. A rebase does not, by itself, promise a gain in market value.

Why can a bridge show a different amount?

Many bridges lock tokens on the source chain and release or mint a representation on the destination. If the source token rebases while held in the bridge, a standard transfer may not carry that change through to the destination token. Lido warns that rewards on bridged stETH can accrue to the bridge contract rather than to the user.

The displayed amount can also change between a quote and settlement if a rebase occurs, while fees and exchange rates can affect the final amount separately. Before confirming, check:

• Which token contract the route sends and receives.
• Whether the bridge supports rebasing or uses a share-based amount.
• The minimum amount the destination transaction promises to deliver.

How can users keep bridge amounts predictable?

A wrapped version can keep its unit balance fixed while its value in the rebasing token changes. Lido’s wstETH documentation describes this model: wstETH balances stay constant through reports, while each unit represents a changing amount of stETH. Lido identifies the wrapper as a compatibility option for bridges that do not handle rebases.

For most users, the practical choice is to bridge the supported wrapped or non-rebasing representation when the route offers it. Compare the destination amount in that token, then account for its conversion rate if you need the rebasing token afterward. The key is to compare like with like: token units, underlying shares and value are related, but they are not interchangeable measures.