Existing dapp sportcrypt.com, idea for contract version 2
What it does
For every event that people would like to bet on, a matchId is computed from the event details. This matchId is what is used to refer to the positions and orders. The matchId's encoding is chosen in such a way that the smart contract has access to all the parameters it needs with nothing needing to be added to the chain in advance, and no unnecessary storage usage.
How I built it
Challenges I ran into
Difficult to debug solidity code.
Accomplishments that I'm proud of
We got full end-to-end dapp betting solution prototyped, and proved the concept of merkle-tree encoded matchIds.
What's next for Scalable Betting Solution
Take these ideas and implement them for SportCrypt contract v2.
Log in or sign up for Devpost to join the conversation.