On this page
Understand Create first
Wallet Guides brings several connected concepts together. A clear decision order is more reliable than memorizing interface steps. Create tells you what is being reviewed now, while Back up and Receive provide context for whether the next action makes sense. Before proceeding, confirm that the wallet and network are the ones you intended to use, then review the address, contract or request origin. If the purpose is unclear or the network does not match, stop rather than guessing.
A reliable Wallet Guides workflow keeps verifiable references such as the network name, address or contract address, transaction hash, block-explorer status and the exact permission being requested. Asset names and icons are useful hints but are not a substitute for on-chain identifiers. With Create, avoid confirming something simply because it looks familiar; spoofed pages, wrong networks and malicious requests are designed to exploit that shortcut.
After an action involving Create, review the result. If a transaction was created, use its hash to check broadcast, block inclusion and confirmations. If a DApp session or approval was created, identify the connected origin and permission scope, and consider disconnecting or revoking access when it is no longer needed. This turns a one-time action into a process you can verify later.
What to review in practice
- Confirm the active network is the one you intended and understand how Create relates to the action.
- Verify addresses, contracts and request origins rather than trusting names or icons alone.
- Before submission, review amount, gas, approval scope or signature details; afterward, keep verifiable on-chain references.
How Back up changes the workflow
To understand Back up, place it back inside the full Wallet Guides workflow. Back up tells you what is being reviewed now, while Receive and Send provide context for whether the next action makes sense. Before proceeding, confirm that the wallet and network are the ones you intended to use, then review the address, contract or request origin. If the purpose is unclear or the network does not match, stop rather than guessing.
A reliable Wallet Guides workflow keeps verifiable references such as the network name, address or contract address, transaction hash, block-explorer status and the exact permission being requested. Asset names and icons are useful hints but are not a substitute for on-chain identifiers. With Back up, avoid confirming something simply because it looks familiar; spoofed pages, wrong networks and malicious requests are designed to exploit that shortcut.
After an action involving Back up, review the result. If a transaction was created, use its hash to check broadcast, block inclusion and confirmations. If a DApp session or approval was created, identify the connected origin and permission scope, and consider disconnecting or revoking access when it is no longer needed. This turns a one-time action into a process you can verify later.
What to review in practice
- Confirm the active network is the one you intended and understand how Create relates to the action.
- Verify addresses, contracts and request origins rather than trusting names or icons alone.
- Before submission, review amount, gas, approval scope or signature details; afterward, keep verifiable on-chain references.
Build a review sequence around Receive
To understand Receive, place it back inside the full Wallet Guides workflow. Receive tells you what is being reviewed now, while Send and History provide context for whether the next action makes sense. Before proceeding, confirm that the wallet and network are the ones you intended to use, then review the address, contract or request origin. If the purpose is unclear or the network does not match, stop rather than guessing.
A reliable Wallet Guides workflow keeps verifiable references such as the network name, address or contract address, transaction hash, block-explorer status and the exact permission being requested. Asset names and icons are useful hints but are not a substitute for on-chain identifiers. With Receive, avoid confirming something simply because it looks familiar; spoofed pages, wrong networks and malicious requests are designed to exploit that shortcut.
After an action involving Receive, review the result. If a transaction was created, use its hash to check broadcast, block inclusion and confirmations. If a DApp session or approval was created, identify the connected origin and permission scope, and consider disconnecting or revoking access when it is no longer needed. This turns a one-time action into a process you can verify later.
What to review in practice
- Confirm the active network is the one you intended and understand how Create relates to the action.
- Verify addresses, contracts and request origins rather than trusting names or icons alone.
- Before submission, review amount, gas, approval scope or signature details; afterward, keep verifiable on-chain references.
Risks and common mistakes involving Send
To understand Send, place it back inside the full Wallet Guides workflow. Send tells you what is being reviewed now, while History and Create provide context for whether the next action makes sense. Before proceeding, confirm that the wallet and network are the ones you intended to use, then review the address, contract or request origin. If the purpose is unclear or the network does not match, stop rather than guessing.
A reliable Wallet Guides workflow keeps verifiable references such as the network name, address or contract address, transaction hash, block-explorer status and the exact permission being requested. Asset names and icons are useful hints but are not a substitute for on-chain identifiers. With Send, avoid confirming something simply because it looks familiar; spoofed pages, wrong networks and malicious requests are designed to exploit that shortcut.
After an action involving Send, review the result. If a transaction was created, use its hash to check broadcast, block inclusion and confirmations. If a DApp session or approval was created, identify the connected origin and permission scope, and consider disconnecting or revoking access when it is no longer needed. This turns a one-time action into a process you can verify later.
What to review in practice
- Confirm the active network is the one you intended and understand how Create relates to the action.
- Verify addresses, contracts and request origins rather than trusting names or icons alone.
- Before submission, review amount, gas, approval scope or signature details; afterward, keep verifiable on-chain references.
Turn History into a repeatable habit
To understand History, place it back inside the full Wallet Guides workflow. History tells you what is being reviewed now, while Create and Back up provide context for whether the next action makes sense. Before proceeding, confirm that the wallet and network are the ones you intended to use, then review the address, contract or request origin. If the purpose is unclear or the network does not match, stop rather than guessing.
A reliable Wallet Guides workflow keeps verifiable references such as the network name, address or contract address, transaction hash, block-explorer status and the exact permission being requested. Asset names and icons are useful hints but are not a substitute for on-chain identifiers. With History, avoid confirming something simply because it looks familiar; spoofed pages, wrong networks and malicious requests are designed to exploit that shortcut.
After an action involving History, review the result. If a transaction was created, use its hash to check broadcast, block inclusion and confirmations. If a DApp session or approval was created, identify the connected origin and permission scope, and consider disconnecting or revoking access when it is no longer needed. This turns a one-time action into a process you can verify later.
What to review in practice
- Confirm the active network is the one you intended and understand how Create relates to the action.
- Verify addresses, contracts and request origins rather than trusting names or icons alone.
- Before submission, review amount, gas, approval scope or signature details; afterward, keep verifiable on-chain references.