How to bridge a rebasing token without losing track of its value

Lido’s stETH updates holder balances daily, so a bridge must account for rebases as well as the transfer itself. The key is to check whether you’re moving rebasing tokens, fixed balance shares or a destination token with its own supply rules.

A bridge usually locks tokens on one chain and releases or mints a representation on another. If the token’s balance can change while it is locked, the bridge and destination contract need a clear way to account for that change.

For the route and settlement details behind cross-chain swaps, see the mayan bridge guide. The token’s rebasing rules are a separate question, and they determine what the amount on the destination chain means.

Why can a rebasing token cause bridge problems?

A rebasing token changes the number of units in a holder’s balance to reflect a change in value or supply. With stETH, for example, the balance updates when Lido’s oracle reports a change in the underlying staking balance.

That can complicate a bridge that expects the number deposited to stay fixed. If the tokens are locked and their balance changes, the bridge must know whether to release the original amount, the updated amount or a corresponding claim on the asset.

For you, the risk is a confusing mismatch: the destination wallet may show a fixed number even though the amount represents a changing claim. A supported route should spell out which token you receive and how its value relates to the original.

What does bridging the token as shares mean?

A share token keeps your unit count steady while the value represented by each share changes. Lido’s wstETH is an example: it wraps stETH into a non-rebasing balance, with each share representing a changing amount of stETH.

This can make transfers and accounting easier because the bridge handles a fixed number of shares. You can compare it to owning shares in a fund: your share count stays the same while each share’s claim on the underlying assets can change.

But the destination needs to support the share token, and you need to understand its conversion rate. A token with the same ticker or similar name may not be the same asset or carry the same claim.

How do you check a bridge route before sending?

Check the route’s token details before you approve a transfer. Confirm the exact destination token, whether the route supports rebasing balances or uses a share representation, and what you can do with the token after arrival.

• Match the source and destination token contracts, not just the ticker.
• Check whether the quoted amount is in rebasing units or fixed shares.
• Confirm that the destination chain supports the token and any needed conversion.
• Review fees, minimums and the route’s return path before sending a large amount.

Some routes may instead convert the asset into a different token on the destination chain. That may be easier to use, but it can add price, liquidity and conversion risks; check what the route promises to deliver.

Which approach should you use?

For most users, a route that explicitly supports the token’s rebasing mechanics—or transfers a recognized share token—is easier to account for than a generic wrapped copy. It keeps the relationship between the amount sent and the amount received understandable.

Only send once the destination token and conversion rules are clear. Watch the bridge’s supported-token list and route quote before you transfer; those are the signals that determine what you’ll receive.