imtoken will never ask for your seed phrase, private key or verification code. Always review the address, network and request details before transferring, signing or approving.
Home / Token Approvals

Token Approvals

Understand approval targets, allowance amounts, persistence, and revocation.

On this pageWhat approvals areSpenders and contractsAllowance scopeRisks of persistent approvalsReviewing and revoking

What approvals are

Connecting a DApp only establishes an interaction channel. It does not mean later signatures, approvals, or transactions should be trusted automatically. Review the domain, contract, permission scope, asset amount, and intended on-chain effect every time a new request appears. An approval usually gives a contract permission to spend within a defined scope. It may not move assets immediately, but broad or persistent permissions can increase exposure. Review the spender, allowance, network, and whether the permission is still needed. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

A practical check

Connecting a DApp only establishes an interaction channel. It does not mean later signatures, approvals, or transactions should be trusted automatically. Review the domain, contract, permission scope, asset amount, and intended on-chain effect every time a new request appears. An approval usually gives a contract permission to spend within a defined scope. It may not move assets immediately, but broad or persistent permissions can increase exposure. Review the spender, allowance, network, and whether the permission is still needed. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

Before proceeding, confirm the network, the address or contract, the amount or permission scope, and the expected result. Keep sensitive recovery information offline and never send a seed phrase, private key, or verification code to another person.

Spenders and contracts

Connecting a DApp only establishes an interaction channel. It does not mean later signatures, approvals, or transactions should be trusted automatically. Review the domain, contract, permission scope, asset amount, and intended on-chain effect every time a new request appears. For spenders and contracts, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

A practical check

Connecting a DApp only establishes an interaction channel. It does not mean later signatures, approvals, or transactions should be trusted automatically. Review the domain, contract, permission scope, asset amount, and intended on-chain effect every time a new request appears. For spenders and contracts, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

Before proceeding, confirm the network, the address or contract, the amount or permission scope, and the expected result. Keep sensitive recovery information offline and never send a seed phrase, private key, or verification code to another person.

Allowance scope

Connecting a DApp only establishes an interaction channel. It does not mean later signatures, approvals, or transactions should be trusted automatically. Review the domain, contract, permission scope, asset amount, and intended on-chain effect every time a new request appears. For allowance scope, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

A practical check

Connecting a DApp only establishes an interaction channel. It does not mean later signatures, approvals, or transactions should be trusted automatically. Review the domain, contract, permission scope, asset amount, and intended on-chain effect every time a new request appears. For allowance scope, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

Before proceeding, confirm the network, the address or contract, the amount or permission scope, and the expected result. Keep sensitive recovery information offline and never send a seed phrase, private key, or verification code to another person.

Risks of persistent approvals

Connecting a DApp only establishes an interaction channel. It does not mean later signatures, approvals, or transactions should be trusted automatically. Review the domain, contract, permission scope, asset amount, and intended on-chain effect every time a new request appears. An approval usually gives a contract permission to spend within a defined scope. It may not move assets immediately, but broad or persistent permissions can increase exposure. Review the spender, allowance, network, and whether the permission is still needed. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

A practical check

Connecting a DApp only establishes an interaction channel. It does not mean later signatures, approvals, or transactions should be trusted automatically. Review the domain, contract, permission scope, asset amount, and intended on-chain effect every time a new request appears. An approval usually gives a contract permission to spend within a defined scope. It may not move assets immediately, but broad or persistent permissions can increase exposure. Review the spender, allowance, network, and whether the permission is still needed. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

Before proceeding, confirm the network, the address or contract, the amount or permission scope, and the expected result. Keep sensitive recovery information offline and never send a seed phrase, private key, or verification code to another person.

Reviewing and revoking

Connecting a DApp only establishes an interaction channel. It does not mean later signatures, approvals, or transactions should be trusted automatically. Review the domain, contract, permission scope, asset amount, and intended on-chain effect every time a new request appears. For reviewing and revoking, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

A practical check

Connecting a DApp only establishes an interaction channel. It does not mean later signatures, approvals, or transactions should be trusted automatically. Review the domain, contract, permission scope, asset amount, and intended on-chain effect every time a new request appears. For reviewing and revoking, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

Before proceeding, confirm the network, the address or contract, the amount or permission scope, and the expected result. Keep sensitive recovery information offline and never send a seed phrase, private key, or verification code to another person.
On-chain transactions generally cannot be unilaterally reversed by a wallet. Third-party DApps, smart contracts, bridges, and staking services may involve technical or operational risk. Digital-asset prices can also fluctuate. Review each action based on your own circumstances.

Keep learning with imtoken

Use the related guides to understand the network, permissions, and security checks before your next on-chain action.

Download imtoken