> For the complete documentation index, see [llms.txt](https://dopameme.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dopameme.gitbook.io/docs/signals/market-cap-policy.md). # Market-Cap and Quality Filters Dopameme filters low market-cap noise from the confluence board. Very low market-cap tokens are often filled with traps, mislabels, thin liquidity, and noisy wallet behavior. The board should surface solid opportunities, not encourage users to gamble on every early print. ## Current Policy * Below roughly $50K market cap: suppressed * Around $50K to $100K: only strong wallet-quality exceptions * Above roughly $100K: eligible for the main board if wallet quality and attention are sufficient * Above roughly $250K: eligible for Prime when quality is strong These thresholds are policy, not guarantees. They can evolve as Dopameme learns. ## Why The Filter Exists Early tokens can move violently, but many are not useful opportunities for a serious intelligence product. Below a certain size, the data becomes less reliable. Liquidity can be thin, holder concentration can be extreme, wallet labels can be misleading, and price action can be easier to manipulate. Showing that activity as normal confluence would make the product noisier and less trustworthy. Dopameme can still record evidence internally. Suppression does not mean the protocol saw nothing. It means the token does not deserve user-facing placement yet. ## Common Suppression Reasons **Market cap floor** means the token is too small for the main confluence board. **Pre-bond** means the token has not shown enough reliable post-bond market structure. **Flipper dominated** means the wallet mix is not trustworthy enough. **Below threshold** means the token did not have enough useful wallet evidence. Suppression is not punishment. It is filtering. ## How The Policy Can Learn Market-cap policy should be evidence-driven. If suppressed tokens repeatedly become strong later opportunities, the protocol should review whether the floor is too strict for certain conditions. If low-cap exceptions repeatedly fail, the protocol should become more conservative. If certain wallet clusters are strong enough to justify earlier attention, that should be learned through packet outcomes, not guessed. The policy is designed to protect users from noise while still leaving room for the protocol to improve. --- # 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://dopameme.gitbook.io/docs/signals/market-cap-policy.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.