Code4rena runs community-driven competitions for smart contract audits. Thousands of auditors from around the world compete to keep high-severity bugs out of the Web3 ecosystem and make crypto projects safer. C4’s competition model aligns three core sets of interests in support of a more secure, stable, and prosperous Web3:
- Web3 projects get the best talent in the industry, on demand — and many skilled eyes on their code;
- Wardens (security researchers) compete for generous prize pools, guaranteed payouts, elite status, and performance-based opportunities;
- The broader Web3 community benefits from published reports, responsibly disclosed vulnerabilities, and a supportive learning community where newcomers can build skills and get paid.
That’s the view from the outside. From the inside, you’ll find Code4rena to be a warm, inclusive community. C4 staff are kind and conscientious people who are excited about working in a cutting edge industry.
How Code4rena competitions work
- C4 staff work with contest sponsors to scope their project’s code and determine a prize pool that will attract top auditors.
- Competitions run for 3-14 days. During this period, wardens review the code and submit vulnerabilities to C4.
- After the competition, a judge reviews the submissions, as does the sponsor team. The judge assesses the validity and risk level of all submissions.
- After judging is finalized, C4 distributes awards to all wardens who submitted valid findings.
- As soon as the sponsor team mitigates the vulnerabilities, C4 releases an audit report.
Competitions Administrator (MVP) responsibilities
Competitions Administrators’ primary responsibility is to support sponsors, wardens, and judges through the competition process. The MVP Specialist will focus on supporting the implementation of new offerings, and handling the logistical side of MVP (minimum viable product) prototypes.
This role reports to the Competitions Administrator Manager, and also works closely with our Head of Customer Success, to support new product offerings that have yet to be integrated into the team’s standard operational processes.
On a day-to-day basis, this looks like:
- Hands-on work to ship MVP offerings quickly. The Head of Customer Success will prototype processes, and you will execute and document them as they’re iterated.
- Communicating with stakeholders. The new offerings will require answering questions and shepherding sponsors, wardens, judges, and other community members through processes that are in development.
- Iterating and improving processes. Each MVP is an experiment with a hypothesis, and involves rapid iteration. You will help the Administration and Customer Success teams to iterate and improve the process with each iteration.
You’ll thrive in this role if you:
- are skillful at tracking input from multiple sources in order to create cohesive output;