WIP - 2023
parent
06f1014707
commit
c337680836
50
README.md
50
README.md
|
@ -1,6 +1,8 @@
|
||||||
# Polkadot Metaverse Championship - Challenges
|
# [WIP] Polkadot Championship 2023 - Challenges
|
||||||
|
|
||||||
The [Polkadot Metaverse Championship (PMC)](https://metaversechampionship.gg/) is an open web3/cryptocurrency contest consisting of a qualification phase and a main event.
|
This document is a work in progress, being updated for 2023!
|
||||||
|
|
||||||
|
The [Polkadot Championship (PMC)](https://polkadotchampionship.org/) is an open web3/cryptocurrency contest consisting of a qualification phase and a main event.
|
||||||
|
|
||||||
# Qualification
|
# Qualification
|
||||||
|
|
||||||
|
@ -21,11 +23,11 @@ The format of a solution is an ASCII string of the form __PMC{...}__, like PMC{#
|
||||||
You can verify the correctness of your solutions before submitting the form. The flags have the following respective Keccak-256 hash values:
|
You can verify the correctness of your solutions before submitting the form. The flags have the following respective Keccak-256 hash values:
|
||||||
|
|
||||||
```
|
```
|
||||||
kusamaverse - 0x896c90f019d0aaa7977ce81c7d7299b1b43d302295f2d567509ab7e3060a797f
|
js/wss - TBA
|
||||||
wss - 0x2f2d4bb11521956c486925241ffcca0cbf7b79bbd9be8eafaeb4fab95713b12d
|
solidity - TBA
|
||||||
solidity - 0x81b1ff6939fedd672ddac358a41abb7192ae1f0660a3b1cbf92ef2c82119612b
|
gear - TBA
|
||||||
ink - 0x82703a464305aad655e2eb617f31e6e57b7e959bf8528f1d3b5968cc02ed60ac
|
rust - TBA
|
||||||
rust - 0x42ce6fca873fe4dc4ce4d9accdb53e02fdb497ffa6b30f421cea36c81d8ea289
|
crypto - TBA
|
||||||
```
|
```
|
||||||
|
|
||||||
To calculate the Keccak-256 hash of a string, you can, for example, install `keccak256-cli` using `cargo`, and then use the `keccak256` command like so:
|
To calculate the Keccak-256 hash of a string, you can, for example, install `keccak256-cli` using `cargo`, and then use the `keccak256` command like so:
|
||||||
|
@ -36,15 +38,8 @@ echo 'PMC{This_Could_be_a_Flag.!}'|keccak256
|
||||||
|
|
||||||
## List of prequalification challenges
|
## List of prequalification challenges
|
||||||
|
|
||||||
__WSS challenge__: you need to play with a websocket connection and get the flag from the service. It is called Fibonacci.
|
__TBA challenge__: TBA
|
||||||
|
|
||||||
__Solidity challenge__: a security audit might reveal what the developers think is private might actually not be.
|
|
||||||
|
|
||||||
__Rust challenge__: work with RSA cryptography and math. The correct math will return you the flag.
|
|
||||||
|
|
||||||
__ink! challenge__: you need to get the flag from an already running Substrate node or find "another" way. Make sure to web2 scan everything.
|
|
||||||
|
|
||||||
__Kusamaverse challenge__: find the flag in Kusamaverse - this one is very easy, but important for the main event.
|
|
||||||
|
|
||||||
### Design for fame
|
### Design for fame
|
||||||
|
|
||||||
|
@ -56,33 +51,38 @@ The main event consists of a 3-day hackathon where projects can be conceptualize
|
||||||
|
|
||||||
At first, teams should be formed by qualified players.
|
At first, teams should be formed by qualified players.
|
||||||
|
|
||||||
The main event's challenges will be disclosed on 2022-12-06 at 10:00:00 CET. The teams will need to solve at least one from each challenge track, in 24 hours.
|
The main event's challenges will be disclosed on /TBA, probably 2023-12-04 at 10:00:00 CET/. The teams will need to solve at least one from each challenge track, in 24 hours.
|
||||||
|
|
||||||
Note: You can already prepare libraries and some code before the hackathon, but the final project needs to be conceived during the main event.
|
Note: You can already prepare libraries and some code before the hackathon, but the final project needs to be conceived during the main event.
|
||||||
|
|
||||||
### Challenges for the main event
|
### Challenges for the main event
|
||||||
|
|
||||||
The details of the main challenges will be shared on 2022 December 6th 10:00 CET. The teams formed before will need to solve at least one from each track, in 24 hours: one of them should be the team's main delivery and the two other are in proposal form. You can already prepare libraries and some code before the hackathon, but the final ideation and project needs to come out during the main event.
|
The details of the main challenges will be shared on /TBA, probably 2023 December 5th 10:00 CET/. The teams formed before will need to solve at least one from each track, in 24 hours: one of them should be the team's main delivery and the two other are in proposal form. You can already prepare libraries and some code before the hackathon, but the final ideation and project needs to come out during the main event.
|
||||||
|
|
||||||
Outline:
|
Outline:
|
||||||
|
|
||||||
#### Track 1 - Collaboration
|
#### Track 1 - Decentralized organizations and governance
|
||||||
|
|
||||||
Challenge 1 - Momentum's Kusamaverse related
|
Challenge 1 - TBA
|
||||||
|
|
||||||
Challenge 2 - Pallet in 24 hours - Requirements specified by Unit Network
|
Challenge 2 - TBA
|
||||||
|
|
||||||
#### Track 2 - Privacy and Security
|
#### Track 2 - Privacy and Security
|
||||||
|
|
||||||
Challenge 1 - Decentralizing Secureground - CCTF project related
|
Challenge 1 - TBA
|
||||||
|
|
||||||
Challenge 2 - Privacy and hacking research related
|
Challenge 2 - TBA
|
||||||
|
|
||||||
#### Track 3 - GameFi and NFT
|
#### Track 3 - AI in Web3
|
||||||
|
|
||||||
Challenge 1 - RMRK project related
|
Challenge 1 - TBA
|
||||||
|
|
||||||
|
Challenge 2 - TBA
|
||||||
|
|
||||||
|
#### Track 4 - "Give me a problem and I solve it"
|
||||||
|
|
||||||
|
Challenges - TBA
|
||||||
|
|
||||||
Challenge 2 - KILT related
|
|
||||||
|
|
||||||
#### Track J - Only for judges and mentors!
|
#### Track J - Only for judges and mentors!
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue