> 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.md). # Advancement and roles Code4rena audits let people of a wide range of skill levels get rewarded while showcasing their talent in order to make the DeFi ecosystem more secure. ## Signal metrics [The `signal` metric ](/roles/signal.md)is Code4rena's accuracy metric for wardens and teams: a means of identifying wardens and teams who have consistently submitted valid findings. `signal` is a factor (along with [certification](/roles/certification-id-verification.md)) in determining submission limits and commenting privileges during Post-Judging QA (PJQA). ## Wardens Wardens protect the DeFi ecosystem from threats by auditing code. Anyone can register to participate in an audit. Learn more about registering as a warden and joining an audit [here](/getting-started.md). ## SR Wardens and certified contributors Wardens who meet certain performance criteria within C4 earn the Certified Security Researcher (SR) role, which provides access to: * Unrestricted number of comments during Post-judging QA * Unrestricted number of submissions per audit [More details here](/roles/sr-wardens.md). ## Judges and Scouts These prestigious roles are assigned to the most skilled and fair-minded members of Code4rena's community: * [Judges](/roles/judges.md) * [Scouts](/roles/scouts.md) --- # 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.md?ask=&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.