> For the complete documentation index, see [llms.txt](https://help.tokenpocket.pro/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tokenpocket.pro/en/security-knowledge/security-measure/about-approve.md).

# About Approve

**What is an Approve?**

Approve is to allow another account (It can be an ordinary personal account or a contract account), <mark style="color:red;">which can control your asset without your permission</mark>. Therefore, Approve is a very dangerous action.

{% embed url="<https://www.youtube.com/watch?v=iIvBlgOgjJA>" %}

**Why Approve?**

Taking the Ethereum network as an example, ETH is the native asset of the network. When ETH is transferred to a target smart contract, the ETH is sent together with the transaction and received directly by the target contract.

However, when transferring a non-native ERC-20 token to a target contract, the process only updates the ledger within the ERC-20 token contract itself. The target contract does not automatically receive a notification of the token transfer. Therefore, the Approve operation is used to authorize a specific account or smart contract to transfer the user’s ERC-20 tokens on their behalf in the future.

At the same time, the Approve mechanism widely exists across Ethereum and other major EVM-compatible blockchain networks, including Ethereum, BNB Smart Chain, Polygon, Arbitrum, Base, and Robinhood-related EVM-compatible networks. These networks generally use address formats that are consistent with or compatible with Ethereum, which is why token authorization is commonly seen when interacting with DApps, swaps, staking, and other smart contract functions.

**What scenarios will use Approve in the process of using the wallet?**

The ordinary transfers won’t ask the Approve in the process of using the wallet; Only when it involves interacting with the contract (DApp, DeFi, etc.), the Approve operation will be performed when the contract needs to be approved. Therefore, when you are in the process of using the wallet, and the following interface appears, you are asked about the Approve. <mark style="color:red;">You must be more careful and confirm whether the current link you are visiting is safe and credible. If not, stop operating!!</mark>

![](https://2516903027-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMJyYRLFVRsMrfcXuRV%2Fuploads%2FW8aee3IpkG4kompl6RHq%2F2.png?alt=media\&token=87200afb-df70-47c0-9a47-34b93da2b084)

**How dangerous Approve is?**

<mark style="color:red;">Approve is to allow the third-party to control your assets without your permission, which means that they can transfer all your assets away without your permission.</mark> So it is very dangerous to approve. Please be more careful when you encounter the Approve! Be sure to determine whether the code is verified and open-sourced, whether it has a code audit, whether the team is trustworthy, etc.!

**How to manage/cancel the Approve?**

Follow this tutorial:[**https://help.tokenpocket.pro/en/security-knowledge/security-measure/cancel-malicious-authorization**](https://help.tokenpocket.pro/en/security-knowledge/security-measure/cancel-malicious-authorization)

**How to prevent Approve scams?**

1. Don't play DApps from <mark style="color:red;">unknown sources</mark>, don’t play DApps have <mark style="color:red;">no open-sourced</mark>, don’t play DApps have <mark style="color:red;">no audit reports</mark> and <mark style="color:red;">not from trustable teams</mark>.
2. Regularly use DeBank, Cointool and other tools to cancel the approval;
3. Create a new wallet. After the approval and other operations are completed, transfer the Token to the new wallet address, which is relatively safe because there is no approval history (Attention: the cancel the approve doesn’t mean absolutely safe, there is no tools on the market that can guarantee a complete cleanup.)
