Content policy
What is not allowed in a token's name, symbol, description or media — and what we do about it.
Last updated: August 26, 2026
1. Scope
This policy covers everything you attach to a token through this interface: name, symbol, description, image, video, links and profile text.
It governs what we display. It cannot govern the chain: a contract we hide from Explore is still deployed, still tradable and still visible in any block explorer.
2. Not allowed
Sexual content involving minors, in any form — real, drawn or generated. This gets reported, not just removed.
Content that incites violence, or that attacks a group on the basis of race, ethnicity, national origin, religion, disability, sex, gender identity or sexual orientation.
Impersonation: presenting a token as the official token of a person, company, project or institution when it is not, including by using their name, logo, likeness or handles.
Content that infringes someone's copyright or trademark — see the Copyright and trademark policy for how to report it.
Doxxing: publishing a private individual's home address, phone number, documents or other private data.
Explicit sexual content, and gratuitous gore.
Claims that a token is endorsed by, partnered with or audited by someone when it is not, and any other statement designed to make a launch look official.
Content promoting terrorism or sanctions evasion.
3. Allowed, even where it stings
Memetokens are a satirical category and we are not the taste police. Parody, political jokes, references to public figures as public figures, and tokens that mock us are fine.
The line is deception and harm, not offence: a joke nobody could mistake for an official project is a joke; the same joke dressed as an official launch is impersonation.
4. Reporting and enforcement
Report anything on this list to contact@zeroliquidity.xyz with the token's contract address, its network, and what is wrong. Include a link if you have one.
We review manually, when we can, with no service-level promise. If we agree, we hide the token, the profile or the media from our interfaces and unpin the affected files from our IPFS account.
There is no pre-publication review. Nothing is checked before it goes live, and the absence of enforcement on a given token means nobody has looked at it yet — not that it passed.
We may respond to repeat abuse by refusing to display any future launch from the wallets involved. We cannot stop anyone from deploying contracts, only from being shown here.

