> 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/competitions/restricted-competitions-and-c4-mitigation-reviews.md).

# Restricted competitions and C4 mitigation reviews

Why some competition details are kept private

Some C4 competitions are limited to specific participants. For the most part, these are mitigation reviews to review the fixes from a preceding C4 competitive audit.&#x20;

Participation in these competitions is determined by [RSVP in the Code4rena Discord](https://discord.com/channels/810916927919620096/958800160870240286). Each opportunity outlines how the opportunity will be assigned (e.g. "The 3 highest ranking wardens based on the audit results who RSVP by the end of the claim window get the opportunity," etc.).&#x20;

The code repo and competition details for restricted competitions are private to the participating wardens, judge, and sponsor team only.<br>


---

# 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/competitions/restricted-competitions-and-c4-mitigation-reviews.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.
