front page
front page when admin connected, shows admin panel
on submit, opens metamask
submiting a prediction
showing use of mode testnet
admin cannot submit prediction. This is hardcoded in the contract.
latest predictions table, updates in real time (added after the video!oops)
get reward if won
winners card animation
mobile view
admin panel

🐸 Gumbledapp

A decentralized prediction-based game built on the Mode network, made to leverage the Sequencer Fee Sharing (SFS) mechanism. Gumbledapp allows users to make predictions on specific events, submitting predictions and competing for a chance to win a share of the sequencer fees collected by the contract.

For this hackathon I tried to utilise SFS creatively, looking for ways the concept could be used in a fun way. This dApp offers an engaging and potentially rewarding way for users to engage with the SFS mechanism and test their prediction skills.

Inspiration

Really like the concept of sfs, very much like the thought of being able to share the goodness around and thought maybe it could be used for that somehow. For the design, I was inspired by bladerunner/cyberpunk/dingey dark late nights.

What it does

Very simply, a user can submit their prediction on whatever event is stated. If they are within the top 3 closest guesses, they win a share of the sequencer fees collected by the contract. That’s it. I wanted to be able to share the sequencer fees instead of only one wallet keeping them all. The contract does almost al the logic, including figuring out the winners and distributing the rewards.

How I built it

First off, started with building out the solidity contract, used Remix for testing and ultimately deploying. Once most of the functionality was there I then started to build out using react for the front end. Kept it to vanilla CSS. Built on my old 2012 laptop (not a typo, twenty-twelve), so had lots of breaks for overheating... both the laptop, and myself.

Challenges I ran into

Keep hitting brick walls with my ideas when I realised some parts were still impossible to build in due to it all being so novel, for example being able to know how much the sfs has generated so far, I’ve left in it there for future functionality. Also, due to the way the sfs works with the 2 week epochs, there’s quite a lot of guesswork. Time was a challenge, not having enough of it. Hackathon deadline 2 days before Christmas, jfc. But was motivated cos I really do think being able to share the earnt transaction fees is such a good idea. Working alone can also be a challenge.

Accomplishments that I’m proud of

Keeping it simple on the front but enough complexity in the back. It’s a mullet of a dapp.

What I learnt.

I learnt a whole lot about SFS, I learnt how to register a contract to the SFS register contract, and then how to assign a contract to the sfs nft that I had registered with, and then how to withdraw the earned fees. I also learnt that the sfs nft is only the claim for the earned fees, just a representation, rather than holding the fees itself and becoming higher value from it.

What's next for Gumbledapp

-Immediate next step is to decentralise it more, as much as possible, so adding an Oracle is urgent and would help with this. -Would also like to add more front end functionality, for example a feature where users can vote on what prediction is next, with the voting contract also holding the sfs nft of the main pool. Other functionality includes running more predictions in tandem that can be played at once. -I want to refine the prediction measurement to include decibel places and only one number allowed to be predicted per cycle, so for example if someone has already predicted number 1, that is theirs, and no longer available. -Also waiting for Modes next steps with how far we can take sfs. -and there's always de-bugging to be done.

ps. its minor but since the video was filmed the dapp now has a Live Latest Predictions board