Create and import
Create and import is easier to manage when the interface label is separated from the actual on-chain object. In the context of Wallet Guides, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Create and import is to break the action into source, destination, permissions or amount, network state and final outcome. When create is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Create and import. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Create and import
- Keep verifiable public information when create is involved
- Never send a seed phrase, private key or verification code to anyone
Backup and recovery
Backup and recovery is easier to manage when the interface label is separated from the actual on-chain object. In the context of Wallet Guides, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Backup and recovery is to break the action into source, destination, permissions or amount, network state and final outcome. When backup is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Backup and recovery. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Backup and recovery
- Keep verifiable public information when backup is involved
- Never send a seed phrase, private key or verification code to anyone
Receive and send
Receive and send is easier to manage when the interface label is separated from the actual on-chain object. In the context of Wallet Guides, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Receive and send is to break the action into source, destination, permissions or amount, network state and final outcome. When transfer is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Receive and send. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Receive and send
- Keep verifiable public information when transfer is involved
- Never send a seed phrase, private key or verification code to anyone
Assets and transaction records
Assets and transaction records is easier to manage when the interface label is separated from the actual on-chain object. In the context of Wallet Guides, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Assets and transaction records is to break the action into source, destination, permissions or amount, network state and final outcome. When asset is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Assets and transaction records. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Assets and transaction records
- Keep verifiable public information when asset is involved
- Never send a seed phrase, private key or verification code to anyone
DApp connection and security checks
DApp connection and security checks is easier to manage when the interface label is separated from the actual on-chain object. In the context of Wallet Guides, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with DApp connection and security checks is to break the action into source, destination, permissions or amount, network state and final outcome. When dapp is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of DApp connection and security checks. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in DApp connection and security checks
- Keep verifiable public information when dapp is involved
- Never send a seed phrase, private key or verification code to anyone