How to Bridge Rebasing Tokens Without Losing Rewards
To move a rebasing token safely, check that the route supports rebases or wrap the token first; stETH can update its balance once a day. A rebasing token changes the number shown in your wallet as rewards or penalties accrue, without a regular transfer.
Why can a rebasing token cause trouble on a bridge?
A bridge often locks your tokens on the starting network and creates or releases a matching token on the destination. If the locked balance changes later, the destination token may not change with it.
For example, if a bridge locks 100 stETH, later rewards may increase the balance held by its contract. Unless the bridge tracks and passes those changes across networks, your destination balance may not receive them. Lido’s token integration guide warns that rewards can collect in the bridge contract instead.
Super Bridge brings together native bridges and third-party providers, so a route’s token support depends on the provider handling the transfer. For a transfer from Ethereum to another network, Super Bridge routes lets you compare available routes; check the selected provider’s support for your exact token before approving.
How does a bridge handle balance changes?
A bridge must account for the token’s changing balance across both networks. Some tokens track ownership as shares, which represent a portion of the total supply; the displayed balance is then calculated from those shares and can change when the exchange rate changes.
Other bridges may be built for tokens with fixed balances. They lock or burn a set amount on one network and issue or release that same amount on the other. If a provider does not account for rebases, a later balance change on the starting network does not automatically update the destination token.
That is why support is specific to the token and route. A provider might accept a token on one network but not support its rebasing behavior, or it might only support a wrapped version. The Wormhole Token Bridge whitepaper describes support for rebasing tokens as a design requirement; that does not mean every bridge or route supports every rebasing token.
Should you wrap the token before transferring it?
If the provider does not clearly support the rebasing token, use a non-rebasing wrapped version when the token issuer recommends one. Wrapping exchanges a token whose displayed balance changes for one with a fixed balance; rewards instead show up as a changing exchange rate when you unwrap.
Lido’s documentation describes this option for stETH: wstETH keeps a fixed token balance, while its value in stETH changes. You can wrap stETH on the starting network, bridge wstETH, then unwrap only where an official wrapper supports it. A destination’s bridged wstETH may not be locally unwrapable, so check before sending.
The trade-off is an extra transaction and its network fee, plus the need to confirm the destination token is the intended asset. Wrapping also does not remove bridge risk: the provider still holds or represents your assets during the transfer.
What should you check before approving?
Check the route’s provider, the exact token name and network at both ends, and whether the provider explicitly supports rebases. Read the amount shown for the destination asset; for wrapped tokens, compare its exchange rate rather than expecting a one-for-one token count.
A common mistake is to see the token’s familiar name in a route and assume its rewards will follow. Fix that by checking the provider’s token details, then wrapping first if the issuer recommends it and the destination supports the wrapped asset. For a few transfers a year, that extra check can prevent rewards from staying behind in a bridge contract.
Before you approve, compare the available routes in Super Bridge, confirm the selected provider supports the token form you intend to send, and make sure you can use the received asset on the destination network.