Skip to content

ethglobal/ethsanfrancisco-bounties

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 

Repository files navigation

ETH San Francisco Prizes

Hackers, check out some of the great prizes we've put together with the help of some of the top projects in the ecosystem!

Sponsors, please double check the information below to make sure you're prepared to answer any questions hackers might have for you :)

Prize List

Sponsor prizes are set up as Gitcoin bounties in this very repo. Sponsors will be adding to these up until the hackathon begins so check back for new ones! The main prizes will be announced at the end of the hackathon as a surprise :)

How to win prizes for dummies

1) Make sure you're eligible to participate!

While participating at ETHGlobal events like ETH San Francisco is essentially as easy as contributing to an open source project, you do have to be physically present. Registration will take place on October 5th at 4:00pm in the Palace of Fine Arts. If you have not received a message confirming that your application to ETH San Francisco was accepted please reach out to us at [email protected].

2) Before the hackathon

2.1) Form your team

Teambuilding will happen at ETH San Francisco. If you don't already have one you'll be able to find plenty of awesome developers, designers, and other talented folks to work with! To make prize distribution easier, please try to create a Github repo for your team.

2.2) Keep calm, and don't start coding yet!

Hacking starts at the hackathon. Teams can form and ideas can evolve before the hackathon. However, the code base, hacks, and prototypes that you create for any apps competing for prizes or bounties need to evolve only during the hackathon. Apps, hacks, and projects that were built before the event do not qualify and will be excluded from judging and any prizes.

And please don't forget to sync your Ethereum nodes ahead of the event :)

2.3) Check out the sponsor prizes available

Some of ETHGlobal’s sponsors have their own prizes. Note that ETHSanFrancisco has no influence on either the challenge or the judging, this is entirely up to the sponsors. You can find all the prize awards, you guessed it, here.

Please note that you can submit your work to multiple prizes, they are not exclusive! So for example you can submit your work to the open track bounty and a sponsor specific prize, just make sure to submit it everywhere you want to participate.

3) At the hackathon

3.1) Register yourself

ETHSanFrancisco starts on October 5th at 4:00pm in the Palace of Fine Arts. Please try to arrive on time as participants that are too late may not be able to participate.

3.2) Start work on the associated Gitcoin bounty (check out the issues in this repository for some of the bounties available)

Before starting work, we recommend creating a new GitHub repo for your team to make it easier for sponsors to see everyone involved in your project. Please ensure that all team members are visible publicly to sponsors so they know who to pay the prizes to :)

Each prize is set up as a cooperative bounty on Gitcoin. This just means that any number of people can start work using the start work button on each issue's associated Gitcoin page. You can find a link to any bounty you're interested in within the GitHub issue itself, or you can check out Gitcoin's issue explorer here. Each hacker, not just one team member, should start work on the prizes their team is working towards in order to be paid out. Don't worry if you're not immediately sure which prizes are relevant to your team, you can start work on the issues relevant to your team at any time up until judging begins.

After you’ve started work, most of your interaction with the prize teams can take place on GitHub and in the associated community channel for longer conversations requiring more specific context about your project.

3.3) Buidl

Work on your project as you like, how you work is up to you! However, remember to only begin working on your project after the hackathon begins!

4) Submit your project

4.1) What to include

When you’re happy with what you’ve built you can submit it by creating a pull request for the issue the Gitcoin bounty is associated with.

What your submission should have:

  • A link to the open-source code must be provided. Please keep it accessible to everyone after the submission deadline.
  • A short presentation file must describe your project. It has to be accessible without special tools. Ideally a PDF, Google slides, or even a hosted recording if you like. The judges need to all be able to access those presentations.
  • The contract address(es) of your deployed demo must be provided, either on a testnet of your choice (Kovan, Rinkeby or Ropsten) or on Ethereum mainnet; instructions on how to interact with the contract(s) are appreciated.
  • A URL to any publicly accessible web-interfaces and demo credentials if applicable.

4.2) How to submit

If you want your project considered for particular bounties, you can submit your project by creating a pull request on the issue the Gitcoin bounty is associated with and submitting work by clicking submit work on the associated Gitcoin bounty page.

You can apply to multiple prizes simultaneously, if you think your project conforms to each one's judging criteria.

You can open a PR before the submission deadline and continue to work, but all materials must be finalized and you must submit work on the relevant Gitcoin bounties before the end of the hackathon. Any commits to your project submission after the deadline will not be considered.

5) After the hackathon

5.1) Congratulate everyone on a job well-done

Whether or not you get a prize, you deserve to be proud of your work. Thanks for buidling!

5.2) Enjoy the rest of blockchain week!

ETH San Francisco is just one part of a week long celebration of blockchain. Stick around and check out some of the other great events and parties.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published