The audit dashboard
Once the submission deadline passes, wardens may view all submissions to most Code4rena audits in which they participated. (Exceptions — such as audits that include live/deployed code — are normally noted in the audit repo README file.) After submissions close, you can use the audit dashboard for an overview of judging progress.
Dashboard overview
After clicking "View dashboard," you'll see an abbreviated list of the highest-severity findings, and any recent comments:

Submission list
From the dashboard, clicking "View all submissions" will take you to the full submission list:

This is a table view that shows:
ID: the finding (
F-) and/or submission (S-) IDFinding = set of duplicate submissions sharing a root cause
Submission = an individual warden or team's submission to the audit
Severity: the judge's assessed severity (see Severity criteria)
Title: the title of the submission
Triage: initial evaluation by the Validator [deprecated]
Review: input from the sponsor, if available
Judge: validity and quality evaluations from the judge
Author: username of the warden or team who created this submission
Timestamps
The dashboard defaults to displaying a "Last updated" timestamp. To view more details, hover over the timestamp:

This information can also be accessed via the individual submission screen:

Filters
There are four ways to filter submissions in the dashboard:
Search
Filtermenu (filter by status)SeveritymenuFilemenu
Search
The search function offers a convenient way to locate submissions by keyword. You can also search by:
warden/team name
submission number (e.g.
S-123)
Filter by status ("Filter" menu)
From the Filter menu, you can select:
All submissions (default)
Primary submissions - submissions selected as
Primary(best) within a finding (duplicate set)Satisfactory submissions - submissions confirmed as valid and sufficient quality by the judge
Partial credit - submissions evaluated as only eligible for partial credit by the judge
Eligible for awards - all submissions currently eligible for awards
Note that all judge rulings are subject to change until awards are announced.

Filter by severity
From the Severity menu, you may select:
All
Highs and Mediums
Highs
Mediums
Lows
QA/Gas

Filter by file
The File filter on the submission dashboard allows you to search by filename (e.g. contracts/Token.sol ) and if desired, to set a first and last line to further narrow results. The filtered results are based on the file and line(s) of code referenced by the submitter.

The Submissions touching same files section within the individual submission screen links to a similarly filtered view:

Individual findings and submissions
To view an individual finding or submission, click on the title from the submission list. It will open the relevant finding or submission.
Finding pages
When viewing a finding (group of duplicate submissions), you'll see:
an excerpt from the primary submission in the finding set,
a timeline of inputs and evaluations, and
a list of all duplicates within the finding set.


Submission pages
The Submission page is slightly different from the Finding page:
Instead of an excerpt, the full-length submission is displayed.
Duplicates are listed in a block on the right side of the screen.
You may also view a list of submissions by the same author.


Interpreting the Timeline
The Timeline block displays a series of inputs and evaluations; it expands as the audit phases unfold.
Submitted: severity level selected by the warden (or team) at the time of submission
Triage: initial evaluation by the Validator [deprecated]
Review: input from the sponsor, if available.
Judging: validity, severity, and quality evaluations from the judge (see Judging criteria)

Dashboard permissions and submission visibility
Only wardens who participated in a competition can view submissions during the judging, awarding, and reporting phases.
After the audit report is published, valid submissions (including A- and B-grade QA reports) are publicly accessible; invalid issues are not.
Wardens may see their own submissions during all phases.
If you cannot see submissions to an audit in which you participated
If the submission deadline has passed, but you're unable to view submissions other than your own, the most likely explanation is that the audit includes live/deployed code. In this and other cases where submission access is restricted, staff will:
include a note in the audit repo's
READMEfile (seeView repoon the audit page), andpost details in the audit channel, in the C4 Discord.
Last updated
Was this helpful?