The problem Khoj solves

1. Lack of Engagement in Web3 Adoption: Web3 adoption faces barriers due to its technical complexity and lack of relatable, engaging entry points for non-technical users.
2. Decline in Real-World Exploration: In a digital era, people often miss out on physical-world experiences.
3. Limited Interactive Marketing for Brands and DAOs: Brands and blockchain communities struggle to engage users meaningfully.

Core Gameplay

• Progressive Riddles: Each hunt consists of multiple interconnected clues that tell a story. This is procedurally generated by the AI.
• Location-Based Verification: The answer to each clue is a physical location.
• Personalised Clues: The clues are tailored to the user's taste using AI while still keeping the answer same.
• Multiple Attempts: Players get 3 attempts per clue to verify their location
• Real-time Collaboration: Built-in video chat for team coordination.
• Rewards & Reputation: Fastest players win rewards based on a reputation score generated which can be redeemed later.

Web3 Integration

• Multi-chain deployment (Base, Moonbeam, BNB Chain).
• Seamless login via Coinbase SDK and NFT-based registration.
• Decentralized storage (Walrus Network) and on-chain clue attestations.
• Smart contracts for hunt registration and rewards.
• Token rewards for achievements and milestones.

Use Cases

1. Co-branded Hunts: Promote products or services creatively.
2. Airdrops: Distribute tokens through gamified participation.
3. Community Engagement: Strengthen DAOs and NFT communities.
4. Educational Hunts: Engage students and visitors at museums or landmarks.
5. Tourism Promotion: Drive interest in cultural and historical sites.
6. Team Building: Foster collaboration within corporate teams.
7. Event Engagement: Enhance festivals and expos with interactive hunts.
8. Fitness Incentives: Gamify physical activity with rewards.

Challenges we ran into

1. Designing the overall workflow and all taking all architectural decisions was difficult.
2. Integrating Lit Protocol as a sponsor took a lot of time.
3. Figuring out how to stream to YouTube via Huddle.
4. Integrating all the different pieces and interactions between the frontend, backend and the smart contract.