> 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/submission-limits.md).

# Submission limits

To reduce spam while keeping C4 competitions open to all, submission numbers are capped on a per-competition basis, using a set of reputational criteria: 

*  `signal` determines the maximum number of submissions wardens/teams can make to each audit.
  * The higher your signal , the more submissions you get.
  * Low- or no-signal users' submissions are capped, to disincentivize spam and encourage newer wardens to focus on their highest-risk, highest-quality findings.
  * Unrestricted submissions unlock at 0.4 (40%) signal + verified identity/tax info.
* Earn bonus (or uncapped) submissions by verifying your identity and submitting your tax information.

For further details on how submission limits work, see [Privileges based on signal](/roles/signal.md#privileges-based-on-signal).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.code4rena.com/competitions/submission-limits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.