# How to Report Bugs

For each bug, include:\
✅ **Bug Title:** Clear and descriptive.\
✅ **Description:** What happened, where, and when?\
✅ **Steps to Reproduce:** How to recreate the bug?\
✅ **Expected vs. Actual Behavior:** What should happen vs. what actually happens?\
✅ **Screenshots or Video Proof:** Attach visuals if possible.

### **Testing Priorities**

🔴 **Critical** – Security risks, transaction failures, data loss.\
🟠 **High** – Wallet connection issues, broken core features.\
🟡 **Medium** – UI inconsistencies, slow loading times.\
🟢 **Low** – Minor visual glitches, typos.

📌 Submit bugs via [**this form**](https://forms.gle/q8PiXN8381x4qNLK8)

Thank you for contributing to the quality of **CandyBlinks**! 🚀


---

# Agent Instructions: 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:

```
GET https://docs.candyblinks.fun/candyblinks/early-access/how-to-report-bugs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.