Betting on a Scalable Future
Date and time
Your Hacker House with Azuro and Gnosis Chain community. Come visit us to relax, hack, earn prizes and much more!
About this event
We welcome hackers and web3 enthusiasts to join us for a multi-track hacker house with speakers from Gnosis Chain, Gnosis Safe, Cow Protocol and a pre-mainnet launch workshop from Azuro featuring a 7 hours hackathon with cool prizes.
We are excited to experiment with new forms of contributor recognition for the hackathon and to meet our fellow community members.
Breakfast, Lunch, Snacks & Drinks will be provided, and, obviously, loads of POAPs!
All visitors of the hacker house will be automatically registered for our After party 💃
Workshop Schedule:
09:00AM - Opening/ Registration - Hackers Survival Kit delivery
10:00AM - Hackathon presentation and task delivery
11:00AM - “How to Deploy on Gnosis Chain” Dan Kaizer, CTO at Azuro
12:00PM - "Integrating the Safe Core SDK" Germán Martínez Gnosis Safe
13:00PM - Lunch
14:00PM - How to build a CoW Protocol Solver for Gnosis Chain?" core team CoW Protocol
16:00PM - "Nifty Demo Workshop" community member at Nifty.ink
17:00PM - Closing
Join Telegram Group
# Hacker challenges
### Dispute Resolution Mechanism
In Azuro's design, every betting event that one can bet on is called a *Condition*.
Conditions on Azuro protocol are usually initialised 3-5 days before the match or the game. They are initialised via [oracles] which deliver data to the protocol.
Each Azuro condition is initiated by [Feed Providers], and also - is resolved in the same way (via Feed Providers & Oracles).
Challenge #1 is to propose a Dispute Resolution Mechanism to handle situations when a Feed Provider(Oracle) provides an incorrect outcome.
### Rewards System
Azuro have an SDK. With this tool anyone can create a betting site powered by Azuro protocol. Such websites are called **Frontends**
Challenge #2 is to create a Rewards System which checks the performance of the Frontend and shares protocol revenue accordingly.
Some core parameters that should be tracked are e.g.:
- For each Bet that was made through the Frontend, Frontend Operator should get x% of the amount of the bet (if that bet ends up to be a losing one).
Contracts for experiments to build reward system on top:
- Betting transactions tracker / Totebetting Github
- Uniswap V2/V3 (For swaps/ lp proving)
- Any kind of Base Contract
Your should fill the form until 15:59 GMT+2. Good luck!
