WalletPractical security / Attention before approval
Your destination. Your network.
Your decision.
Participation in a decentralised network starts with informed decisions. Keep your intention, the destination and the signing tool in view throughout each request.
A closer look at the request
Explore four checkpoints for reviewing an action: intention, destination, network and permission.
SourceDestination
Review the application
and requested access.
Read the transaction
in the signing tool.
A connection is not a transaction approval.
Compare the asset, amount and fee with the action you intended. Read the request in your signing tool, even when you began from a familiar interface.
An unexpected request deserves a pause. Do not approve it merely because it follows a previous action or appears inside a familiar workflow.
Verify the complete destination address rather than relying only on the first and last characters. Compare it with an independently checked source.
Check the asset denomination as well as the name. Similar tickers or labels do not establish that two assets or routes are equivalent.
Check the selected network and, for a cross-chain transfer, the source, destination, asset and channel. The interface must support the intended route.
A shielded step does not erase information exposed before or after it. Transparent endpoints and application behaviour remain part of the privacy context.
Read which application is requesting access and what it is asking you to authorise. A website connection and a transaction approval are separate decisions.
Review active sessions in the relevant application’s controls and disconnect those you no longer need. Keep access permissions aligned with the tools you choose to use.
Recovery information / A personal boundary
Keep recovery phrases and private keys out of websites, messages, screenshots and cloud notes. This website never requests them, and the local help panel does not need them to find guidance.
Someone offering to verify an account by receiving a transfer or a recovery phrase is not following the support workflow on this website. Stop and verify the source independently.
Find help without account accessApplication & host
Open trusted bookmarks rather than links in unsolicited messages. Verify the publisher of an application package and read the relevant installation instructions.
A familiar name, visual identity or version number is not proof of the source. If an installed application cannot open, review its package instructions before changing system security settings.
Prepare a desktop sessionEvidence & scope
Namada’s security materials document reviews of named protocol components and interfaces. Read the scope, completion date and findings for the component you are evaluating.
Assess a review alongside the product version, application publisher and intended operation. Keep protocol evidence and application-specific security information in their respective contexts.
Understand tool responsibilitiesBefore you continue
External chains, transparent transactions, previously exposed addresses and application behaviour can reveal information. Review the complete path, including what happens outside the shielded set.
Check the application and relevant network status before submitting again. An interface delay does not necessarily mean an action failed; repeating it may create a second transaction.
The help panel matches topics locally in your browser. Account information and transaction authorisation stay in your application and signing tool; recovery information stays private.