> 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/awarding/judging-criteria.md).

# Judging criteria

This page has moved: see [Judging criteria](https://docs.code4rena.com/competitions/judging-criteria.md).

### Submission review process

See [Judging criteria](https://docs.code4rena.com/competitions/judging-criteria.md#submission-review-process)

### Duplicate submissions

See [Judging criteria](https://docs.code4rena.com/competitions/judging-criteria.md#duplicate-submissions)

### Similar exploits under a single issue

See [Judging criteria](https://docs.code4rena.com/competitions/judging-criteria.md#similar-exploits-under-a-single-issue)

### Penalty / award standardization: duplicate submission PoC thoroughness

See [Judging criteria](https://docs.code4rena.com/competitions/judging-criteria.md#standards-for-full-partial-credit-duplicates)

### Findings published in prior audit reports

See [Judging criteria](https://docs.code4rena.com/competitions/judging-criteria.md#findings-published-in-prior-audit-reports)

### Scope

See [Judging criteria](https://docs.code4rena.com/competitions/judging-criteria.md#scope)

### Scoring

See [Judging criteria](https://docs.code4rena.com/competitions/judging-criteria.md#quality)

### QA reports (Low risk and Governance/Centralization risk) <a href="#qa-reports-low-risk-and-governance-centralization-risk" id="qa-reports-low-risk-and-governance-centralization-risk"></a>

See [Judging criteria](https://docs.code4rena.com/competitions/judging-criteria.md#qa-reports-low-risk-and-governance-centralization-risk)

### Acceptance of submissions based on automated findings

See [Submission guidelines](https://docs.code4rena.com/competitions/submission-guidelines.md#automated-findings-considered-known-issues)


---

# 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/awarding/judging-criteria.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.
