Skip to main content
File a report from your dedicated mining account after linking a hotkey. A submission is evidence for review, not a verdict or a promise of payment. If you cannot join Bounty, you can still file an ordinary bug report.

​
Add a bug report to Bounty

1

Describe a reproducible finding

Open the account menu, then Settings > General > Report a bug. Give it a specific title, explain the expected and actual behaviour, and include the steps needed to reproduce it. Remove passwords, private keys and unrelated personal information from text and screenshots.
2

Submit the report

Send the report and keep the ticket reference on the receipt. Follow-up questions and the team’s response arrive by email; reply in that thread with any missing evidence.
3

Add the eligible report

On the receipt, choose Add to the Challenge Bounty if it appears. The programme must be active and your account must have a linked hotkey. Wait for confirmation that the report was added.
The button is conditional: filing a bug report does not automatically enter it into Bounty. If the programme is paused, participation is unavailable or adding it fails, the original bug report stays filed. A report can be added only once; retrying does not create a second Bounty finding. If you have several linked hotkeys, this route uses the first linked hotkey; the receipt does not offer a hotkey picker. Do not assume the key from a different Chat conversation will receive the credit.

​
Reporting from an existing miner conversation

An already-enabled Bounty miner conversation can offer the bounty_report Chat tool. Describe the finding in that conversation and ask for it to be filed. The resulting report uses that conversation’s active linked hotkey.
The /link card only links a hotkey. It does not enable a miner conversation, and its success message does not provide a conversation-activation control. Do not expect the report tool to appear in an ordinary Chat thread after linking. Use the bug-report route when eligible; /miner is not an activation command.

​
Follow the review

Pending reports are not listed on the public leaderboard or report log. An empty public log does not mean your submission was lost. Keep your bug-report receipt and distinguish a submission acknowledgement from an adjudicated verdict. Once staff records a verdict, check the Transparency API. A valid verdict needs severity before it can contribute to scoring. Eligibility and the final allocation depend on the scoring rules, not just on how many reports you submitted. There is no guaranteed review deadline or payment date.

​
What stays private

The original report body, Chat transcripts, account identity and email address are not part of the public transparency log. Public rows contain the hotkey, report identifier, verdict, severity when applicable, problem statement, justification and timestamps. Duplicates identify a related report. A summary is optional and requires staff approval before publication. Do not publish raw findings in a public issue merely because the verdict has become public. A public verdict does not authorize disclosure of credentials, private conversations or unpatched reproduction details.