> For the complete documentation index, see [llms.txt](https://docs.tachyo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tachyo.ai/platform/feedback.md). # Feedback Feedback is a real part of the product, not a contact form. A large share of what exists in Tachyo today started as a note from someone who trades with it. The section is always available in the sidebar, for every signed-in user, whatever else is going on with your account. That is deliberate: the way to report that something is broken must never itself be gated. ## Submitting * Pick a **category**: bug, idea, or whichever fits. * Describe it. Specific beats polite: what you did, what you expected, what happened. * **Attach an image** by dropping it in. For a visual bug, a screenshot is worth more than three paragraphs. * You can submit **anonymously** if you prefer. ## After you submit **Your submissions** shows everything you have sent and its current status, including **Accepted**, which means it has been taken up as work. You can **withdraw** a submission you no longer stand behind. Accepted submissions earn **points**, and there is a leaderboard. Points appear once a submission is accepted, not when it is sent. ## What makes a report actually useful * **One issue per report.** Three bugs in one message become one hard-to-triage note. * **Say which screen and which token or wallet.** "Holders looked wrong" is hard; "Holders on this contract shows a snapshot from three days ago while the chart moved 4x" is fixable. * **Include the time.** Data problems are often freshness problems, and knowing when you looked narrows it fast. * **Ideas are welcome as ideas.** You do not need to propose an implementation. Say what you were trying to do and what got in the way. --- # 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.tachyo.ai/platform/feedback.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.