1️⃣ In-Scope Contracts:
- Add all the contracts that are part of the competition into the In-Scope table or frame.
- This ensures auditors know which contracts are eligible for review.
2️⃣ Select Code Language:
- Choose one or more programming languages that apply to your project. This helps auditors understand the technologies they’ll be working with.
3️⃣ Main Repository and Commit Hash:
- Add the main repository link for the competition.
- Include the relevant commit hash. You can modify this hash before the competition starts if necessary.
- The Hats bot will fork this repository and its commit hash 10 minutes before the competition begins. This is where all issues will be submitted, so it’s crucial to ensure that the repository is up-to-date before the competition starts.
4️⃣ Project Documentation Link:
- Provide a link to the project’s documentation. This will help auditors quickly access any necessary reference material to understand the project better.
5️⃣ Out-of-Scope Section:
- List all out-of-scope contracts in this section. Clearly indicate any known issues that will not be eligible for rewards.
- Include previous audit reports for transparency, ensuring auditors are aware of past findings that are not eligible for payouts.
6️⃣ Steps to Run the Project:
- Optionally, you can provide detailed steps on how to run the project. This will help auditors set up the project faster and streamline their participation in the competition.
Make sure to save all changes once the scope details are added to ensure smooth auditor access and competition setup.