Osmosis
Native · osmosis-1The native token of Osmosis. Used for staking, governance and transaction costs. Staked tokens carry validator, unbonding and slashing risks.
Explore asset identities found around Osmosis. Origin, denomination and transfer path tell you more than a symbol alone.
Thirteen ecosystem identities. Explore their origins and save your favorites locally.
The native token of Osmosis. Used for staking, governance and transaction costs. Staked tokens carry validator, unbonding and slashing risks.
Read the origin, understand the route, and verify the exact representation.
Native assets originate on a chain. Bridged assets depend on a transfer mechanism and its security assumptions. IBC assets carry a denomination derived from their transfer path. Two tokens with the same ticker can have different origins, redemption options and risks.
The Osmosis frontend uses curated Chain Registry and assetlist metadata to help identify assets. Names, symbols, icons and network context are useful navigation aids, not guarantees of asset safety or a promise of desktop-wallet support.
A denomination such as ibc/<hash> points to a transfer trace. To understand it, inspect the source denomination and channel path. The hash itself is not a human-readable chain name, and reversing a route requires accurate counterparty information.
ibc/<hash>Copied icons and ticker collisions make visual recognition insufficient. Compare network, origin, full denomination and intended receiving asset. Favorites here are local reading preferences, not balances or assets synchronized with a wallet.
No. These are local informational records with no prices, liquidity figures or rankings.
It is an Osmosis alloyed-asset example built around qualifying Bitcoin representations, not native Bitcoin and not a removal of underlying risk.