Connections, Signatures and Approvals
Signature Requests: Messages & Transactions is easier to use safely when you separate what the wallet interface shows from what the blockchain actually records. In practice, you should consider 消息签名, 交易签名, and 域名 together. A wallet can prepare and broadcast a request, but the final state is determined by the selected network and the transaction that network accepts.
Before taking action, confirm that 交易签名 matches what you intend to do, then review 域名 and Nonce. If a page, DApp, or third-party service asks for a seed phrase, private key, recovery phrase, or verification code, stop. imtoken will not ask you to disclose those secrets, and they should never be sent to another person.
Blockchain actions are often difficult or impossible for a wallet provider to reverse on its own. When evaluating 域名, prefer verifiable information such as the network name, destination address, transaction hash, contract address, and block explorer records instead of relying only on screenshots, chat messages, or unfamiliar links.
If something looks wrong around 合约调用, avoid repeatedly submitting the same action. Record the network, address, and transaction hash first, then determine whether the request was broadcast, is waiting for confirmation, or failed because of fees or parameters. Repeated attempts can add cost and make troubleshooting harder.
The practical goal here is to understand“签名”并非单一行为，每次请求都要独立判断. When information cannot be verified, pause and return to on-chain records or official pages instead of relying on someone else's assurance.
The Full Interaction Flow
Before taking action, confirm that 交易签名 matches what you intend to do, then review 域名 and Nonce. If a page, DApp, or third-party service asks for a seed phrase, private key, recovery phrase, or verification code, stop. imtoken will not ask you to disclose those secrets, and they should never be sent to another person.
Blockchain actions are often difficult or impossible for a wallet provider to reverse on its own. When evaluating 域名, prefer verifiable information such as the network name, destination address, transaction hash, contract address, and block explorer records instead of relying only on screenshots, chat messages, or unfamiliar links.
If something looks wrong around 合约调用, avoid repeatedly submitting the same action. Record the network, address, and transaction hash first, then determine whether the request was broadcast, is waiting for confirmation, or failed because of fees or parameters. Repeated attempts can add cost and make troubleshooting harder.
For 消息签名, a repeatable review order is useful: verify the source, verify the network, verify the counterparty or contract, review the requested permission, check the amount, and only then decide whether to sign or send. A stable checklist makes subtle differences easier to notice.
The practical goal here is to understand“签名”并非单一行为，每次请求都要独立判断. When information cannot be verified, pause and return to on-chain records or official pages instead of relying on someone else's assurance.
Verification order
Verify the source and network first, then the address, amount, requested permission and fees; finally review the transaction hash or on-chain state.
Contracts and Permission Risk
Blockchain actions are often difficult or impossible for a wallet provider to reverse on its own. When evaluating 域名, prefer verifiable information such as the network name, destination address, transaction hash, contract address, and block explorer records instead of relying only on screenshots, chat messages, or unfamiliar links.
If something looks wrong around 合约调用, avoid repeatedly submitting the same action. Record the network, address, and transaction hash first, then determine whether the request was broadcast, is waiting for confirmation, or failed because of fees or parameters. Repeated attempts can add cost and make troubleshooting harder.
For 消息签名, a repeatable review order is useful: verify the source, verify the network, verify the counterparty or contract, review the requested permission, check the amount, and only then decide whether to sign or send. A stable checklist makes subtle differences easier to notice.
Signature Requests: Messages & Transactions is easier to use safely when you separate what the wallet interface shows from what the blockchain actually records. In practice, you should consider 风险提示, 消息签名, and 交易签名 together. A wallet can prepare and broadcast a request, but the final state is determined by the selected network and the transaction that network accepts.
The practical goal here is to understand“签名”并非单一行为，每次请求都要独立判断. When information cannot be verified, pause and return to on-chain records or official pages instead of relying on someone else's assurance.
When something looks wrong
Do not keep clicking or resubmitting. Preserve information that can be safely verified, and never provide a seed phrase, private key, verification code, or remote-control access.
Managing Connections Afterwards
If something looks wrong around 合约调用, avoid repeatedly submitting the same action. Record the network, address, and transaction hash first, then determine whether the request was broadcast, is waiting for confirmation, or failed because of fees or parameters. Repeated attempts can add cost and make troubleshooting harder.
For 消息签名, a repeatable review order is useful: verify the source, verify the network, verify the counterparty or contract, review the requested permission, check the amount, and only then decide whether to sign or send. A stable checklist makes subtle differences easier to notice.
Signature Requests: Messages & Transactions is easier to use safely when you separate what the wallet interface shows from what the blockchain actually records. In practice, you should consider 风险提示, 消息签名, and 交易签名 together. A wallet can prepare and broadcast a request, but the final state is determined by the selected network and the transaction that network accepts.
Before taking action, confirm that 消息签名 matches what you intend to do, then review 交易签名 and 域名. If a page, DApp, or third-party service asks for a seed phrase, private key, recovery phrase, or verification code, stop. imtoken will not ask you to disclose those secrets, and they should never be sent to another person.
The practical goal here is to understand“签名”并非单一行为，每次请求都要独立判断. When information cannot be verified, pause and return to on-chain records or official pages instead of relying on someone else's assurance.
