*Paid Advertisement. Not financial advice. RugDoc is not responsible for the projects showcased here. DYOR and ape safu.

How to check if tokens and liquidity is burned (Polygon)

In order to check if at least a part of the liquidity is burned before the farming starts, you can check the liquidity token contract for the current holders. If liquidity is “burned” this means it cannot be removed at any time. Having liquidity locked or burned is a good sign for the investors, as it cannot be removed short term, which reduces the soft-rug risk a lot. If liquidity is removed this would lead to the problem that the investors cannot trade their tokens anymore.

Find the token contract #

If you have the token contract already available you can continue here. You can find the token contract via the masterchef. We will use this Masterchef as an example.

Navigate to “Contract” and select “Read Contract”.

Then scroll down to the token name to find the token address.

Use the Token Tracker to find current holders #

Click on the “Token Tracker” token link within the token contract “More Info” block.

On the new page click on “Holders” to see the current list of holders of the token. If the “dEaD” address is one of the holders this means that some tokens are burned and cannot be recovered.

But now we have to distinguish between token burn and liquidity burn as burning tokens is not necessarily helpful for the investor. This is because burning tokens can increase the share of the other holders, which could lead to more price impact when they sell their tokens. Therefore it’s important to find out if liquidity is burned and not only the tokens.

Find the liquidity token contract #

In order to do the same research for the liquidity we need to find the liquidity pair token of the reward token.

In the Masterchef navigate to “Contract” and select “Read Contract” and query the pool info starting with 0.

Then click on the lpToken address to find out if this pool is the liquidity pair of the reward token.

If it shows “Uniswap” in the “Token Tracker” info you found a liquidity pool but we have to check the underlying tokens to be sure we have the right one. Therefore we read the contract information with “Read Contract” and scroll down to the “Token0” and “Token1” blocks.

By following the linked addresses we find out which tokens are in this liquidity pool. In our example it’s USDC and Plague Token (Native Token). So we have found the correct pool.

We can now have look on the holders list of the liquidity pool token to check if this liquidty is burned. As you can see 34% of the liqudity is burned, qhich is a good sign. As this liquidity cannot be removed at any time, it can reduce the risk of soft-rug significantly depending on the burned amount. In addition to that the largest holder is the masterchef itself. This may increase the risk of the dev dumping liquidity if they are they majority holders of the initial liquidity.

Conclusion #

You now know how to check if tokens or liquidity is burned or not. This is not the only way to reduce the risk for investors, but it’s a very transparent one. There also is the possibility of liquidity locking which we will explain in a separte article. You can also check out this video where we also explain the topic.

Updated on October 12, 2021
How do you feel about this article?
 

3 Comments

    • Hey, When the liquidity is burned, what happens is that the LP-tokens of a liquidity pool are sent to a burner address, which is basically a one way ticket for tokens. This ensures that the LP-tokens can’t be turned in for the actual tokens in the liquidity pool, which prevents a price dump.. In this article, we aren’t talking about your, or other (small) investor’s LP-tokens but the LP-tokens from whales, such as the developers.

Leave a Reply

*Paid Advertisement. Not financial advice. RugDoc is not responsible for the projects showcased here. DYOR and ape safu.

Our mission here at RugDoc is to screen for hard rug code that results in 100% theft of ALL underlying funds for ALL participants.

This is the ONE part of the due diligence process that most people cannot simply do on their own as it costs thousands of dollars to hire a senior solidity developer to look over a farm for safety.

A project coin with terrible code can go up in price, and a project with good code and a good team can also go down in price.

Do NOT use our ratings to refer to your likelihood in making money if you invest in the project. They are ONLY in reference to code safety.

Everything else beyond code safety is YOUR responsibility to go do research on. We just make sure the casino you’re betting in won’t rob you before you even get to place a bet.

Our reviews for projects are organized into a few colors.

🟢 Least Risk
These projects are the least likely to hard or soft rug. Usually reserved for cornerstone projects of an ecosystem where it makes no financial sense for them to rug in any manner as they make more money just being legit.

🔵 Low Risk
These projects are usually established projects in an ecosystem that have a track record of success or have KYC’d to us or other authoritative sources in the real world. As a result, it is extremely unlikely for them to soft rug or hard rug their projects. The projects can still fail and the token price can go down, but usually more as a result of natural market forces.

⚪️ Some Risk
This is the default rating for projects with unknown teams but have code that is unlikely to have hard rug risk. Since the team is unknown and doesn’t have a track record of success, it’s entirely possible that they may try to soft rug by dumping tokens, abandoning the project, etc. Even a last minute contract swap to a malicious contract is possible. The only thing that is unlikely is a complete hard rug as long as you are 100% sure you deposit into the contract we review.

🟠 Medium Risk
Similar to Some Risk, but the underlying code itself is custom enough or complex enough that it warrants an elevated risk rating that needs deeper research. Make sure you read every point presented to make sure you’re comfortable with that before entering. Still unlikely to hard rug, but more chances of custom code behaving incorrectly and causing other issues.

🔴 High Risk
Project contains code or practices that are HIGHLY LIKELY to lead to catastrophic losses as they are right now. Make sure you read the description carefully as we will always warn what these issues are. If you see the words Hard Rug anywhere in the review, STAY FAR AWAY!

⚫️ Not Eligible
We reserve the right to not review exceedingly complex projects that would require tens of thousands of dollars of senior security analyst man hours. Typically these are projects that deal with leverage, lending, options, derivatives, and anything that is overly complex and which requires tons of peer reviews and audits from top audit companies.

Search

🟢 For owners who have made impactful changes and would like an update to their farm review:

1️⃣ Use #update at @RugDocChat with your description and proof of changes and it will be forwarded to our scanners.

2️⃣ This does not guarantee a change in your review.

3️⃣ Owners who have difficulty solving the issues can consider our Consultation Package - please contact @BaymaxCrypto on Telegram to discuss.