# Signal metrics

The `signal` metric is Code4rena's accuracy metric for wardens and teams: a means of identifying wardens and teams who have consistently submitted valid findings. For a warden or team, it is the ratio between the number of valid High- or Medium-risk findings versus all of the High and Mediums they've submitted.

`signal = findings / submissions`

A signal of `1` means that the user has consistently submitted valid Highs and Mediums, whereas a signal of 0 means the user has either submitted only invalid findings or has not yet met the participation threshold to calculate signal.

Contributors' signal will display as `null` until they have submitted at least 3 High or Medium severity submissions to a finalized C4 audit. (Signal is calculated when competition results are published.)

Notes:

* Only High/Medium severity submissions from finalized audits count toward `signal`. Audits that are still in progress (i.e. results have not been officially announced) do not count toward the thresholds for signal calculation.
* Submissions downgraded to Low severity do not count towards `signal`, to discourage wardens from inflating severity.

## How is `signal` used?

`signal` is a factor in determining eligibility for a variety of privileges within Code4rena competitions, including:

* [Eligibility for the `SR` role](/roles/sr-wardens.md) and its associated privileges
* [Unrestricted submissions](#submission-limits-based-on-signal)
* [PoC requirements waived for high-signal wardens](/competitions/submission-guidelines.md#required-proof-of-concept-poc-for-solidity-evm-audits)

This is not an exhaustive list, and is subject to change.

## Privileges based on signal

### Submission limits based on `signal`

To reduce spam while keeping C4 competitions open to all, `signal` determines the maximum number of submissions wardens/teams can make to each audit.

* The higher your signal , the more submissions you get.
  * All [submission types](https://docs.code4rena.com/competitions/submission-guidelines#submission-types) count towards your submission limit (e.g. High, Medium, QA).
* Low- or no-signal users' submissions are capped, to disincentivize "spray and pray" behavior and encourage newer wardens to focus on their highest-risk, highest-quality findings.
* Earn bonus (or uncapped) submissions by verifying your identity and submitting your tax information.
* Unrestricted submissions unlock at 0.4 (40%) signal + verified ID/tax info.

These limits are subject to change, based on the volume of low-quality/spam submissions we receive over time.

| User's signal   | Max # of submissions per audit | Certified + submitted tax info |
| --------------- | ------------------------------ | ------------------------------ |
| `null` or < 0.2 | 1                              | 2                              |
| 0.2-0.3999      | 2                              | 10                             |
| 0.4+            | 10                             | unrestricted                   |

* If (( signal = `null` (e.g. you are a newly-registered user, or have submitted < 3 High/Medium findings to finalized audits) OR signal < 0.2 )) and you have not verified your identity and submitted tax info, then you will be limited to 1 submissions per audit.
  * If you meet these criteria, and have both [verified ID](/roles/certification-id-verification.md) and [submitted tax info](/awarding/awarding-process.md#tax-information-for-code4rena-contributors-wardens-judges-etc), then you will unlock 1 bonus submission1 per audit (i.e. max 2 submissions in total)
* If your `signal` = 0.2-0.3999 and you have not verified your identity and submitted tax info, then you will be limited to 2 submissions per audit.
  * If you meet these criteria, and have both [verified ID](/roles/certification-id-verification.md) and [submitted tax info](/awarding/awarding-process.md#tax-information-for-code4rena-contributors-wardens-judges-etc), then you will unlock 8 bonus submissions per audit (i.e. max 10 submissions in total)
* If your `signal` ≥ 0.4, you will be limited to 10 submissions per audit.
  * If you meet these criteria, and have both [verified ID](/roles/certification-id-verification.md) and [submitted tax info](/awarding/awarding-process.md#tax-information-for-code4rena-contributors-wardens-judges-etc), then you will have unrestricted submissions.

**How do submission limits apply to teams?**

* Warden teams are subject to the same criteria as individual wardens.
* Submission limits apply to both teams and individual wardens.
* To unlock bonus submissions, *all* members of a team must verify their identity and submit tax info.

#### Bypassing `null` signal limits as an established researcher

Security researchers who are ranked in the top 50 on the [Sherlock](https://audits.sherlock.xyz/leaderboards), [Cantina](https://cantina.xyz/leaderboard), or [Immunefi](https://immunefi.com/leaderboard/) leaderboards and who have insufficient history at C4 to have an existing `signal` score (i.e. they have `null` signal) may request to bypass null signal submission limits.

To qualify, researchers must

1. hold a top-50 position on at least one of the above leaderboards at the time of the request;
2. submit a [C4 help desk request](https://code4rena.com/help) that includes a) a link to your leaderboard profile on one of the above-mentioned platforms, and b) your C4 username; and
3. post a note in [this discussion thread](https://github.com/code-423n4/code423n4.com/discussions) **from the Github account linked to your Sherlock/Cantina/Immunefi profile,** confirming your request.

If approved, you will receive the same submission limits as wardens with 0.4+ signal for your first 3 Code4rena audits. After that, your submission limit will revert to whatever your C4 signal score dictates at that time.

As outlined in the table above, unlimited submissions can be unlocked by completing identity verification and submitting tax info.

{% hint style="info" %}
Not in the top 50, or mainly compete on a platform that's not listed? We'll give consideration to other achievements (e.g. Top 150 on Cantina with a 100% reputation score), but will evaluate such applications on a case-by-case basis.&#x20;
{% endhint %}

### PJQA comments based on `signal`

For competitions starting on or after January 8, 2026, all wardens may comment during post-judging QA (PJQA) if they:

* Have [verified their identity (KYC)](/roles/certification-id-verification.md)
* Have [submitted tax info](/awarding/awarding-process.md#tax-information-for-code4rena-contributors-wardens-judges-etc)
* Submitted at least one finding to the relevant competition

| User's signal   | Max # of PJQA comments per audit | Certified + submitted tax info |
| --------------- | -------------------------------- | ------------------------------ |
| `null` or < 0.2 | 0                                | 1                              |
| 0.2-0.3999      | 0                                | 3                              |
| 0.4+            | 0                                | unrestricted                   |

Note: Post‑judging QA (PJQA) comments are the formal mechanism for raising disputes or clarifications about judge decisions. Do not contact judges directly outside of PJQA.

## High/Medium submissions downgraded to QA

Currently, all High- and Medium-risk submissions that are downgraded to Low-risk (QA) are excluded from `signal` calculations.

We expect this to change in future, and will update this documentation as the formula evolves.

## FAQ

**Q. How can I view my signal?**

A. You can view your `signal` score on [your account settings screen](https://code4rena.com/account).

**Q. How can I view my team's signal?**

A. You can view the score on the [teams page](https://code4rena.com/account/teams) in your account settings

**Q. Who else can see my signal?**

A. Authenticated users can see the `signal` score of wardens and teams alongside their submissions, while logged in to [Code4rena.com](https://code4rena.com).

**Q. How often is signal updated?**

A. It is updated daily.

**Q. What happens if my signal changes — and crosses the submission limit threshold — during an audit?**

A. If a warden’s signal increases to cross a submission limit threshold during an audit, their submission limit will increase accordingly. Conversely, if their signal decreases to drop below a submission limit threshold during an audit, their submission limit will decrease accordingly. Any submissions made prior to the change will be preserved.

**Q. How much historical data does the `signal` calculation use?**

A. The score is calculated with data from March 2023 to present.


---

# Agent Instructions: 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:

```
GET https://docs.code4rena.com/roles/signal.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.