Skip to content
RideTheBet

RideTheBet

Unleash your predictions in decentralized duels!

Created on 12th July 2025

RideTheBet

RideTheBet

Unleash your predictions in decentralized duels!

The problem RideTheBet solves

If you're a sports fan, you know that the conversation around a big match is passionate, chaotic, and global. But right now, that engagement is fundamentally broken.
Right now, you have thousands of fans with brilliant insights, making predictions on social media. But these opinions are ephemeral—they're just text that gets instantly buried in an endless feed. There's no structure, no persistence, and no way to separate a valuable prediction from simple noise
This chaos creates a huge problem: there is zero accountability. An influencer can post ten different predictions, delete the nine that were wrong, and then parade the one correct prediction as proof of their genius. There is no immutable record, no on-chain truth to prove who was actually right over time
There's no way to directly monetize your knowledge or to engage in a fun, high-stakes game against those who doubt you. All of this passion and knowledge is being wasted.

This led us to ask a simple question: What if we could fix this? What if we could give every fan's opinion real weight, real accountability, and real value on the Chiliz Chain?

That's exactly why we built Ride The Bet. We've created a fully on-chain prediction market that transforms fan opinions from simple text into verifiable, high-stakes duels.

Here’s how it works, in three simple steps:

First, an influencer creates a prediction. They don't just post an opinion; they create a formal duel on the Chiliz Chain and stake their own $PSG tokens to prove they have real skin-in-the-game.
Second, the community gets involved. Instead of just liking or commenting, fans can now stake their own $PSG tokens to either upvote the prediction, joining the influencer's pool, or downvote it, forming a pool of opposition. This creates two distinct, transparent, and competing sides for every single bet.
And finally, the winner takes all. When the match is over and the bet is resolved, our smart contract automatically executes the outcome. The entire stake from the losing pool is proportionally distributed among every single member of the winning pool.
We've turned a chaotic social media argument into a structured, decentralized, and incredibly engaging game where knowledge is rewarded and every prediction has real, verifiable consequences.

So, to bring this vision to life, we focused on four key features that make Ride The Bet a complete and robust platform, not just a proof-of-concept.
First, we built an On-Chain Influencer Identity system. This isn't just a username; it's a permanent, verifiable brand on the Chiliz Chain, allowing influencers to build a reputation based on their actual, proven performance.
Second, we introduced Leaderboard Gamification. All results are tracked in real-time, creating a competitive and fun environment where the most skilled predictors rise to the top, and users can easily discover who to trust and follow.
Third, and most critically, is our Economic Security model. To create a duel, an influencer must lock a minimum stake of their own tokens. This 'skin-in-the-game' requirement provides a powerful guarantee of quality and acts as a security layer that blocks bots and spam, ensuring a high-quality market for everyone.
And finally, all of this is wrapped in a Dynamic and Seamless UI. Our platform is built mobile-first for the modern fan, providing real-time updates on duel pools and a simple, secure transaction experience for voting and claiming winnings.

These features combine to create a platform that is not just functional, but also secure, engaging, and ready for the community.

So, what you've just seen is our foundation. But our vision for Ride The Bet is to evolve from a dApp into a fully automated, trustless, and self-sustaining protocol
First, we'll activate our Pyth Oracle integration, to set the minimum stake for duels in a stable USD value, making the platform fair and accessible for everyone.
Second, we'll integrate Chainlink to fetch live match results automatically. This will make bet resolution completely trustless and instant, removing any single point of failure.
Looking further ahead, for high-value markets, we envision creating a specialized AVS with EOracle with EigenLayer's restaking underlying. This would allow the community itself to guarantee outcomes, achieving the ultimate level of decentralized security.
And finally, to fund this growth, we'll implement a small Protocol Treasury fee. This ensures the platform has the resources to continue innovating and remain a leader in decentralized fan engagement.

So, we're not just building an app; we're building the future of how fans interact with the sports they love.
And just so you know, this whole project went from idea to execution in the last 18 hours. So I hope you enjoyed the presentation. Thank you.

Challenges I ran into

One of the most significant challenges I ran into was a classic cross-chain compatibility problem, highlighting the subtle yet critical differences between various EVM-compatible networks. This hurdle manifested in a critical bug that required a methodical, step-by-step debugging process under intense time pressure.

The influencer registration function worked perfectly on both the local Remix IDE VM and on the public Base Sepolia testnet. However, when the exact same, fully functional contract was deployed to the Chiliz Spicy Testnet, the registerInfluencer function reverted every single time.

The Debugging Process:
This was particularly challenging because the code was logically sound and operational on other chains. To isolate the problem, I began battle-testing the function by stripping it down to its core components. I removed all require statements and tested the two mapping write operations individually:

_registeredNameHashes[nameHash] = msg.sender; -> This consistently reverted on Spicy.

influencerNames[msg.sender] = _name; -> This also reverted on Spicy.

This systematic testing led me to believe the issue wasn't with my logic, but potentially with a unique configuration on the Spicy Testnet related to state changes involving mappings, possibly due to gas calculation differences or a specific node implementation.

How I Got Over It (The Hackathon Choice):
As I had started this project just 18 hours before the submission deadline, I had to make a pragmatic choice to deliver a functional product. After documenting my detailed testing, I decided to record the final video demo on the Base Sepolia testnet, where the feature was fully operational. This allowed me to showcase the complete vision and user flow of the dApp without being blocked by a chain-specific issue that required a deeper investigation than time would allow. This hurdle was a powerful lesson in the subtle differences between EVM-compatible chains and the importance of prioritizing a working submission under tight deadlines.

Tracks Applied (1)

Fan Token Utility

We specifically chose the 'Fan Token Utility' track because our project's core mission is to answer one simple question:...Read More

Discussion

Builders also viewed

See more projects on Devfolio