Charts and statistical insights for Code4rena.
You can use nbviewer or to run the notebooks online.
You can also git clone [email protected]:Krow10/code4rena-stats.git
and run JupyterLab for running them locally.
findings
: value ($USD) of findings by category, etc.trends
: looking at present (and future) trends in the Code4rena space.wardens
: warden's participation over time, rewards, etc.
Data is pulled from the community resources given by Code4rena. There are two main .csv
files that are regularly updated with new contests. My older project used to scrape additional data from GitHub and the Code4rena website, but this is not necessarily needed anymore.
findings.csv
contest | handle | finding | risk | score | pie | split | slice | award | awardCoin | awardUSD |
---|---|---|---|---|---|---|---|---|---|---|
Contest ID | Name of the warden (or team) | Finding ID with risk prefix | Risk level as integer | ? | Number of shares for the finding1 | Number of identical submissions for the finding1 | Number of shares assigned to the warden's finding1 |
|
Coin used for the reward | Converted coin amount to $USD |
contests.csv
contestid | title | sponsor | details | start_time | end_time | amount | repo | findingsRepo | hide | league |
---|---|---|---|---|---|---|---|---|---|---|
Contest ID | Contest title | Contest sponsor | Summary of project | Start time for contest in date time format (e.g. Wed Feb 17 2021 00:00:00 GMT+0000) | End time for contest in date time format | Total prize pool for the contest | GitHub repo of the project | GitHub repo for submissions to contest | Used to hide contest from showing on the website | Mostly blockchain identifier for the project |
Footnotes
-
From Code4rena docs ↩ ↩2 ↩3 ↩4