Create and Submit a First Flight
Last updated
Was this helpful?
Last updated
Was this helpful?
Community First Flights are Cyfrin's most recent expansion to our First Flight initiative. Community First Flights presents the perfect opportunity for those wanting to contribute a fun code base or strengthen the developer side of their skill set!
The rules are simple:
Create a fun project with a theme! (Holidays are popular)
Ensure the in-scope contracts are ~ 100-200 nSLOC
The project should have a maximum complexity of 200
In addition to the above, First Flights are meant to contain bugs! Make sure your project intentionally includes:
One or two easy-to-find bugs
One medium-difficulty bug
One hard-to-find bug
One High/Critical
One Low
Be sure to write up an answer key detailing the intentional bugs you've placed in your code!
The final piece required is to ensure your project has an appropriate README. Please use the template provided below and tell us about your protocol!
Submissions will be accepted on a first-come, first-served basis. A few things to note:
A submission must be fully vetted and accepted before being 'in line'.
First Flights are held twice/month.
In order to run the contest, we require at least three days' notice before the next expected First Flight.
Code bases ready with less notice than this will be scheduled for the next available First Flight.
Cyfrin retains the right to shift to a lottery selection process should the pending submissions grow too large.
Once your repo is ready fill out this and, ping @equious.eth on . He will arrange the sharing of your code base privately. From here, your submission will be vetted, and you'll be provided any necessary feedback or adjustments that require implementation.