Search projects, hackathons, sponsors and tech

    ← All projects

    Spoiler

    Spoiler is a prediction game that positions you as if you're from the future, ready to reveal what will happen next.

    About

    The problem it solves In the ever-evolving landscape of social media and interactive entertainment, a new player has entered the game: Spoiler. This unique prediction game brings an exciting twist to engaging with social media content. Spoiler is not just a game; it's a new way to interact with social events and content, merging the thrill of betting with the dynamic world of social media. Spoiler is a prediction game that positions you as if you're from the future, ready to reveal what will happen next. The game will initially center around social activities on Farcaster where players make predictions about upcoming actions on Farcaster using their $DEGEN tokens. Spoiler combines the essence of social media interactions with the fun and excitement of a betting game, allowing users to engage with Farcaster content in an entirely new way. By betting on real-time events and earning points for accurate predictions, Spoiler adds an engaging layer of excitement to social interactions.

    How it's made

    Challenges we ran into Contract
 Since our app is based on smart contract, we put a lot of effort into implementing the betting logic and revenue sharing logic of the contract.
 All core logic for betting and result processing is handled within the contract, we put a lot of thought into security. We made significant efforts to prevent users' funds from being hacked due to contract errors.
 First, we separated the logic for creating and processing prediction markets from the logic for recording users' betting amounts at the contract level. We also designed the contract that holds the DEGEN tokens used for betting to be separate.
This design ensures that issues arising from a single bet do not spread to the entire product, and users' funds remain secure unless the admin account of the treasury is compromised.
 Furthermore, we enhanced security by dividing the management accounts into multiple layers, separating the addresses responsible for light management from the admin address that can handle actual funds. Farcaster Frame
 The technical specifications of Farcaster Frame were a challenge at first because we wasn't familiar with them, especially the 256 bytes limit for post_url.
 also UX of the Farcaster Frame faced difficulties in handling complex logic.
Due to the nature of the prediction market, users had to click multiple buttons to place their bets. During this process, the frame transitions were somewhat slow, potentially causing inconvenience for users.
As a result, we decided to maintain only the minimal functionality within the Farcaster Frame and implemented the actual processing on a separate web page.
 If the time between button clicks and screen transitions within the frame were reduced, and the operations within the frame were handled more smoothly, like a SPA (Single Page Application), we believe we could add even more exciting features.