1. Applicant & Project Overview
-
Project Name: Urban Mayhem
-
Team / Individual Name(s): Tamar, Valeria and Natachi
-
Links:
-
Github web store: GitHub - natachigram/urban-mayhem-store
-
Game repo: https://github.com/h4sashi/urban-mayhem
-
Website (store): https://urban-mayhem-store.vercel.app/
-
Game App: Urban Mayhem - Google Drive
-
Socials: X https://x.com/urban__mayhem
-
-
100-Word Summary:
Urban Mayhem is a multiplayer battle royale game with a Web3 store where players buy UMP tokens and character skins using $TRUST. Built on Intuition Protocol, every item displays stake-weighted trust scores, players attest on-chain, and accurate raters benefit as their insights gain value. A Unity SDK is in development to let other developers integrate Intuition without backend complexity. Live on Base L2. The goal: a fair, trust-driven gaming economy where reputation is portable and quality is verifiable. -
Project Category
- Other : Gaming / Dev > tool
Elevator pitch:
Urban Mayhem is a multiplayer battle royale powered by Intuition so players can buy tokens and skins with real trust scores, giving the game a clean and scam free economy. With creator monetization and a coming Unity SDK, it becomes a plug and play trust layer for all Web3 games.
-
Origin story:
We grew up playing Mini Militia, a game that brought friends together and created lasting memories. Urban Mayhem was born to capture that same fun, but in a Web3 battle royale where trust, provenance, and transparent item ownership empower both players and creators. -
Current users or early testers: 5
2. What we’re Building
Problem Statement:
Gaming economies lack a universal, verifiable layer for trust and reputation.
For Players:
Players purchasing in-game items have no reliable way to verify quality. Centralized reviews can be manipulated. Influencer endorsements often involve undisclosed sponsorships. Marketplace listings show prices, not verified community sentiment. Players make decisions based on incomplete information.
For Game Developers:
Building trust and reputation systems requires custom backend infrastructure, anti-manipulation mechanisms, and ongoing moderation. For indie studios, this is prohibitively expensive. Most games ship without meaningful trust layers.
For the Ecosystem:
Reputation is siloed. A player’s standing in one game has no bearing on another. Cheaters migrate freely between games. Trusted community members start from zero everywhere. There is no portable reputation primitive for gaming.
Proposed Solution
We are building trust infrastructure for gaming using Intuition Protocol, delivered through three integrated products:
Urban Mayhem Store (Live)
A Web3 marketplace for our mobile game demonstrating Intuition attestations in production. Players see trust scores on items, submit on-chain attestations, and view community ratings before purchasing. Deployed on Base L2.
Urban Mayhem Game (Live)
A mobile battle royale game providing the player base and real-world use case. Backend integration enables trust-influenced mechanics including reputation-weighted loot and matchmaking.
Intuition Unity SDK (In Development)
A plug-and-play package enabling any Unity developer to integrate Intuition without blockchain expertise. Pre-built C# components and UI prefabs reduce integration from weeks to hours. Creates network effects as more games share the same reputation layer.
Technical Implementation:
Game items and players registered as Intuition atoms
Attestations structured as semantic triples
Trust scores computed from stake-weighted attestations
Built on Base L2 for low transaction costs
Stage of Development (Idea, Prototype, MVP, Live, Scaling)
| Component | Stage |
|---|---|
| Urban Mayhem Store | Live — Deployed with wallet connection, attestation submission, trust score display |
| Urban Mayhem Game | Live — Playable Unity mobile game |
| Store ↔ Game Integration | Prototype — Backend APIs implemented, Unity integration in progress |
| Unity SDK | Early Development — Architecture complete, core components in development |
Stack: React, TypeScript, Intuition SDK, wagmi, RainbowKit, Base L2, Unity
- Technical architecture overview:
-
Integrations or dependencies:
Intuition Protocol (Core Dependency)
- Intuition SDK (TypeScript) for creating atoms and submitting attestations
- Intuition API for querying trust scores and attestation data
- Base L2 as the settlement layer
Wallet Infrastructure
- RainbowKit for wallet connection UX
- wagmi for React hooks and contract interactions
- viem for low-level Ethereum operations
Backend Services
- Supabase for database, authentication, and serverless functions
- Vercel for frontend hosting and CDN
Planned Integrations
- Unity SDK package for external game developers
- IPFS for decentralized asset storage (post-MVP)
-
Security considerations
Access Control
- Wallet-based authentication via message signing
- Row-Level Security at database layer
- API key authentication for game client
Attestation Integrity
- On-chain via Intuition Protocol
- Stake-weighted scoring makes manipulation costly
- Rate limiting per user per item
Economic Alignment
- Players stake $TRUST tokens when attesting
- Early accurate attestations gain value as more users stake on the same claim
- Creates incentive to attest honestly rather than spam
3. Team & Execution Ability
-
Team backgrounds:
Tamar Hanzo (Lead Game Developer)
Six years experience in game development and design. Has built multiple indie projects from prototype to launch. Focuses on gameplay, Unity development, and creating stable multiplayer systems.
Valeria (Research Lead)
Researcher with long-term involvement in the Intuition community. Understands how atoms, triples, and the knowledge graph work in practice. Helps shape how the game and upcoming SDK use Intuition features correctly and realistically.
Natachi (Blockchain Deveoper)
Developer with a background in smart contract work and security research. Has experience integrating blockchain features into games and understands how on-chain systems behave in the real world. Handles development direction and all Web3 related work for the project.
-
Execution proof (past products, repos, shipped work):
- Lt. Ahmed (https://play.google.com/store/apps/details?id=com.SixPaths.LtAhmed )
- Jaru’s Journey ( https://play.google.com/store/apps/details?id=com.griotstudios.jarusjourney )
- Escape Protocol ( https://play.google.com/store/apps/details?id=com.LOGICDEV.ESCAPEPROTOCOL )
-
Commitment level: Full time
Team structure and roles:
Tamar Hanzo (Game Developer)
Natachi (Blockchain Developer)
Valeria (Researcher)
Advisors or collaborators: Nexal Gaming (https://nexalgaming.co)
Expected future hiring:
Game designer
UX designer
C# engineer
3D Artist
Prior crypto / AI experience relevant to the project:
Our team has hands-on experience in Web3 gaming, having developed projects like LT Ahmed and BRM Metaverse. We bring deep expertise in blockchain development, Web3 security, and practical applications of machine learning and AI automation.
4. Grant Request & Milestones
Amount Requested
$30,000 USD or 230,000 $TRUST
Budget Breakdown (12-Month Project)
| Category | Amount | Allocation | Purpose |
|---|---|---|---|
| Game Development & Polish | $8,000 | 27% | Complete unfinished features, bug fixes, UX improvements |
| Unity SDK Development | $7,000 | 23% | Core SDK package for external developers |
| Store & Backend Improvements | $4,000 | 13% | Purchase flow, inventory sync, API stability |
| Creator Tools (If Validated) | $3,000 | 10% | Asset submission portal, provenance tracking |
| Marketing & Community | $4,000 | 13% | User acquisition, content, community building |
| Infrastructure | $2,000 | 7% | Hosting, services, testing environments |
| Contingency | $2,000 | 7% | Unexpected costs, scope adjustments |
| Total | $30,000 | 100% |
Timeline & Milestones (12 Months)
Phase 1: Foundation (Months 1-3)
Focus: Complete what’s started, stabilize the product
| Deliverable | Success Criteria |
|---|---|
| Game polish and bug fixes | Zero critical bugs, smooth gameplay loop |
| Store ↔ Game integration complete | Purchases sync within 10 seconds |
| Attestation flow refined | Users can rate items without friction |
| Analytics setup | Track key metrics: users, purchases, attestations |
Budget Allocation: $6,000
Game dev work: $4,000
Store/backend fixes: $2,000
Phase 2: Core Product (Months 4-6)
Focus: Make the product worth using
| Deliverable | Success Criteria |
|---|---|
| Improved game UX | Designer review implemented, player feedback addressed |
| Reputation badges in-game | Players see trust tiers in lobby |
| 50 active players | Organic + early marketing push |
Budget Allocation: $7,000
Game design + dev: $4,000
Marketing (soft launch): $2,000
Infrastructure: $1,000
Phase 3: SDK Development (Months 5-8)
Focus: Package the trust layer for other developers
| Deliverable | Success Criteria |
|---|---|
| SDK core components | IntuitionManager.cs, TrustScoreClient.cs, AttestationClient.cs |
| UI prefabs | Trust badge, rating panel (drag-and-drop) |
| Documentation | Quickstart guide, API reference, example scene |
| Beta testing | 2-3 indie developers successfully integrate |
Budget Allocation: $7,000
Phase 4: Creator Tools — Validation First (Months 7-9)
Focus: Validate demand before building
| Step | Action |
|---|---|
| Month 7 | Interview 10+ potential creators. Do they want this? What features? |
| Month 8 | If validated: Build basic submission portal. If not: Reallocate budget to marketing/SDK. |
| Month 9 | Onboard 3-5 creators, test workflow |
| If Built — Deliverables | Success Criteria |
|---|---|
| Asset submission portal | Creators can upload assets |
| Intuition atom creation | On-chain provenance for each asset |
| Basic earnings tracking | Creators see their sales |
Budget Allocation: $3,000 (conditional)
- If validated: Creator tools dev
- If not validated: Reallocate to marketing or SDK polish
Phase 5: Growth & Polish (Months 9-12)
Focus: User acquisition and product refinement
| Deliverable | Success Criteria |
|---|---|
| Marketing campaign | Content, community, influencer outreach |
| SDK public release | GitHub repo, documentation, Unity forum announcement |
| 200 active players | Sustained weekly active users |
| 10+ attestations per week | Organic community participation |
| Creator marketplace live (if validated) | 5+ creator-submitted items in store |
Budget Allocation: $7,000
- Marketing: $4,000
- Final polish + infrastructure: $2,000
- Contingency: $1,000 (if unused, rolls into marketing)
Summary Timeline
| Months | Phase | Key Outcome |
|---|---|---|
| 1-3 | Foundation | Stable, integrated product |
| 4-6 | Core Product | Playable game with trust mechanics, 100 users |
| 5-8 | SDK Development | Packaged SDK for external devs |
| 7-9 | Creator Validation | Decide build/no-build based on real demand |
| 9-12 | Growth | 500 users, SDK public, creator tools (if validated) |
Success Criteria Summary
| Metric | Target (End of 12 Months) |
|---|---|
| Weekly Active Players | 500+ |
| Total Attestations | 200+ |
| SDK Integrations (Beta) | 3+ external developers |
| Creator Assets (if built) | 10+ items from external creators |
| Critical Bugs | Zero |
Stretch Goals
If ahead of schedule or under budget:
- SDK on Unity Asset Store (broader distribution)
- Cross-game reputation demo (second game using SDK)
- Mobile wallet integration (reduce friction)
Key Dependencies
| Dependency | Risk | Mitigation |
|---|---|---|
| Intuition SDK stability | Low | Pin version, abstraction layer |
| Creator demand | Unknown | Validate before building (Phase 4) |
| Player acquisition | Medium | Budget allocated for marketing, organic via game communities |
Risk Assessment
| Risk | Probability | Impact | Mitigation |
|---|---|---|---|
| Development takes longer than estimated | Medium | Schedule slip | 3-month buffer built in, scope can flex |
| Low player adoption | Medium | Weak metrics | Marketing budget, iterate on feedback |
| Creators don’t want to participate | Medium | Wasted effort | Validate first, conditional budget |
| SDK too complex for indie devs | Low | Low adoption | Beta test with real developers, iterate on feedback |
| Team bandwidth | Medium | Delays | Hire contractors, not just solo founder effort |
How This Compounds Value for Intuition
- Every player rating generates on-chain attestations, growing Intuition’s knowledge graph organically.
- The SDK makes Intuition accessible to Unity developers (50%+ of game market). Each integration multiplies network effects.
- A live game with real players proves Intuition works for gaming, and is usable in Intuition’s marketing and ecosystem materials.
- If creator tools succeed, it validates “on-chain provenance” and “fair creator economics” use cases for Intuition.
- As more games adopt the SDK, player reputation becomes cross-game and which directly advances Intuition’s core thesis.
5. Intuition Ecosystem Alignment
-
Why Intuition (How you use the graph, registry, attestations, InfoFi, MCP, or AI context):
We use Intuition as the trust backbone for item provenance, creator identity, player ratings and cross game reputation. The on chain attestations and knowledge graph allow us to turn subjective signals like quality, credibility and rarity into verifiable, machine readable data. This gives players confidence when buying items, gives creators a provable authorship trail and gives studios a portable reputation layer they can plug into their own games. No traditional database or off chain cache can deliver this level of transparency or composability. -
Which Intuition primitives you use (Atoms, triples, signal, DID / agent registry, knowledge graph, InfoFi, MCP, AI context, etc.):
- Atoms for player, creator and item entities
- Triples for ratings, authorship and reputation links
- Knowledge Graph for reputation traversal and data discovery
- InfoFi and bonding semantics for stake weighted trust signals
- TRUST for purchases and attestation staking
- Intuition SDK and API for writing and querying attestations
-
Why it must be built on Intuition
- On chain atoms and triples create verifiable provenance for items and creator claims. This is difficult to replicate with off chain only systems.
- Bonding and stake weighted signals reduce Sybil and spam, which is critical for rating systems and creator reviews.
- The knowledge graph makes reputation portable across multiple games, which is a core feature of our SDK vision.
- Intuition’s SDK and query layer reduce integration time. Rebuilding our own verification and reputation infra would be slower, more expensive and less secure.
-
Data structure plan (atoms, triples, signal, schemas):
| Type | Schema |
|---|---|
| Item Atom | urban-mayhem:item:<uuid> — metadata: name, rarity, image, price |
| Player Atom | urban-mayhem:player:<wallet> — wallet address |
| Creator Atom | urban-mayhem:creator:<id> — name, wallet |
| Attestation Triple | <player_atom> → rated_as → <rating> on <item_atom> |
- How do you plan to integrate TRUST, the native currency of Intuition Network:
- Attestation staking uses $TRUST per Intuition’s protocol mechanics
- Accept $TRUST for in-store purchases
- New schemas, patterns, or agent types you might introduce
- MarketplaceAgent for creating item atoms and publishing listing events
- CreatorAgent for DID backed authorship proofs
- GameServerAgent for verified match data and in game event attestations
- How this increases network activity or knowledge density
- Every item listing generates a new atom
- Every rating or review generates a triple
- Every creator verification writes authorship proofs
- The Unity SDK encourages other games to produce attestations, multiplying graph activity beyond our own title
- Long-term contribution to the ecosystem (12–24 months):
- Urban Mayhem becomes the reference case for gaming integrations on Intuition, improving onboarding for future studios
- Games using our SDK produce thousands of attestations each, increasing graph density and reputation reuse
- Player trust and creator credibility become portable across games, demonstrating Intuition’s cross app value
- Interactive gameplay generates high frequency micro events that contribute continuously to the graph
- If creator tools succeed, our schemas for asset provenance and revenue tracking become reusable for other Web3 games and marketplaces
- TRUST staking on quality and reputation creates recurring network activity instead of one time usage
6. Sustainability & Long-Term Vision
-
Long-term vision (6–24 months):
Months 6 to 12
- Fully stable game loop with 200 to 500 weekly active players driven by community events and referral incentives.
- First public release of the Unity SDK, with 2 to 3 indie studios integrating available features.
- Creator onboarding tools released only if early artists show enough demand, helping them publish and verify items directly.
- 2,000 to 3,500 Intuition backed attestations generated through players, creators, and game events.
Months 12 to 24
-
5 to 10 live games integrating the SDK.
-
Demonstrated cross game reputation, where verified creators or trusted players maintain portable reputation across multiple game titles.
-
$10K to $30K GMV flowing through the marketplace from verified assets and creator sales.
-
Operational sustainability where marketplace revenue and in game purchases cover core infrastructure costs including servers and Intuition attestations.
-
Post-grant sustainability plan :
Game Revenue- In game cosmetics and items created by the team.
- 100 percent of those sales go to us and stay inside the Urban Mayhem ecosystem.
Creator Marketplace
- Creators earn 70 percent.
- Platform takes a 30 percent cut, which funds infrastructure and attestation costs.
SDK Licensing (Later Stage)
- Free tier for early teams and solo devs to reduce friction.
- $49 to $99 monthly for studios that want advanced features such as analytics, cross game reputation syncing, and premium verification tools.
-
Business or revenue model:
Our revenue model is built around three sustainable streams tied directly to player activity, creator participation and future SDK adoption.
First, players purchase in game currency through the web store which gives us an immediate and predictable revenue base. Second, we sell team created skins and items which provide high margin revenue since all sales from these assets go directly to us. Third, as creators join the marketplace, they earn 70 percent from their item sales while the platform takes a 30 percent cut that covers moderation, storage and verification through Intuition attestations. As the ecosystem grows, the Unity SDK becomes a long term revenue extension. It launches with a free tier for indie teams and later introduces a paid tier between 49 and 99 dollars per month for studios.
This model keeps us sustainable in the short term while building a long term ecosystem where player activity, creator output and developer adoption naturally reinforce each other.
-
Go-to-market or distribution strategy
Players
Target Web3 native gamers through gaming Discords and Twitter/X micro influencers using gameplay clips and early access access codes. Introduce a referral loop where players earn verified cosmetics and small marketplace credits for bringing friends. Partner with Web3 communities for a trust scored tournament that rewards store credits and exclusive verified items, which drives early marketplace engagement.
Developers
Publish an early access GitHub repo with documentation for the upcoming SDK and a lightweight Unity demo showing how items use Intuition attestations. Stay active in Unity forums to answer technical questions and become visible. Sponsor a small indie jam where the reward is SDK integration support, marketplace visibility, and revenue share boosts for winning teams.
Creators
Onboard 5 to 10 Unity compatible artists into an invite only beta, giving them 70 percent revenue share, boosted marketplace visibility, and authorship verification through Intuition backed attestations. Add a launch incentive where early creators receive marketplace fee rebates on their first set of items, helping them maximize earnings.
Partnerships
Collaborate with two indie studios that want verified item economies through simple co marketing integrations. Run a community load test with Web3 gaming communities using store credit incentives to drive participation. Plan a future listing on the Unity Asset Store once the SDK ships and stabilizes, turning the SDK into a discovery funnel for both developers and creators.
7. Additional Materials
Demo link, repo, or screenshots:
Game UI:
-
Contact email + wallet address:
Email: natachigram@gmail.com
Wallet Address: 0x522fEb1112F33b68776FD5A22b8025fFB295F5a0
-
video walkthrough: Urban Mayhem Demo Video - Google Drive
8. Applicant Attestation
I confirm that all information submitted is accurate and that I intend to deliver the listed milestones.
Name: Valeria from URBAN MAYHEM
Wallet Address:0x522fEb1112F33b68776FD5A22b8025fFB295F5a0
Date: 5-12-2025








