🚀 Bounty Guidelines🚀

[andylamgot]

When participating in a bounty program and reporting bugs, it's important to follow certain guidelines to ensure effective communication and maximize the chances of your bug being understood and addressed. Here are some common guidelines for bug reporting in bounty programs:

• Provide a Clear and Detailed Description:

Clearly describe the bug, including the steps to reproduce it. Be concise yet thorough in your explanation.
Include any relevant information, such as the environment (operating system, browser, version), device, or specific configurations.

• Include Supporting Evidence:

Provide screenshots, videos, or code snippets that illustrate the bug. This visual evidence can help the developers understand the issue more easily.
Include error messages or console logs if applicable.

• Specify Impact and Severity:

Indicate the impact or consequences of the bug, such as security risks, data loss, or functional impairments.
Assign a severity level (e.g., low, medium, high, critical) based on the bug's impact and potential risks.

• Isolate the Bug:

Attempt to reproduce the bug in a controlled environment to ensure it is not caused by external factors.
Identify any specific conditions or scenarios that consistently trigger the bug.

• Provide Clear Steps to Reproduce:

Break down the steps to reproduce the bug into clear, concise instructions.
Include any specific inputs, configurations, or user interactions required to trigger the bug.

• Avoid Assumptions:

Stick to facts and avoid making assumptions about the bug or its cause.
If you have suspicions or hypotheses, clearly state them as such and provide supporting evidence if possible.

• Be Respectful and Professional:

Maintain a respectful and professional tone in your bug report. Avoid using offensive or inflammatory language.
Focus on the issue at hand and provide constructive feedback.

• Avoid Duplications:

Before reporting a bug, search for existing reports to ensure it hasn't already been reported.
If you find an existing report, you can add additional information or confirm the bug's presence to help the developers.

• Follow Submission Guidelines:

Adhere to the specific bug reporting guidelines provided by the bounty program. This ensures that your submission meets the program's requirements and is processed correctly.

• Be Responsive:

If the developers or program administrators request additional information or clarifications, respond promptly to assist in the debugging process.