Search projects, hackathons, sponsors and tech

    ← All projects

    Nouns' Wallet Poker

    A Crypto-native poker app for Nouns DAO that has gamification elements & social graph

    About

    The problem it solves ## The Problem it Solves Community engagement is essential for many crypto-native communities. Poker is a great channel for community engagement. Engagement materials like leaderboards, NFTs, and poker games can help the Nouns community bond and have fun together. ## Use Cases and Benefits - **Enhancing Community Engagement:** Wallet Poker offers a platform for the Nouns DAO community to engage through a popular and enjoyable activity. By incorporating poker games, leaderboards, and NFTs, members can interact more frequently and in a fun environment. - **Gamified Experience:** Gamification elements such as native tokens and NFTs provides additional incentives for participation. Members can earn rewards, trade NFTs, and increase their earning rates, making the experience more engaging. - **Fair and Transparent Gameplay:** Unlike traditional poker games, Wallet Poker ensures fairness and transparency through its on-chain technology. This mitigates concerns about manipulation and provides a trustworthy environment for all players. - **Smooth Multichain Payment:** Wallet Poker integrates smooth multichain payment systems, making transactions fast and efficient. This reduces friction and enhances the overall user experience. - **Social Integration:** With integrations to platforms like Twitter and Farcaster, Wallet Poker enhances social engagement by allowing users to share their achievements and activities. This creates a sense of community and fosters more interaction among members. - **Future-Proof and Scalable:** The platform is designed to onboard more games in the future, making it a scalable solution for ongoing community engagement. The interoperable token and NFT system ensures the platform can evolve and grow with the community's needs.

    How it's made

    Challenges we ran into 1. Gameplay management with many edge cases. Multi-threading problem when it comes to user disconnection. 2. Validation and Sync between backend and contract when it comes to token-specific interaction to make sure those are aligned.