> 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/protocol/packets.md). # Packets and Evidence Packets are Dopameme's memory layer and the backbone of the protocol. When a token is scanned, Dopameme creates a structured record of the evidence available at that moment. The packet captures what the system saw, what the operator read said, which levels mattered, what holder or wallet context was available, and what should be checked the next time the token appears. This matters because meme markets move quickly and raw snapshots age fast. A packet gives Dopameme a point of comparison. The next scan is not just a new output; it is a chance to ask whether the previous read improved, weakened, confirmed, or failed. ## What Packets Preserve * Token identity, market cap, liquidity, volume, and available price context * Operator read, thesis, uncertainty, and consequence map * Technical levels that matter for continuation, rejection, or breakdown * Holder concentration and tracked-wallet context where available * Suppression reasons when a token is too noisy or too early to show broadly * Comparison points for future scans * Audit history and review outcomes when the packet has been challenged Packets are not just UI content. They are protocol memory. ## Why Packets Matter Without packets, every scan is isolated. With packets, Dopameme can ask better questions: did the level hold, did the holder picture improve, did tracked-wallet attention continue, did the operator read miss something, and what should be remembered next time? That is the difference between a terminal that refreshes data and a protocol that learns from market evidence. ## What A Good Packet Should Do A good packet should make the next read better. It should tell the system what was believed, why it was believed, what evidence supported it, and what would prove the read wrong. It should preserve enough context that a later scan can compare against the original state instead of generating a disconnected summary. For users, the value is clarity. The token page should not feel like random backend data. It should show the latest useful packet read in a way that explains: 1. What matters right now. 2. What changed since the earlier read. 3. Which levels define the next decision points. 4. What the consequence map says if price accepts, rejects, or breaks down. 5. Where holder or wallet data strengthens or weakens the read. --- # 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/protocol/packets.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.