The goal of the contest is to use manual testing to find significant bugs in products in the TON ecosystem.
By significant bugs we mean UX inconsistencies, logical contradictions, and functional shortcomings. For example, if the application freezes, the action did not take place, incorrect information is displayed, the UI layout is so broken that it is impossible to use some function, etc. In other words, bugs that do not allow using some functionality of the application, or incorrect operation of the application (e.g. want to send 1 TON, but 5 TON was sent), or incorrect display of information (e.g. 1 TON sent, 0.99 TON is shown or you have NFT but it doesn't show up).
If you find a security bug (one that may affect not only you, but also other users of the service) — please, do not publish it on the contest, but submit it privately through the bug bounty program. The reward for such bugs will be according to the rules of the bug bounty.
First, go through the @toncontests_bot to share with us your GitHub account and TON wallet address so we may reward you in case you win.
Then choose any products reflected on the website and test it.
All bug reports will be collected in the project repositories. The repositories are also provided in the list of projects.
To make a bug report, go to the repository of the TON ecosystem project, follow the template of the issue, and provide a detailed explanation of the bug. It is mandatory to support the issue with a screencast or screenshots.
Please, follow the template for the issue in each repository. It will also be taken into account during the approval of the pull request.
* These participants will get a double reward because they find very critical bugs. ** TON Scan decided to reward the author of the bug on their own because there are no critical bugs were found during the contest.