# Backtest

This **unique function** is designed to analyze the potential historical activity of the contract owner with a primary focus on liquidity pull metrics. This specialized tool aims to identify instances where the liquidity was pulled, providing users with essential insights into the potential risks associated with the current contract.

The backtest works in **several stages**. 👀 It is almost impossible to make a direct link between 2 contracts with only one indicator. This is why we **cross-reference the data** to target the contracts that are most likely to be from the same deployer :

* **Source of funds** is the origin of the first transfer to the deployer's wallet. For Binance, we make the link whatever the Bincance transfer wallet (Binance1 / Binance2, 3, 4...).
* **Website IP** corresponds to the IP of the server on which the website detected in the contract is hosted. Please note that the number of websites per IP depends on the web host you choose. But there can be several hundred websites on a single IP.
* For the **contract size** we use the number of characters in the BIN file sent by the deployer (unverified compiled file). We take a small margin if the deployer changes the contract a little. For information, comments do not impact the size of the Bin file.

**It is really not easy for a scammer to change the source of his funds, the IP of his server or to create new contracts. Most of the time they keep it simple by just changing the name of the contract and the website domain.**

We search the database with as much targeting information as possible. If the database returns nothing, we expand the search. 🔎 In the attached example, we are seeking contracts with:

<figure><img src="https://3106451934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FU9cKrfuNXh83VtEr6c93%2Fuploads%2FyVz3K20fciE3T5XkODKO%2Fimage.png?alt=media&#x26;token=c2850dec-5ed0-4a5d-a00c-733cd02cf530" alt=""><figcaption></figcaption></figure>

* a similar **contract size,** identical **source of funds,** an **identical website domain IP**.&#x20;

&#x20;As we found nothing we re-ran a search with only:

* identical source of funds and an identical IP.&#x20;

As you can see in the example, we also display whether **liquidity has been withdrawn** and after how long...

This information, which you will not find on any bot, will allow you to invest with the most security! 👌

***31/05/24 Update*** : We have launched a new feature that significantly improves the information provided by the backtest. We identify if the contracts were scams with a ⛔️ indicator.

<figure><img src="https://3106451934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FU9cKrfuNXh83VtEr6c93%2Fuploads%2F5CWgld2qsst9Ae8GxNYB%2Fimage.png?alt=media&#x26;token=89082337-8758-4638-a53c-634851113e2c" alt=""><figcaption></figcaption></figure>

This indicator makes it easier and faster to assess the legitimacy of the displayed contract. Another major innovation is that, to identify scam contracts, we use our database, but we have also developed a script that scans the history of our database daily using the remaining balance of our TokenSniffer API credit. We only scan contracts that are more than 24 hours old because TokenSniffer is excellent at identifying scams, but only a few hours after the contract is released. Thus, we obtain very reliable information to determine whether a contract was a scam or not.

➡️ Note that limited results of the backtest are also visible for free on our website! Check it out here: <https://vision-scanner.com/eth-backtest/?0x84eb89c6d555b6af9ba2bd799ce1003e37281578>

🧐 **How to use it ?**

The results displayed in the backtest **are only a suspicion** of a link between the contracts. The indices are converging towards these contracts.

If you wish to invest in a contract that has a backtest result, we recommend that you first try to find contracts that come from the same deployer. &#x20;

For example, you can open the sources of the contracts in Etherscan and try to find similarities such as:

* A similar header formatting&#x20;
* A similar compiler version
* A similar License Identifier
* A very similar contract name ("Abc Coin" and "Cba Coin" for example)
* identical contract source code with just minor differences

For example this 3 headers looks very similar. If one is a scam, the next one may be too...  :&#x20;

<figure><img src="https://3106451934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FU9cKrfuNXh83VtEr6c93%2Fuploads%2FeDjxEce2z5dg67VC0tOh%2Fimage.png?alt=media&#x26;token=83d11b1e-d6ff-45f0-aaf4-7cb884693c93" alt=""><figcaption><p>Same compiler, same License, same link formatting...</p></figcaption></figure>

You can go further by using text tools with comparison functions. Scammers often change only a few variables between each scam...

<figure><img src="https://3106451934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FU9cKrfuNXh83VtEr6c93%2Fuploads%2FLafZ07yOK85p5Q2PXZXp%2Fimage.png?alt=media&#x26;token=28e7a659-7e0a-4eeb-a5f4-3c0fb9a752c6" alt=""><figcaption></figcaption></figure>

You can also check the website if it still exists:

* are they similar in their presentation
* do they use the same builder (wordpress, sitepad...)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://vision-8.gitbook.io/docs/features/backtest.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.