What we focus on
The core purpose is to help users understand relationships among wallets, networks, transactions, DApps, approvals and security so on-chain actions follow explainable steps. A useful way to understand this is to connect the concept with its operating conditions and the result recorded on-chain. imtoken focuses on making network, transaction and permission details understandable before users confirm an action. The wallet interface can prepare and display an action, but the selected network ultimately records transaction state, so a clickable button is not proof that every parameter is correct.
For practical use, define the intended outcome first and then review the items related to what we focus on one by one. Confirm the network and account context, check the address, asset or requesting contract, and only then review fees, permissions and confirmation details. Separating these checks makes it easier to identify whether an unexpected result comes from the network, transaction parameters, a contract or local display state.
Service and network conditions can change, so what we focus on should not be treated as producing a fixed outcome. The core purpose is to help users understand relationships among wallets, networks, transactions, DApps, approvals and security so on-chain actions follow explainable steps. For proof-of-stake, validators or third-party services, consider network status, waiting mechanics, technical risk and digital-asset price volatility separately. Participation should reflect personal circumstances rather than assumptions of fixed or guaranteed returns.
- Confirm the network, account or requester related to what we focus on
- Verify the address, network and amount before a transfer; consider a small test when appropriate
- Read signature and approval details instead of treating later requests as automatically trusted
- Keep the transaction hash or other information needed to verify on-chain status
What to do when the result differs from expectations
If the interface, network state or outcome does not match what you expected, avoid repeatedly submitting the same action. Confirm the active network and account, then use the transaction hash, a suitable block explorer or contract information to establish what has already happened. For what we focus on, distinguishing a local display issue from a transaction already recorded on-chain is an important first step.
How content is organized
Chinese content lives at root URLs and English content at matching /en/ URLs, with the same facts and topics expressed naturally for each language. A useful way to understand this is to connect the concept with its operating conditions and the result recorded on-chain. imtoken focuses on making network, transaction and permission details understandable before users confirm an action. The wallet interface can prepare and display an action, but the selected network ultimately records transaction state, so a clickable button is not proof that every parameter is correct.
For practical use, define the intended outcome first and then review the items related to how content is organized one by one. Confirm the network and account context, check the address, asset or requesting contract, and only then review fees, permissions and confirmation details. Separating these checks makes it easier to identify whether an unexpected result comes from the network, transaction parameters, a contract or local display state.
Service and network conditions can change, so how content is organized should not be treated as producing a fixed outcome. Chinese content lives at root URLs and English content at matching /en/ URLs, with the same facts and topics expressed naturally for each language. For proof-of-stake, validators or third-party services, consider network status, waiting mechanics, technical risk and digital-asset price volatility separately. Participation should reflect personal circumstances rather than assumptions of fixed or guaranteed returns.
- Confirm the network, account or requester related to how content is organized
- Verify the address, network and amount before a transfer; consider a small test when appropriate
- Read signature and approval details instead of treating later requests as automatically trusted
- Keep the transaction hash or other information needed to verify on-chain status
What to do when the result differs from expectations
If the interface, network state or outcome does not match what you expected, avoid repeatedly submitting the same action. Confirm the active network and account, then use the transaction hash, a suitable block explorer or contract information to establish what has already happened. For how content is organized, distinguishing a local display issue from a transaction already recorded on-chain is an important first step.
Security principles
Users retain custody of seed phrases and private keys and legitimate imtoken personnel will not request them; third-party DApps and contracts can involve risk, and on-chain transactions are generally not reversible by a wallet alone. A useful way to understand this is to connect the concept with its operating conditions and the result recorded on-chain. imtoken focuses on making network, transaction and permission details understandable before users confirm an action. The wallet interface can prepare and display an action, but the selected network ultimately records transaction state, so a clickable button is not proof that every parameter is correct.
For practical use, define the intended outcome first and then review the items related to security principles one by one. Confirm the network and account context, check the address, asset or requesting contract, and only then review fees, permissions and confirmation details. Separating these checks makes it easier to identify whether an unexpected result comes from the network, transaction parameters, a contract or local display state.
Service and network conditions can change, so security principles should not be treated as producing a fixed outcome. Users retain custody of seed phrases and private keys and legitimate imtoken personnel will not request them; third-party DApps and contracts can involve risk, and on-chain transactions are generally not reversible by a wallet alone. For proof-of-stake, validators or third-party services, consider network status, waiting mechanics, technical risk and digital-asset price volatility separately. Participation should reflect personal circumstances rather than assumptions of fixed or guaranteed returns.
- Confirm the network, account or requester related to security principles
- Verify the address, network and amount before a transfer; consider a small test when appropriate
- Read signature and approval details instead of treating later requests as automatically trusted
- Keep the transaction hash or other information needed to verify on-chain status
What to do when the result differs from expectations
If the interface, network state or outcome does not match what you expected, avoid repeatedly submitting the same action. Confirm the active network and account, then use the transaction hash, a suitable block explorer or contract information to establish what has already happened. For security principles, distinguishing a local display issue from a transaction already recorded on-chain is an important first step.
Boundaries around corporate claims
The site does not invent office addresses, phone numbers, email addresses, regulatory licenses, partners, user counts, download counts, transaction volume, rankings or media reviews. A useful way to understand this is to connect the concept with its operating conditions and the result recorded on-chain. imtoken focuses on making network, transaction and permission details understandable before users confirm an action. The wallet interface can prepare and display an action, but the selected network ultimately records transaction state, so a clickable button is not proof that every parameter is correct.
For practical use, define the intended outcome first and then review the items related to boundaries around corporate claims one by one. Confirm the network and account context, check the address, asset or requesting contract, and only then review fees, permissions and confirmation details. Separating these checks makes it easier to identify whether an unexpected result comes from the network, transaction parameters, a contract or local display state.
Service and network conditions can change, so boundaries around corporate claims should not be treated as producing a fixed outcome. The site does not invent office addresses, phone numbers, email addresses, regulatory licenses, partners, user counts, download counts, transaction volume, rankings or media reviews. For proof-of-stake, validators or third-party services, consider network status, waiting mechanics, technical risk and digital-asset price volatility separately. Participation should reflect personal circumstances rather than assumptions of fixed or guaranteed returns.
- Confirm the network, account or requester related to boundaries around corporate claims
- Verify the address, network and amount before a transfer; consider a small test when appropriate
- Read signature and approval details instead of treating later requests as automatically trusted
- Keep the transaction hash or other information needed to verify on-chain status
What to do when the result differs from expectations
If the interface, network state or outcome does not match what you expected, avoid repeatedly submitting the same action. Confirm the active network and account, then use the transaction hash, a suitable block explorer or contract information to establish what has already happened. For boundaries around corporate claims, distinguishing a local display issue from a transaction already recorded on-chain is an important first step.