minusROAD MAP

Stellar Integration Roadmap

Executive Summary

Hero2Quest is a blockchain-based gaming platform that combines NFT heroes with quest-driven gameplay. Our smart contracts are production-ready, with comprehensive test coverage and security validation.

Key Points

  • GameRoot: Stores contract/WASM hashes and deploys Account/QuestManager contracts. Not a central game registry — used only for deterministic contract deployment.

  • InventoryDetails: System contract storing hero characteristics.

  • QuestIndex: System contract for quest discovery by tags.

  • Account: One per player, owned by the player’s blockchain wallet address.

  • QuestManager: Created by Account; multiple instances allowed.

  • Quest: Deployed by QuestManager (not by GameRoot).

  • QuestClient: Combines HeroNFT + Quest into a single game session.


Planned Blockchain Integration

Technology Stack

Layer
Technology
Purpose

Tokens

On-chain fungible token standard

Assets: H2Q (game currency), QST (access/utility token)

NFT

On-chain NFT standard

HeroNFT — unique game characters

Wallets

Standard wallet custody

Users hold game assets in their own wallets

API / Contracts

Blockchain RPC + smart contracts (Rust)

Read state, submit transactions; game logic, quest mechanics, rewards

Events / Indexing / Proof

Contract events + RPC event streaming

Proof logging; index tx_hash/contract_id/asset_id; public verification links


How We Integrate with Blockchain

Smart Contracts (Rust)

  • Production-ready contracts for core game mechanics

  • Native token integration via standard fungible token interfaces

  • Deterministic contract deployment with upgrade paths

  • HeroNFT compatible with widely used NFT standards

On-chain Tokens & Assets

  • H2Q Token: fixed-supply game currency

  • QST Token: access/utility token

  • Hero NFTs: unique characters represented as NFTs

On-chain Event System

  • Contract events for all game actions

  • Provable quest completions via Proof Index

  • Transparent reward distribution with verification URLs

Frontend Integration

  • Real-time state sync via blockchain RPC

  • Proof capsules with on-chain verification links

  • Wallet integration via common wallet connectors/providers (Deliverable 3)


Roadmap: 3 Deliverables (3 Months)

Deliverable 1 — Testnet Deploy + Frontend

Duration: 4 weeks Focus: Deploy contracts to a public testnet + frontend migration to blockchain SDK + transparent liquidity UI

What’s included:

  • Testnet Deploy: Deploy production-ready contracts (9 contracts, 350+ tests, ~52M fuzz iterations) to testnet. Verify full gameplay loop: craft → quest → reward.

  • Frontend Migration: Migrate React frontend to the blockchain SDK.

  • Transparent Liquidity UI: UI for tracking H2Q purchase transactions and fund flow + basic metrics.

How to measure completion:

  • All smart contracts deployed to testnet

  • Full gameplay cycle works: craft hero → stake in quest → claim reward

  • All contract events emitted correctly

  • Verifiable via tx_hash in a public block explorer

  • UI integrations with the blockchain SDK are up to date

  • Transaction traceability UI is functional

Tech stack: contract CLI/toolchain, public testnet, blockchain SDK, React Estimated completion: Week 4


Deliverable 2 — Provability Infrastructure

Duration: 4 weeks Focus: Proof Index + Proof URL + Collective Quests

What’s included:

  • Proof Index: Indexer service (event stream → Postgres) with checkpoints for contract events.

  • Proof URL: Public verification page by tx_hash / hero_id → “on-chain proof capsule”.

  • Collective Quests: Extended mechanics — group quests, player alliances.

How to measure completion:

  • Indexer runs continuously

  • Proof URL shows verifiable data: network, contract, event, parameters

  • Collective quest mechanics work on-chain

Tech stack: blockchain RPC event APIs, Postgres, smart contracts, blockchain SDK, React Estimated completion: Week 8


Deliverable 3 — Token Launch + Social + Mainnet

Duration: 4 weeks Focus: H2Q/QST tokens + provability layer on X + mainnet deploy

What’s included:

  • Token Infrastructure: Issue H2Q (fixed supply) and QST (access token) on mainnet using a standard fungible token model; configure wallet holding/permission flows as required by the chosen chain.

  • Wallet Integration: Production wallet connectors in the frontend.

  • Provability Layer (X): Automated posts on X/Twitter with proof capsules for achievements.

  • Mainnet Deploy: Deploy to mainnet + monitoring.

How to measure completion:

  • H2Q and QST issued on mainnet

  • Token holding/enablement flow works in frontend

  • Frontend connects to user wallets

  • X/Twitter posts contain proof links

  • Mainnet contracts process game transactions stably

Tech stack: fungible token standard, wallet connectors, X API, smart contracts, blockchain SDK

Estimated completion: Week 16

Last updated