Knowledge & Services
Wallet Guides
Wallet Guides explains create and recover, receive assets, send transactions and asset troubleshooting with practical wallet, network and Web3 checks.
Create and recover
This section focuses on create and recover and how it affects a practical wallet, network or Web3 workflow.
A practical review of create and recover separates origin, target, permission or value, and network state. Connections, message signatures, transaction signatures and token approvals are distinct requests; review the spender, allowance and expected effect separately. If a contract is unfamiliar, an allowance is unexpectedly broad, the network is wrong, or the result does not match your intent, stop and verify the transaction hash, contract address or block state before continuing.
Understanding create and recover also means considering what remains true after you confirm. Transaction hashes, block height, contract addresses and event logs provide useful verification points for distinguishing interface delays from actual on-chain state. On-chain transactions generally cannot be reversed by a wallet alone, and a DApp connection is not the same as an approval. The confirmation button is only the final step; the important work happens before it.
More broadly, create and recover rarely stands alone. It usually connects to at least one of the following: an address, an active network, gas, a transaction hash, a DApp request or validator state. Reading those pieces together reduces errors caused by choosing the wrong chain, misunderstanding a permission or misreading a pending state.
- Verify the active network, address or contract target
- Keep a transaction hash or other public data that can be independently checked
- Never provide a seed phrase, private key or verification code to anyone
Receive assets
This section focuses on receive assets and how it affects a practical wallet, network or Web3 workflow.
Understanding receive assets also means considering what remains true after you confirm. Transaction hashes, block height, contract addresses and event logs provide useful verification points for distinguishing interface delays from actual on-chain state. On-chain transactions generally cannot be reversed by a wallet alone, and a DApp connection is not the same as an approval. The confirmation button is only the final step; the important work happens before it.
Security around receive assets should be considered together with seed phrases, private keys, device conditions and permission management. Separate chains maintain separate state, and similar-looking address formats do not make networks interchangeable; use the correct block explorer when you need public verification. A legitimate workflow does not require sending recovery secrets or verification codes to another person or entering them into an unknown webpage.
More broadly, receive assets rarely stands alone. It usually connects to at least one of the following: an address, an active network, gas, a transaction hash, a DApp request or validator state. Reading those pieces together reduces errors caused by choosing the wrong chain, misunderstanding a permission or misreading a pending state.
- Verify the active network, address or contract target
- Keep a transaction hash or other public data that can be independently checked
- Never provide a seed phrase, private key or verification code to anyone
Send transactions
This section focuses on send transactions and how it affects a practical wallet, network or Web3 workflow.
Security around send transactions should be considered together with seed phrases, private keys, device conditions and permission management. Transaction hashes, block height, contract addresses and event logs provide useful verification points for distinguishing interface delays from actual on-chain state. A legitimate workflow does not require sending recovery secrets or verification codes to another person or entering them into an unknown webpage.
For send transactions, begin by identifying the active network, the exact address or contract involved, and the result you actually intend to achieve. Separate chains maintain separate state, and similar-looking address formats do not make networks interchangeable; use the correct block explorer when you need public verification. This turns an interface prompt into information that can be independently checked instead of relying on a name, icon or single status label.
More broadly, send transactions rarely stands alone. It usually connects to at least one of the following: an address, an active network, gas, a transaction hash, a DApp request or validator state. Reading those pieces together reduces errors caused by choosing the wrong chain, misunderstanding a permission or misreading a pending state.
- Verify the active network, address or contract target
- Keep a transaction hash or other public data that can be independently checked
- Never provide a seed phrase, private key or verification code to anyone
Asset troubleshooting
This section focuses on asset troubleshooting and how it affects a practical wallet, network or Web3 workflow.
For asset troubleshooting, begin by identifying the active network, the exact address or contract involved, and the result you actually intend to achieve. Separate chains maintain separate state, and similar-looking address formats do not make networks interchangeable; use the correct block explorer when you need public verification. This turns an interface prompt into information that can be independently checked instead of relying on a name, icon or single status label.
A practical review of asset troubleshooting separates origin, target, permission or value, and network state. Fees, confirmation speed and contract behavior change with network conditions, so wallet estimates should be interpreted in the context of the active chain. If a contract is unfamiliar, an allowance is unexpectedly broad, the network is wrong, or the result does not match your intent, stop and verify the transaction hash, contract address or block state before continuing.
More broadly, asset troubleshooting rarely stands alone. It usually connects to at least one of the following: an address, an active network, gas, a transaction hash, a DApp request or validator state. Reading those pieces together reduces errors caused by choosing the wrong chain, misunderstanding a permission or misreading a pending state.
- Verify the active network, address or contract target
- Keep a transaction hash or other public data that can be independently checked
- Never provide a seed phrase, private key or verification code to anyone