Bull Run
It is a blockchain-powered Monopoly-like game where players claim real-world properties, earn rewards, and explore cities, blending strategy, AI-driven events, and Web3 for an immersive experience.
Demo
About
The problem it solves Bull Run addresses the gap between digital gaming and real-world exploration by gamifying travel through blockchain. Here's how it solves key challenges: Real-World Engagement in Gaming It incentivizes players to explore real-world locations, encouraging physical movement and cultural discovery, unlike traditional sedentary games. Blockchain Transparency and Ownership Players own virtual properties tied to real locations as NFTs, offering true asset ownership and secure transactions. This removes the risk of losing progress or assets common in traditional games. Enhanced Travel and Tourism By linking gameplay to real-world sites, it promotes tourism and local business engagement, offering a unique way to discover cities while earning rewards. Gamified Urban Exploration Tasks like visiting landmarks, navigating hotspots, and solving location-based challenges make exploring cities fun and interactive. AI-Powered Personalization AI-driven events and tailored challenges enhance engagement by keeping gameplay dynamic and relevant to individual player behavior. Financial Inclusion and Incentives By earning cryptocurrency or in-game tokens, players access potential financial benefits, bridging gaming with blockchain-based economies. Community and Social Connection The multiplayer aspect fosters collaboration and competition, building vibrant communities centered on shared experiences. In summary, Bull Run transforms the way players interact with cities, combining strategy, travel, and blockchain ownership to create a seamless blend of gaming and real-world exploration.It
How it's made
Challenges we ran into While building on Okto, we encountered several challenges. Initially, we faced authentication errors when calling APIs, followed by issues with the raw transaction API due to problems with the ABI encoder. Subsequently, reading data from the smart contract presented difficulties, which we resolved by utilizing an external RPC URL. Currently, we are dealing with a transaction lifecycle issue where transaction data is not being fetched synchronously, affecting the overall workflow.