How Rebasing Tokens Work Across Chains

A rebasing token changes the balance in your wallet as its underlying value changes. Across chains, that only works if the bridge and destination token account for those changes; a basic lock-and-mint bridge may leave rewards behind.

Lido’s stETH is one example: its balance updates as staking rewards or penalties change the holder’s share of the pooled ether. Its wrapped version, wstETH, keeps a fixed token balance while the amount of stETH each token represents can change.

How does a rebasing token change your balance?

A rebasing token tracks your portion of a pool, often as shares. The token balance is calculated from those shares and the pool’s current value, so a rebase can change the displayed balance without a transfer to your wallet.

A bridge that locks tokens on one chain and mints a fixed amount on another may not pass along that balance change. If the locked tokens earn rewards inside the bridge contract, the destination token will not automatically reflect them.

If you are also choosing an integration route, read Acrossbridge’s swap-versus-bridge choice for that separate decision. For a rebasing asset, the key question is whether the route carries the asset’s changing share value to the destination.

What happens when you bridge a rebasing token?

The result depends on how the bridge and destination token are built. A destination token can use share accounting, or the bridge can send rate updates so the token reflects the changing value of its backing.

That design has trade-offs. Share accounting can preserve the asset’s rebasing behavior, but it needs compatible contracts on the destination chain. Rate updates can keep balances fixed while value accrues, but users and apps depend on those updates arriving correctly.

Before using a route, check:

• Whether the destination token rebases or uses a fixed-balance wrapper.
• How rewards or penalties on the original token reach the destination.
• Who can send or pause rate updates, and what happens if an update is delayed.
• Whether the destination token can be redeemed for the intended underlying asset.

These checks matter because a familiar ticker or token name does not prove that two chain versions handle rewards the same way. Confirm the route and token contract details before sending a balance you expect to keep rebasing.

Is a wrapped token better for cross-chain use?

For most users and apps, a non-rebasing wrapper is simpler to bridge. The token count stays fixed, while its exchange rate against the rebasing asset reflects accrued rewards; wstETH uses this model for stETH.

A direct rebasing token can still make sense when the destination supports its share accounting and reward updates. The signal to watch is the route’s next rate update and whether the destination balance or exchange rate reflects it as promised.