Send & Receive

Good decisions around Send & Receive depend on context more than on memorizing a screen. Receiving starts with confirming the network both sides intend to use. A copied address still deserves a visual check. Before sending, verify network, asset, and amount together. This page therefore follows a prepare, review, act, and verify sequence, with clear stop conditions whenever the network, target, amount, permission, or expected result does not match the user’s intent.

Before you begin

Use a trusted device and network
Confirm the active account and network
Read the full request before signing

On this page

Before you begin: Receiving starts with confirming the network both sides intend to use First execution stage: Before sending, verify network, asset, and amount together Second execution stage: Contract tokens differ from the network native asset Verify the result: Do not blindly resend while confirmation is pending Common mistakes and recovery: A small test transfer can validate an unfamiliar route

Before you begin: Receiving starts with confirming the network both sides intend to use

Focus on a copied address still deserves a visual check

First, in Send & Receive, the Before you begin: Receiving starts with confirming the network both sides intend to use stage should not be reduced to the next button. Receiving starts with confirming the network both sides intend to use. A copied address still deserves a visual check. For Send & Receive, the user should start by identifying the active network, then reread the account, network, address, asset, amount, and request summary in the order they will matter on-chain. The goal is to be able to explain what will happen, on which network, and to which target before approval. That discipline is more durable than memorizing where a control appears in one version of an interface.

First follow-up in Send & Receive: after the action described by Focus on a copied address still deserves a visual check, a success message should not be the only evidence used. Before sending, verify network, asset, and amount together. Insufficient gas assets can prevent submission. Keep the public identifiers needed for later review, such as the transaction hash, network, and target address, and verify them through the matching block explorer or wallet record. Remember to put public evidence ahead of visual familiarity. If the result differs from the expectation, establish what has already happened on-chain before attempting another signature or transfer, because a second submission may create a separate action rather than repair the first one.

Confirm receiving starts with confirming the network both sides intend to use.
Check how a copied address still deserves a visual check affects the current request.
Use before sending, verify network, asset, and amount together as a separate verification point.

First execution stage: Before sending, verify network, asset, and amount together

Focus on insufficient gas assets can prevent submission

Second, in Send & Receive, the First execution stage: Before sending, verify network, asset, and amount together stage should not be reduced to the next button. Before sending, verify network, asset, and amount together. Insufficient gas assets can prevent submission. For Send & Receive, the user should do not let a familiar label replace a technical check, then reread the account, network, address, asset, amount, and request summary in the order they will matter on-chain. The goal is to be able to explain what will happen, on which network, and to which target before approval. That discipline is more durable than memorizing where a control appears in one version of an interface.

Second follow-up in Send & Receive: after the action described by Focus on insufficient gas assets can prevent submission, a success message should not be the only evidence used. Contract tokens differ from the network native asset. A submitted transaction receives a trackable hash. Keep the public identifiers needed for later review, such as the transaction hash, network, and target address, and verify them through the matching block explorer or wallet record. Remember to confirm the object, then the action, then the result. If the result differs from the expectation, establish what has already happened on-chain before attempting another signature or transfer, because a second submission may create a separate action rather than repair the first one.

Confirm before sending, verify network, asset, and amount together.
Check how insufficient gas assets can prevent submission affects the current request.
Use contract tokens differ from the network native asset as a separate verification point.

Second execution stage: Contract tokens differ from the network native asset

Focus on a submitted transaction receives a trackable hash

Third, in Send & Receive, the Second execution stage: Contract tokens differ from the network native asset stage should not be reduced to the next button. Contract tokens differ from the network native asset. A submitted transaction receives a trackable hash. For Send & Receive, the user should stop when two pieces of context disagree, then reread the account, network, address, asset, amount, and request summary in the order they will matter on-chain. The goal is to be able to explain what will happen, on which network, and to which target before approval. That discipline is more durable than memorizing where a control appears in one version of an interface.

Third follow-up in Send & Receive: after the action described by Focus on a submitted transaction receives a trackable hash, a success message should not be the only evidence used. Do not blindly resend while confirmation is pending. Using the wrong network can change the expected arrival path. Keep the public identifiers needed for later review, such as the transaction hash, network, and target address, and verify them through the matching block explorer or wallet record. Remember to split a request into source, target, permission, and outcome. If the result differs from the expectation, establish what has already happened on-chain before attempting another signature or transfer, because a second submission may create a separate action rather than repair the first one.

Confirm contract tokens differ from the network native asset.
Check how a submitted transaction receives a trackable hash affects the current request.
Use do not blindly resend while confirmation is pending as a separate verification point.

Verify the result: Do not blindly resend while confirmation is pending

Focus on using the wrong network can change the expected arrival path

Fourth, in Send & Receive, the Verify the result: Do not blindly resend while confirmation is pending stage should not be reduced to the next button. Do not blindly resend while confirmation is pending. Using the wrong network can change the expected arrival path. For Send & Receive, the user should record the state before and after the action, then reread the account, network, address, asset, amount, and request summary in the order they will matter on-chain. The goal is to be able to explain what will happen, on which network, and to which target before approval. That discipline is more durable than memorizing where a control appears in one version of an interface.

Fourth follow-up in Send & Receive: after the action described by Focus on using the wrong network can change the expected arrival path, a success message should not be the only evidence used. A small test transfer can validate an unfamiliar route. On-chain transfers generally cannot be reversed by the wallet alone. Keep the public identifiers needed for later review, such as the transaction hash, network, and target address, and verify them through the matching block explorer or wallet record. Remember to understand why a confirmation is needed before approving it. If the result differs from the expectation, establish what has already happened on-chain before attempting another signature or transfer, because a second submission may create a separate action rather than repair the first one.

Confirm do not blindly resend while confirmation is pending.
Check how using the wrong network can change the expected arrival path affects the current request.
Use a small test transfer can validate an unfamiliar route as a separate verification point.

Common mistakes and recovery: A small test transfer can validate an unfamiliar route

Focus on on-chain transfers generally cannot be reversed by the wallet alone

Fifth, in Send & Receive, the Common mistakes and recovery: A small test transfer can validate an unfamiliar route stage should not be reduced to the next button. A small test transfer can validate an unfamiliar route. On-chain transfers generally cannot be reversed by the wallet alone. For Send & Receive, the user should treat network context as a prerequisite for every step, then reread the account, network, address, asset, amount, and request summary in the order they will matter on-chain. The goal is to be able to explain what will happen, on which network, and to which target before approval. That discipline is more durable than memorizing where a control appears in one version of an interface.

Fifth follow-up in Send & Receive: after the action described by Focus on on-chain transfers generally cannot be reversed by the wallet alone, a success message should not be the only evidence used. Receiving starts with confirming the network both sides intend to use. A copied address still deserves a visual check. Keep the public identifiers needed for later review, such as the transaction hash, network, and target address, and verify them through the matching block explorer or wallet record. Remember to prefer public records that can be checked again later. If the result differs from the expectation, establish what has already happened on-chain before attempting another signature or transfer, because a second submission may create a separate action rather than repair the first one.

Confirm a small test transfer can validate an unfamiliar route.
Check how on-chain transfers generally cannot be reversed by the wallet alone affects the current request.
Use receiving starts with confirming the network both sides intend to use as a separate verification point.

Practical checklist

Review receiving starts with confirming the network both sides intend to use.
Review before sending, verify network, asset, and amount together.
Review contract tokens differ from the network native asset.
Review do not blindly resend while confirmation is pending.
Review a small test transfer can validate an unfamiliar route.