Why token decimals matter in cross-chain route quotes

Token decimals determine how a cross-chain route quote turns on-chain amounts into the token amounts a user sees. A token balance is stored as a whole number of its smallest units, while decimals tell a wallet where to place the decimal point. If a route reads that number with the wrong decimal setting, the displayed amount can be wildly off even when the underlying transfer is handled correctly.

What do token decimals mean in a route quote?

Decimals are a display scale: a token with six decimals represents 1.25 tokens as 1,250,000 smallest units. A token with 18 decimals represents the same displayed amount as 1,250,000,000,000,000,000 units. The token contract handles whole numbers; software uses the decimal setting to show a human-readable balance.

A cross-chain route may take tokens on one network and deliver a corresponding token on another. The two token contracts can use different decimal settings. The quote system needs to interpret the source amount using the source token’s scale, then show the destination amount using the destination token’s scale. For a closer look at the transfer steps, see this guide to using the Bungee bridge to move tokens between chains. The key comparison is the readable amount and the token on each network, not the raw integers alone.

Why can the quoted amount look different across chains?

A difference in raw unit counts does not by itself mean that value has been lost. If a route converts between representations with different decimals, the same human-readable quantity can correspond to very different integers. Fees, exchange rates, and the route’s chosen steps can also change how many destination tokens the quote shows.

For example, a quote could start with 1.25 tokens represented as 1,250,000 source units and show a destination amount represented with 18 decimals. The destination raw integer may be much larger even if the readable amount is close to 1.25. A mismatch in token metadata can instead make an amount appear too large or too small by a factor of ten for each decimal place of error.

Quotes are estimates of a route’s expected output, not a promise that the final amount will match exactly. A route may include a swap, which exchanges one token for another, as well as a bridge transfer. Each step can affect the final amount. The quote should label the destination token and network, and the displayed output should make sense alongside the input and stated fees.

What should you check before using a quote?

Check the token and network on both sides, then compare the readable amounts. A familiar ticker symbol is not enough to identify a token, since different contracts can use the same symbol. Before signing, confirm that the receiving asset is the one you intended and that the quote’s output and fees are acceptable.

• Confirm the source and destination networks.
• Check the token contract or verified asset label on each network.
• Compare readable token amounts, not raw unit counts.
• Review the minimum received amount and any rounding shown before signing.

Rounding matters most for small transfers. If the destination token allows fewer decimal places, a tiny remainder may not fit in its smallest unit and can be rounded down. For most readers, the useful habit is simple: judge a route by the displayed destination asset, expected amount, and fees together. Decimal settings explain how those amounts are written; they do not, on their own, tell you whether a route offers good value.