Inspiration
Early doom games had the capacity to save player inputs into a file. In which, players were able see there games again. This tool soon used as a means of proving speed runs. However, a problem emerged with induvial began editing and using scripting to cheat. The file format allowed the community to find clues of obvious cheating and manipulation. However, there was still room for cheaters fall through the cracks.
Our project attempts to remedy this solution by allowing a speed runner to submit there runs live. minimizing the time cheaters have to manipulate and allowing auditors to check the speed run.
What it does
Client Side Script
The client side application handles tracking and sending information related to the smart contract.
Smart Contract
The smart contract handles the storage and verification of all player inputs. The smart contract is also responsible for providing auditors with the full list of inputs.
How we built it
Both applications were build in rust.
Challenges we ran into
Many team members have never worked with smart contracts or rust before. As a result many team members had a steep learning curve.
What we learned
How smart contracts work How to program in rust
What's next for Speed Run Verification
The next step to link the front end and smart contract. Afterwards, SRV plans on adding more more verification and stats executions.
[Hybrid]
Log in or sign up for Devpost to join the conversation.