HYBRID DEVNET · PUBLIC EVIDENCE LIVEVerifiable infrastructure for value, markets, identity, and operational dataInspect the network

Funding & transfers

How do we distinguish assets with the same symbol on different chains?

3 min read

Keep the asset’s network and chain-specific identifier alongside its display symbol. This avoids treating matching labels as evidence that two tokens or routes are interchangeable.

A familiar ticker is not a unique identity

Names and symbols are designed for people to recognize, but they are not sufficient to identify a token. Different networks can contain assets with matching labels, and a token contract can be distinct from another contract using the same name. Treat the network and chain-specific identifier as part of the asset description. This is why an application should keep more than a three- or four-letter symbol when it stores a payment or portfolio record.

What a user should compare

Before sending, compare the asset, selected network, recipient’s supported network, and any relevant token contract or native-asset identifier. Use the intended wallet’s receiving instructions, not a random search result. In Explorer, inspect the network context alongside the asset record. A correct-looking address is not enough if the receiving workflow expects a different network. If the labels disagree, clarify the route before authorizing rather than hoping the interface will translate it automatically.

What a business application should preserve

Keep these identifiers with the amount and transaction reference through the entire journey, including reports and support tools. Do not merge two balances solely because their symbols match. If a conversion or cross-chain route is intended, represent that as its own supported workflow with its own outcome and charges. This makes reconciliation more reliable and gives users a clear explanation of what they hold, what they are sending, and where the recipient will receive it.

Illustrative example

A payment review displays both the token identifier and selected network instead of showing only a stablecoin ticker.

In plain language

The network is part of the address and asset

A currency symbol is a convenient label, not a complete destination. Two networks can use similar-looking addresses, and tokens with the same ticker can exist on more than one chain. The safe description includes the asset, its network, and any chain-specific token identifier, as well as the recipient address. Mainnet, Testnet, and Devnet are also separate contexts: a test balance is not a production balance simply because both screens show a familiar name. Before any external transfer, obtain the receiving details from the intended, authorized wallet workflow and compare the network at both ends. Do not choose a different network just because it appears cheaper without confirming the whole route. A shared application can make these choices easier to manage, but it cannot erase the differences between the underlying chains. If the destination or route is unclear, stop before authorizing the transfer and ask for clarification.

In plain language

Why several reference numbers can describe one journey

A business request, a payment-provider record, a Hybrid-Chain event, and an external blockchain transaction can each have their own identifier. These are not competing names for the same database row. They identify different parts of a journey, just as an order number and a parcel tracking number describe related but different records. Keep the relationship between them rather than overwriting one with another. A hash is a compact cryptographic fingerprint used to identify or commit to data; a UUID is another kind of record identifier. Neither should be interpreted from its appearance alone. Use the label beside it and the system that issued it. When asking for help, include the network and the type of reference as well as the value. This makes it much easier to distinguish a missing link from a failed operation and avoids searching an external chain for an internal reference.

Conditions & limitations

A familiar symbol does not establish asset identity, redeemability, a supported route, or permission to transfer.

What to do next

Use the identifiers required by the exact API contract and validate the destination network in your workflow.

V2 API reference ↗Funding & Settlement ↗