imtoken Knowledge Center
Signature Requests｜imtoken
Distinguish message, transaction and structured-data signatures before approving any request.
On this page
What a signature represents
To understand Signature Requests, place what a signature represents inside the full on-chain workflow instead of treating it as an isolated label. Check the domain and the intended network before connecting. Connection, signature, transaction and approval are separate decisions. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. Each request should be reviewed on its own rather than approved automatically. End a session by disconnecting and reviewing any new approvals. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach what a signature represents is to use a consistent review sequence. First, check the domain and the intended network before connecting. Next, connection, signature, transaction and approval are separate decisions. After a transaction, signature or approval is submitted, each request should be reviewed on its own rather than approved automatically. Finally, end a session by disconnecting and reviewing any new approvals. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- Check the domain and the intended network before connecting
- Connection, signature, transaction and approval are separate decisions
- Each request should be reviewed on its own rather than approved automatically
- End a session by disconnecting and reviewing any new approvals
Message signatures
To understand Signature Requests, place message signatures inside the full on-chain workflow instead of treating it as an isolated label. Check the domain and the intended network before connecting. Connection, signature, transaction and approval are separate decisions. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. Each request should be reviewed on its own rather than approved automatically. End a session by disconnecting and reviewing any new approvals. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach message signatures is to use a consistent review sequence. First, check the domain and the intended network before connecting. Next, connection, signature, transaction and approval are separate decisions. After a transaction, signature or approval is submitted, each request should be reviewed on its own rather than approved automatically. Finally, end a session by disconnecting and reviewing any new approvals. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- Check the domain and the intended network before connecting
- Connection, signature, transaction and approval are separate decisions
- Each request should be reviewed on its own rather than approved automatically
- End a session by disconnecting and reviewing any new approvals
Transaction signatures
To understand Signature Requests, place transaction signatures inside the full on-chain workflow instead of treating it as an isolated label. Check the domain and the intended network before connecting. Connection, signature, transaction and approval are separate decisions. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. Each request should be reviewed on its own rather than approved automatically. End a session by disconnecting and reviewing any new approvals. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach transaction signatures is to use a consistent review sequence. First, check the domain and the intended network before connecting. Next, connection, signature, transaction and approval are separate decisions. After a transaction, signature or approval is submitted, each request should be reviewed on its own rather than approved automatically. Finally, end a session by disconnecting and reviewing any new approvals. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- Check the domain and the intended network before connecting
- Connection, signature, transaction and approval are separate decisions
- Each request should be reviewed on its own rather than approved automatically
- End a session by disconnecting and reviewing any new approvals
When a request is unclear
To understand Signature Requests, place when a request is unclear inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify when a request is unclear in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach when a request is unclear is to use a consistent review sequence. First, the practical point is to verify when a request is unclear in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- The practical point is to verify when a request is unclear in the context of the selected blockchain network
- The user should compare the request with the intended address, asset, account or contract before confirming
- On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
- Third-party DApps, services and smart contracts can introduce risks that need separate review