On this page
creation and import
The wallet guides follow an actual workflow from creation and backup through receiving, sending, history and permissions. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For creation and import, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.
If a balance is missing, verify network and contract first; if a transaction is pending, check the hash and network conditions first. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate creation and import workflow requires a seed phrase, private key or verification code to be sent to another person.
backup and recovery
If a balance is missing, verify network and contract first; if a transaction is pending, check the hash and network conditions first. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate backup and recovery workflow requires a seed phrase, private key or verification code to be sent to another person.
Every guide treats seed phrases and private keys as secrets that should never be shared with anyone. If the action includes a signature, approval or contract call, inspect the permission scope and possible asset impact separately. Friendly labels are not a substitute for the underlying request. Check the target, asset, amount or allowance, network and final confirmation details before proceeding. This sequence reduces mistakes caused by urgency, phishing or the wrong network.
- Verify the network, address and public on-chain information relevant to backup and recovery.
- Never send a seed phrase, private key or verification code to anyone.
- For DApps or contracts, review each signature and approval scope separately.
receiving and sending assets
Every guide treats seed phrases and private keys as secrets that should never be shared with anyone. If the action includes a signature, approval or contract call, inspect the permission scope and possible asset impact separately. Friendly labels are not a substitute for the underlying request. Check the target, asset, amount or allowance, network and final confirmation details before proceeding. This sequence reduces mistakes caused by urgency, phishing or the wrong network.
The wallet guides follow an actual workflow from creation and backup through receiving, sending, history and permissions. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For receiving and sending assets, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.
transaction history and troubleshooting
The wallet guides follow an actual workflow from creation and backup through receiving, sending, history and permissions. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For transaction history and troubleshooting, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.
If a balance is missing, verify network and contract first; if a transaction is pending, check the hash and network conditions first. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate transaction history and troubleshooting workflow requires a seed phrase, private key or verification code to be sent to another person.
- Verify the network, address and public on-chain information relevant to transaction history and troubleshooting.
- Never send a seed phrase, private key or verification code to anyone.
- For DApps or contracts, review each signature and approval scope separately.