> For the complete documentation index, see [llms.txt](https://docs.code4rena.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.code4rena.com/roles/scouts.md).

# Scouts

Code4rena Scouts specialize in scoping and pre-audit intel. They assess the following factors to help determine the optimal parameters for an audit:

* Library dependencies
* External calls
* Timelocks
* SLoC

In evaluating the scope of an audit, Code4rena Scouts provide valuable, high-level information to all parties:

* **For Wardens:** Ensuring that the audit repo is set up correctly ensures that those considering participating have a well-organized, consistently-formatted workspace.
* **For Projects:** Providing feedback to the project team on the scoping accuracy and repo preparedness helps accelerate the audit launch while maintaining consistency.

## How the Scouting process works

1. Scouts review the proposed code and repo before an audit has begun.
2. Feedback is provided to the Project and Code4rena teams on scoping accuracy and preparedness. Any concerns are flagged, and the Scout can supply technical guidance regarding any necessary adjustments.
3. Once the audit begins, the Scout monitors the public code repo to ensure all guidelines are adhered to.
4. As compensation, Scouts receive a flat fee of $500 USDC per competition.

## Scout selection process

Due to the highly sensitive nature of the role, Scouts are hand-picked by the Code4rena team.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.code4rena.com/roles/scouts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
