> For the complete documentation index, see [llms.txt](https://docs.trench.express/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trench.express/trench-express/overview/token-security.md). # Token Security At Trench Express, we prioritize the safety and security of the tokens we incubate, implementing robust measures to protect both creators and buyers. Our unique features set us apart in the DeFi space, ensuring a secure environment for all participants. Here's how we achieve this. ### Key Security Features * **Standard, immutable ERC-20 deployments**\ Every token is deployed from a standard, unmodified ERC-20 contract. The **entire supply is minted once at creation** and there is **no mint function** afterwards — supply is fixed forever. This eliminates common exploits such as infinite minting or hidden supply inflation. * **No deployer control after launch**\ Tokens have no owner in the traditional sense. Before a token graduates, the platform can only apply the launch-safety controls that keep trading confined to the bonding curve. The moment a token graduates ("launches"), those controls are **permanently and irreversibly disabled** — the token becomes a fully-free, immutable ERC-20 with no pause, no blacklist, and no admin powers. * **Creators have no economic power over the token**\ A token's creator can only update cosmetic metadata (description, image, social links). They cannot mint, pause, freeze, or otherwise interfere with holders' tokens. * **Fair launch model**\ Every coin on Trench Express follows a fair launch model with no presale. The full supply is minted "in-house" onto the bonding curve, ensuring equitable access for all participants. * **Permanently locked graduation liquidity**\ When a token graduates, its Uniswap v3 liquidity position is escrowed in a no-egress locker. The liquidity principal can never be pulled — protecting buyers from a launch-liquidity rug. Through these comprehensive security measures, Trench Express aims to create a safe and trustworthy environment for token creators and buyers alike. We are committed to fostering innovation while prioritizing the protection of our community's interests. --- # 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://docs.trench.express/trench-express/overview/token-security.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.