WalletA guide to transaction context
Identify the network, the application and the intended action. A clear view of the whole route makes the details easier to evaluate.
Explore IBC network identities, then review the source, destination, asset denomination and channel for your intended route.
SOURCE CONTEXTCosmos HubATOMDESTINATION CONTEXTRead the entire address and compare it with an independently checked source. A matching beginning and ending is not enough.
Compare the destination, asset, amount, network and fee with your intention. Verify addresses in full rather than relying only on the first few characters. Read permission requests and stop if an application asks for something unexpected.
Check the status in the application and on the relevant network before submitting again. A slow interface does not necessarily mean a transaction failed. Repeating an action may create a second transaction.
An IBC transfer involves a source, destination and a specific route. Verify the channel and asset denomination in the tools you use. Do not assume that similar asset names identify the same asset or that a bridge route is supported by every interface.
Namada supports both transparent and shielded activity. Information already exposed on a transparent chain or in an application is not automatically hidden by a later shielded action. Consider the whole workflow.
Never send recovery phrases, private keys or credentials to anyone offering transaction help. Use your application and signing tool to review account information and authorise actions.
Understand Namada network layers Review safer use