Web3_Championship
/
Polkadot_Championship_Challenges
1
1
Fork 1
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Actualization of README, you can start forming teams 

Small changes
master
six 2023-11-16 08:58:14 +00:00
parent ecc9ef146f
commit bb1dbbd2e0
1 changed files with 6 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
README.md
View File

@ -50,42 +50,17 @@ Hard - Web3 business plan - Creation of a legit web3 business plan can be tough.
# Main event
The main event consists of a 3-day hackathon where projects can be conceptualized and implemented, and also of more challenge-solving in parallel.
The main event consists of a 3-day hackathon where projects can be finalized. First day is the day for education, second day is about DEADLINE MODE ON, then the third day is about the presentation of the projects. You can already get started with team formation and working on the main challenges!
At first, teams should be formed by qualified players.
Your final project needs to be conceived during the main event. Mentors and workshops will help you make it happen.
The main event's challenges will be disclosed on 2023-12-04 at 10:00:00 CET/. The teams will need to solve at least one from each challenge track, in 24 hours.
[Link to Main Challenge Details](https://git.hsbp.org/Web3_Championship/Polkadot_Championship_Challenges/src/branch/master/Main_Challenges.md)
Note: You can already prepare libraries and some code before the hackathon, but the final project needs to be conceived during the main event.
Playing teams will need to choose one challenge as their main one. Additionally, they need to choose at least one from the other tracks and create a proposal for solving them. You can already see good examples from last year's hackathon.
### Challenges for the main event (WIP)
Overall, two things need to be delivered by the teams on the 3rd day: the main challenge solution, a proposal for the second challenge.
As time progresses we share more information regarding the main tracks.
Outline:
#### Track 1 - Decentralized organizations and governance
#### Track 2 - Privacy and Security
#### Track 3 - AI in Web3
#### Track 4 - "Give me a problem and I solve it"
#### Track J - Only for judges and mentors!
### Choosing challenges and deliveries at the final round
Playing teams will need to choose one challenge as their main one. Additionally, they need to choose at least one from the other tracks and create a proposal for improving the projects.
Overall, three things need to be delivered by the teams: the main challenge solution, a proposal for the second challenge, and a proposal for the third challenge.
The teams need to initialize a git project on https://git.hsbp.org/ or https://github.com/ when the 24 hours start and commit all their development there. Commits after the finish of the end of the 24 hours won't be accepted.
The teams need to initialize a git project latest on the 2nd day of the hackathon, on https://git.hsbp.org/ or https://github.com/ (which is shamefully owned by Microsoft) and commit all their development there. Commits after the finish of the end of the 24 hours DEADLINE MODE ON won't be accepted.
### Judging criteria
@ -115,9 +90,6 @@ Judges will score each team's project based on the following criteria:
- Note: don't spend more than an hour as a team on this, but make sure to do it. 5/5 is the maximum score per proposal.
Each criterion has a maximum score of 10 and the judges will decide individually how many scores they vote for the teams. The maximum score a team can get for their main project is 70. After the scores are finalized, they will be presented in the Hall of Fame smart contract.
## Support and feedback for the prequalification
We don't help with solving the challenges, but if something is unclear or you think you've found a bug, we are always open to hear from you.
## Contact