Bridging rebasing tokens means checking more than the balance

1 stETH balance can change after a rebase without a transfer. When you bridge a rebasing token, that means the amount shown on the destination chain may not keep tracking the value represented on the source chain.

Why does a rebasing token balance change?

A rebasing token adjusts how many token units each holder sees as the protocol’s accounting changes. With stETH, for example, holders have shares in a pool, and the displayed token balance is calculated from those shares and the pool’s total ether. A rebase can therefore change your stETH balance without changing your share count.

This differs from a fixed-balance token, where your displayed amount usually changes only after a transfer, mint or burn. Some tokens instead offer a wrapped form: wstETH balances stay fixed, while each unit can represent a changing amount of stETH. That design can make the token easier for bridges and other applications to handle, but the exchange rate still matters when you unwrap or compare values.

A cross-chain route may lock tokens on one chain and mint a representation on another. If the locked token rebases but the bridge does not account for rebases, the rewards may accrue to the bridge contract rather than to the destination holder. For a fuller route example, see this guide to building a Biswap cross-chain swap flow; the route mechanics are only part of the check, since the token’s accounting needs review too.

What happens to a rebasing token when you bridge it?

It depends on the bridge and the token form. A bridge that supports the token’s share accounting can preserve the relationship between your shares and the changing balance. A bridge that treats the token as a standard fixed-balance asset may not pass the rebase through to you.

The destination token might also be a wrapped or synthetic representation, rather than the same token contract used on the source chain. Its displayed units can remain unchanged while its value relative to the original token shifts. A wallet display alone cannot tell you which accounting model the route uses.

Before you bridge, identify the route’s relevant details:

• The exact token form you hold, such as a rebasing token or its wrapped counterpart.
• Whether the bridge locks and mints, burns and mints, or uses another transfer model.
• Whether the destination asset tracks shares, rebases, or keeps a fixed unit balance.
• How and when you can redeem the destination asset for the original token.

These details affect what you receive and how rewards are reflected. A fixed destination balance is not automatically a loss: a wrapped token may accrue value per unit instead. But if the bridge holds the rebasing asset and the destination representation does not account for its rebase, you should not assume the rewards will reach your wallet.

How can you check your balance after bridging?

Compare the token’s units and its underlying value separately. The units answer how many tokens the destination contract records for your address; the underlying value depends on the conversion rate and the bridge’s accounting.

Use this sequence before you rely on the destination balance:

1. Record the source token and amount, including whether it is rebasing or wrapped.
2. Check the bridge route’s documentation or interface for the destination token and how it accounts for rebases.
3. After the transfer completes, verify the destination token contract and your on-chain balance, rather than relying only on a wallet’s cached display.
4. Check the current conversion or redemption rate, then compare the underlying amount you can claim with what you expected.

Rebases may not emit the usual transfer event, because no token moved between addresses. A wallet that relies on transfer history can therefore show a stale balance; refreshing the view or checking the contract’s current balance can help distinguish a display delay from the token’s actual accounting.

For most users, a bridge route designed for a non-rebasing wrapped form is easier to verify, provided you understand its conversion rate and redemption path. If you bridge the rebasing form directly, confirm that the bridge explicitly handles its share accounting. The useful check is not simply “did the tokens arrive?” It is “does the destination representation still account for the value and rewards I meant to carry?”