Seed phrases, private keys and control
Seed phrases, private keys and control is easier to manage when the interface label is separated from the actual on-chain object. In the context of Security, 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 Seed phrases, private keys and control is to break the action into source, destination, permissions or amount, network state and final outcome. When seed 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 Seed phrases, private keys and control. 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 Seed phrases, private keys and control
- Keep verifiable public information when seed is involved
- Never send a seed phrase, private key or verification code to anyone
Basic checks before transfers
Basic checks before transfers is easier to manage when the interface label is separated from the actual on-chain object. In the context of Security, 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 Basic checks before transfers is to break the action into source, destination, permissions or amount, network state and final outcome. When private key 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 Basic checks before transfers. 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 Basic checks before transfers
- Keep verifiable public information when private key is involved
- Never send a seed phrase, private key or verification code to anyone
DApp signatures and approvals
DApp signatures and approvals is easier to manage when the interface label is separated from the actual on-chain object. In the context of Security, 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 signatures and approvals is to break the action into source, destination, permissions or amount, network state and final outcome. When approval 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 signatures and approvals. 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 signatures and approvals
- Keep verifiable public information when approval is involved
- Never send a seed phrase, private key or verification code to anyone
Device, network and clipboard risks
Device, network and clipboard risks is easier to manage when the interface label is separated from the actual on-chain object. In the context of Security, 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 Device, network and clipboard risks is to break the action into source, destination, permissions or amount, network state and final outcome. When device 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 Device, network and clipboard risks. 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 Device, network and clipboard risks
- Keep verifiable public information when device is involved
- Never send a seed phrase, private key or verification code to anyone
Limiting damage after an incident
Limiting damage after an incident is easier to manage when the interface label is separated from the actual on-chain object. In the context of Security, 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 Limiting damage after an incident is to break the action into source, destination, permissions or amount, network state and final outcome. When phishing 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 Limiting damage after an incident. 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 Limiting damage after an incident
- Keep verifiable public information when phishing is involved
- Never send a seed phrase, private key or verification code to anyone