Identify the issue
Identify the issue is a distinct part of understanding Support. Support focuses on self-service diagnostics: confirm the network, check a transaction hash, identify the request type, review approvals and inspect the device environment. Support will never ask for a seed phrase or private key. Ethereum staking and validator participation should be understood through PoS rules, reward sources, validator status, withdrawals and exits. Rewards can change, exits can involve waiting, validators can face protocol penalties, and smart contracts or third-party services add technical risk.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
Transaction checks
Transaction checks is a distinct part of understanding Support. Support focuses on self-service diagnostics: confirm the network, check a transaction hash, identify the request type, review approvals and inspect the device environment. Support will never ask for a seed phrase or private key. Ethereum staking and validator participation should be understood through PoS rules, reward sources, validator status, withdrawals and exits. Rewards can change, exits can involve waiting, validators can face protocol penalties, and smart contracts or third-party services add technical risk.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
- Confirm the active network before sending or approving.
- Compare the full destination or contract details.
- Keep recovery material offline and private.
Security incidents
Security incidents is a distinct part of understanding Support. Support focuses on self-service diagnostics: confirm the network, check a transaction hash, identify the request type, review approvals and inspect the device environment. Support will never ask for a seed phrase or private key. Ethereum staking and validator participation should be understood through PoS rules, reward sources, validator status, withdrawals and exits. Rewards can change, exits can involve waiting, validators can face protocol penalties, and smart contracts or third-party services add technical risk.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
Self-service resources
Self-service resources is a distinct part of understanding Support. Support focuses on self-service diagnostics: confirm the network, check a transaction hash, identify the request type, review approvals and inspect the device environment. Support will never ask for a seed phrase or private key. Ethereum staking and validator participation should be understood through PoS rules, reward sources, validator status, withdrawals and exits. Rewards can change, exits can involve waiting, validators can face protocol penalties, and smart contracts or third-party services add technical risk.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
Security and risk reminder
Blockchain transactions are generally irreversible by a wallet provider. Third-party DApps and smart contracts can contain technical or business risks. Review every signature and approval independently, and consider revoking permissions you no longer use.