Send & Receive
Blockchain transfers generally cannot be unilaterally reversed by a wallet. Receiving starts with network and address checks; sending also requires reviewing amount, gas, recipient and the final signing request.
On this page
Confirm the network when receiving
Before sharing an address, state the intended receiving network and confirm that the asset is supported there. An address without network context can easily lead to the wrong chain.
A common mistake is to treat a normal-looking interface as proof that the underlying blockchain action is correct. Public addresses, transaction hashes, contract addresses and network parameters provide independent ways to verify what is happening.
Use a three-part send check
Before sending, verify recipient, network and amount, and confirm that sufficient gas is available for token transfers. For higher-value operations, a small test can validate the path first.
A repeatable order of checks is more reliable than memory. Review source, network, account, target and expected outcome each time so the same safety logic carries across wallets and DApps.
Understand gas and failures
Gas pays for network execution. A failed transaction does not necessarily mean every fee is returned; outcomes depend on the network and execution path, so avoid repeatedly retrying without diagnosis.
When a task involves a third-party contract, bridge, validator or web service, separate that external risk from the wallet itself. A wallet can display and sign a request, but it cannot guarantee the safety of outside code or services.
Track with the transaction hash
Keep the transaction hash and review status, block height, sender, recipient and amount on the correct network explorer. If the interface is delayed, do not resend the same transfer blindly.
Put this concept back into the current network, account and request type before acting. Identify what the interface is asking for, then decide whether a signature, gas payment or ongoing permission is actually required.
Practical checklist
- Confirm that “Confirm the network when receiving” matches the task you intend to perform
- Confirm that “Use a three-part send check” matches the task you intend to perform
- Confirm that “Understand gas and failures” matches the task you intend to perform
- Confirm that “Track with the transaction hash” matches the task you intend to perform
Risk reminder
Seed phrases and private keys remain under the user’s control. Legitimate support should not ask for a seed phrase, private key or verification code. Review address, network and amount before transferring; blockchain transactions generally cannot be unilaterally reversed by a wallet. Third-party DApps and smart contracts carry risk, so review spender and permission scope and consider revoking unused approvals.