How to read the SAFU V1 Scanner?
Tags: Cybersecurity, Crypto Tokens, Scanner App, Documentation, Crypto

In this article, we will deal with the different sections of the scanner point by point in an attempt to better understand its overall functioning.

I. Rug Pull Safety

The Rug Pull Safety section is used to determine the likelihood of a token getting rugged, i.e. owners withdrawing liquidity, or dumping a massive amount of tokens.

A. Liquidity

The liquidity analysis is the analysis of the holders of the LP tokens: the scanner recognizes two cases for liquidity:

- locked : less than 10% of the LP tokens are held by non-contract addresses

- unlocked : more than 10% of the LP tokens are held by non-contract addresses

Note that even if liquidity is locked, it’s still possible to scam : minting, disabling trading, rug pull.. however, if the liquidity is unlocked at more than 30%, worry seriously!

B. Holders

The analysis of holders is essentially to determine if some hold too many tokens, or if they have had transactions with the dev wallet (which may mean that the dev hides his tokens in many wallets). The scanner identifies two distinct cases:

- clean: less than 10% of the supply (normalised with liquidity supply) is considered suspicious

- suspicious: more than 10% of the supply (normalised with liquidity supply) is considered suspicious

C. Top 5 holders

Analysis of the top 5 holders returns the proportion of tokens held by the largest whale — if this number is too large, beware!

D. Mint

Our scanner is calibrated to detect minting functions — these functions, which allow owners to generate an infinite number of tokens, are very dangerous if put in the wrong hands. However, perfectly safe projects can have a minting function. In summary, only enter projects with minting functions if you trust the dev team.

II. Delayed Honeypot Safety

The Delayed Honepot section is extremely important as it determines the possibility of a token becoming a honeypot.

A. Ownership

The ownership of a token is determined by the owner property of a smart-contract: the token recognizes 3 different cases:

- renounced : the owner is the dead address

- owned : the owner is any other address than the dead address

- none : there is no owner property in the smart-contract

Warning : in all cases, there can be hidden functions that another ‘owner’ could activate (mint, disable trading)

B. Blacklist

The scanner can detect blacklist functions: these allow owners to exclude an address from transactions (this address will not be able to sell or receive tokens). They can be very dangerous: be careful.

C. Modify Max TX

If the owners can change the value of the max transaction of a token, it can turn into a delayed honeypot (if the max transaction is 0, it is impossible to sell tokens)

D. Modify Fees

The same logic applies here: if it is possible to set fees at 100%, then it is impossible to sell tokens.

E. Disable Trading

Functions to disable token trading are often used by scammers: this is the easiest way to build a delayed honeypot. They just have to click a button, and you can’t sell your tokens anymore: only invest if you have full confidence in the dev team.

III. Informations

The last section gathers several useful information about the tokens such as the buying and selling fees and the gas used for buying and selling.

A. Honeypot-Like

Honeypot-Like is considered true if the smart-contract is in our honeypot database; however, the fact that it is not does not guarantee that the token is not a honeypot

B. Honeypot

Honeypot is considered true if our token sale simulation fails: this means that it is strictly impossible to sell the tokens you buy (at least at the time of scanning)

Summary

You should always be careful of tokens not listed : there isn’t enough data to correctly estimate the risk of scam !