The problem ScanQuest solves

Engaging your community, captivating fans, and attracting new leads through interactive real-world treasure hunts featuring your products.

Try the demo now: ScanQuest Demo on Base Sepolia.

ScanQuest boosts event engagement by integrating a QR-coded treasure hunt that captivates participants with discovery and prize excitement. Whether as a main attraction or added feature, this innovative approach boosts foot traffic across all event areas, ensuring maximum exposure.

Discover: Participants explore the event venue, scanning QR codes to uncover hidden treasures and surprises.

Scan: QR codes lead to loot boxes containing prizes such as merchandise, gift cards, or exclusive services.

Win: Winners receive NFTs representing their prizes, ensuring secure ownership and the option to trade or sell rewards on blockchain platforms, adding ongoing value beyond the event.

Cashout: Last but not least, winners can redeem their prizes anytime, receiving either their chosen virtual rewards online or physical items delivered directly to them.

By leveraging blockchain technology, ScanQuest simplifies prize distribution, enhances transparency, and prevents fraud. This not only increases attendee satisfaction and engagement but also provides organizers with valuable insights into participant behavior for optimizing future events and marketing efforts.

Challenges we ran into

Geolocation Integration in React: Integrating precise and glitch-free geolocation was a significant hurdle, especially since existing libraries did not meet our requirements for accuracy and smooth functionality in a React environment. We overcame this by developing our own custom solution, leveraging the more precise and less buggy browser API to ensure reliable location tracking for our users.

Complexities with Paymaster and Thirdweb: Integrating Thirdweb and Paymaster on both the frontend and backend added a layer of complexity not present with traditional wallet extensions. Initially, we verified transactions to ensure that the redemption process was correctly executed, which worked until we integrated user operations from the Paymaster bundler. This led to discrepancies that we resolved by shifting our verification process to use transaction event logs instead of the transactions themselves, allowing for more accurate assertions of redemption validity.

Compatibility between Thirdweb SDK and Coinbase SDK: Thirdweb abstracts away a lot of the complexity and makes it very easy to get up and running, but makes it harder to customize for a specific use case. Coinbase SDK on the other hand makes it easy to customize but there a still a lot of boilerplate codes that needs to be implemented before it's actually usable. But hey, we're early so it's part of the game!