Signature Requests

Core concepts

Seed phrases and private keys remain under the user’s control. Official staff will not ask for them, and they should never be sent through chat, email or web forms. In the context of message signatures, it also helps to connect transaction signatures with origin domains rather than treating them as isolated features. Before transferring, signing or approving, review the domain, address, network, amount, target contract and permission scope. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare message signatures with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Practical workflow

Before transferring, signing or approving, review the domain, address, network, amount, target contract and permission scope. In the context of transaction signatures, it also helps to connect origin domains with readable content rather than treating them as isolated features. Public computers, remote-control sessions, unknown Wi-Fi and untrusted apps increase exposure around sensitive actions. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare transaction signatures with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Checks before confirmation

Public computers, remote-control sessions, unknown Wi-Fi and untrusted apps increase exposure around sensitive actions. In the context of origin domains, it also helps to connect readable content with message signatures rather than treating them as isolated features. After use, review DApp sessions and approvals and consider removing permissions that are no longer needed. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare origin domains with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Risks and follow-up

After use, review DApp sessions and approvals and consider removing permissions that are no longer needed. In the context of readable content, it also helps to connect message signatures with transaction signatures rather than treating them as isolated features. Seed phrases and private keys remain under the user’s control. Official staff will not ask for them, and they should never be sent through chat, email or web forms. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare readable content with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Key risks

• Never share a seed phrase, private key or verification code.
• Third-party DApps, networks and contracts can fail or behave maliciously.
• Staking and digital assets do not offer guaranteed returns or protection from price volatility.