> For the complete documentation index, see [llms.txt](https://gitbook.simplifyerc.com/simplify-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.simplifyerc.com/simplify-whitepaper/important-informations/disclaimer.md). # Disclaimer ## 1) This is an experiment This token represents an experimental token standard (ERC-314) and may contain bugs or vulnerabilities. Use it at your own risk. Together, we aim to build and enhance the ERC-314 ecosystem. ## 2) We will improve the simplicity We know everything can look a bit sketchy but that's the thing with a first mover. ERC-314 is going to be a widely used tech of the future. To make it mainstream, we are or will be in contact with the teams of all your most used tools (telegram snipers/scanners/web bots and charting websites). We will have them implement our new technology which will make it more convenient and simple for everyone to use and become the staple token standard on Ethereum DeFi and meme ecosystem. ## 3) Anti MEV With Simplify and ERC-314, you can trade safely. There will be no MEV bots impacting the trades utilizing ERC-314, since Anti-MEV is built directly into our contract. Nobody will be able to buy and sell in the same block, hence MEVs won't be able to do their job. Even if you wanted to buy and sell directly as a normal user, you would have to wait for the next block after your purchase (approximately 12 seconds). ## 4) Additional things to know At first, all Telegram scanner bots will tell you that we're not live or that our token isn't sellable because they don't support our new erc standard, but don't be frightened by this, we are or will be in touch with all team of these to integrate our new technology into their bot. The same applies to all web scanners. The classic way of buying with telegram sniper bots won't work aswell at the beggining. [Please read Additional things here too](/simplify-whitepaper/how-to/buy-sell-erc-314-token.md#additional-things). ## 5) Liquidity Lock Liquidity, once it is added, is locked directly into the contract. When the developer of an ERC-314 token calls the add liquidity function, he has to add the block number where the liquidity will be unlocked, of course, he can also extend it. If you would want to check how long the developer locked the liquidity for, you'd need to check the block that is put in the transactions when the add liquidity function is called or check the value of blockToUnlockLiquidity\_ variable. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://gitbook.simplifyerc.com/simplify-whitepaper/important-informations/disclaimer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.