# Hsuite Fan Launchpad System Specification _Source: attached DOCX from Telegram, saved locally._ Hsuite Fan Launchpad Full System Specification for Match Pool NFT Prediction Campaign Prepared for Hsuite Wallet and Smart Node implementation Important compliance note: This specification describes a token-funded match pool where users buy prediction NFTs and winning NFT holders receive distributions from the match account. This may be treated as gambling, wagering, gaming, sweepstakes, or a regulated prediction-market product in many jurisdictions. Legal review, jurisdiction controls, age restrictions, and licensing assessment are required before any public launch. 1. Executive Summary The Hsuite Fan Launchpad is a World Cup match prediction system using Hsuite Wallet, match-specific NFT collections, match pool accounts, and Smart Node governed execution. For each match, the match account mints NFTs for both teams. Users connect their wallet, choose the match, buy the NFT representing the team they support, and pay x HSUITE into the match account. After the match result is confirmed, the system deducts a configurable platform fee and distributes the remaining pool to eligible NFT holders based on the result. The four core modules are: Match setup and minting of both team NFTs by the match account Wallet connection using WalletConnect or Hsuite Native Protocol Purchasing the team NFT using HSUITE Snapshot and distribution to platform operator and eligible NFT holders 2. System Objectives Drive Hsuite Wallet adoption through a simple fan engagement product. Showcase Hsuite Smart Nodes as a governed execution layer for rules, funds, NFT issuance, snapshots, and distribution. Create a reusable launchpad pattern for sports, esports, communities, creator campaigns, and loyalty pools. Keep the product simple: pick a team, buy the NFT, pool closes before kickoff, results determine distribution. Ensure transparent auditability with transaction records, pool balances, snapshots, and distribution proofs. 3. High-Level System Flow 1. User connects wallet using WalletConnect or Hsuite Native Protocol.2. User selects a game.3. User sees NFTs for both teams.4. User selects which team to support by buying that team NFT for x HSUITE.5. User signs the transaction. The NFT is transferred to the user account and HSUITE is transferred to the match account.6. The match account collects all NFT sales for that match.7. Thirty minutes before kickoff, NFT sales stop.8. After the match, the result is either Team A wins, Team B wins, or draw.9. If there is a winner, the match account deducts the configured platform fee and transfers it to the platform operator account. The balance is divided equally between eligible holders of the winning team NFT.10. If the match ends in a draw, the match account deducts the configured platform fee and distributes the balance equally to eligible holders of both team NFTs.11. Unsold NFTs still held by the match account are excluded from any distribution.12. A snapshot is taken 30 minutes after the match for holder determination, unless the final policy is changed to pre-kickoff snapshot for stronger anti-manipulation control. 4. Recommended Architecture Frontend Web App -> Wallet Connection Layer -> Campaign API -> Smart Node Policy Engine -> Match Account / NFT Treasury -> HSUITE Pool Account -> Result Oracle / Admin Confirmation -> Snapshot Engine -> Distribution Engine -> User Wallets + Platform Operator Wallet Component Purpose Frontend Web App Allows users to connect wallets, browse matches, buy team NFTs, and view rewards. Wallet Connection Layer Supports WalletConnect and Hsuite Native Protocol. Campaign API Maintains match configuration, sale status, NFT metadata, pool state, and user activity. Smart Node Policy Engine Enforces rules: sale windows, fees, purchase validation, snapshot rules, and distribution approvals. Match Account Mints and holds unsold NFTs, receives HSUITE from NFT purchases, and distributes funds after result. Result Oracle Receives official match results and triggers settlement flow. Snapshot Engine Determines eligible NFT holders, excluding unsold NFTs in the match account. Distribution Engine Calculates platform fee and holder payouts, then executes airdrops. Audit / Proof Layer Stores transaction IDs, snapshot hashes, and distribution proofs. 5. Module 1 - Match Setup and NFT Minting This module allows the operator or authorized Smart Node to create a match, create or assign a match account, mint NFTs for both teams, define NFT price in HSUITE, configure platform fee, and set sale cutoff time. Area Specification Inputs Match ID, team names, kickoff time, NFT price, platform fee, operator account, match account, NFT supply for each team, artwork, metadata. Outputs Match record, NFT token IDs/serials, match pool account, sale schedule, metadata URIs, configuration proof. Rules Only authorized admin or Smart Node may create matches. Each match has a dedicated match account. The platform fee is configurable per match and inherits the default fee if not specified. NFT sales close 30 minutes before kickoff by default. Unsold NFTs remain in the match account and are excluded from payout calculations. 6. Module 2 - Wallet Connection This module handles user authentication and wallet session creation using WalletConnect or Hsuite Native Protocol. Area Specification Supported Methods WalletConnect and Hsuite Native Protocol. Data Captured Wallet address/account ID, wallet provider, session ID, connection timestamp, chain/network, consent status. Rules No custodial private keys are stored by the platform. The user must sign transactions from their wallet. Wallet sessions expire based on configured policy. The system should support reconnect and session revocation. 7. Module 3 - Purchasing Team NFT This module allows a connected user to buy a team NFT for a selected match using HSUITE. Area Specification Purchase Flow User selects match, chooses team NFT, reviews price and pool rules, signs transaction, receives NFT, and transfers HSUITE to match account. Atomicity Requirement The NFT transfer and HSUITE transfer should be executed atomically where possible. If atomic execution is not possible, Smart Node compensation logic must detect partial failure and reverse or reconcile. Rules Sales must be open. User must have sufficient HSUITE. The NFT must be available. The match account must receive payment. The user account must receive the NFT. All purchases are recorded with transaction IDs. 8. Module 4 - Snapshot and Distribution This module determines eligible NFT holders, deducts platform fees, and distributes the match account balance after result confirmation. Area Specification Snapshot Policy User requested snapshot 30 minutes after the match. For stronger anti-manipulation protection, the recommended eligibility snapshot is at sale close or kickoff. If using post-match snapshot, NFT transfers should be frozen from sale close until distribution completion. Winner Scenario If Team A or Team B wins, only eligible holders of the winning team NFT receive the distributable pool. Unsold winning NFTs held by the match account are excluded. Draw Scenario If match ends in a draw, eligible holders of both team NFTs receive the distributable pool equally. Unsold NFTs held by the match account are excluded. Platform Fee Default 10%, configurable per match. Fee is deducted first and transferred to the platform operator account. 9. Core Data Model Match- matchId- teamAId- teamBId- kickoffTime- saleCloseTime- matchEndTime- resultStatus- result- nftPriceHsuite- platformFeePercent- matchAccountId- platformOperatorAccountId- teamANftTokenId- teamBNftTokenId- statusPurchase- purchaseId- matchId- walletAccountId- selectedTeamId- nftTokenId- nftSerial- hsuiteAmount- paymentTxId- nftTransferTxId- purchasedAt- statusSnapshotRecord- snapshotId- matchId- nftTokenId- nftSerial- holderAccountId- selectedTeamId- eligible- exclusionReason- snapshotTimeDistribution- distributionId- matchId- poolBalance- platformFeePercent- platformFeeAmount- distributableAmount- eligibleNftCount- rewardPerNft- status- distributionTxBatchId 10. Match Status Lifecycle DRAFT -> CONFIGURED -> NFT_MINTED -> SALE_OPEN -> SALE_CLOSED -> MATCH_IN_PROGRESS -> RESULT_PENDING -> RESULT_CONFIRMED -> SNAPSHOT_TAKEN -> DISTRIBUTION_READY -> DISTRIBUTED -> CLOSED Status Meaning DRAFT Match has been created but not finalized. CONFIGURED Match details, fee, price, and accounts have been configured. NFT_MINTED Team NFTs have been minted by the match account. SALE_OPEN Users can buy NFTs. SALE_CLOSED Sales closed 30 minutes before kickoff. MATCH_IN_PROGRESS Match is underway. RESULT_PENDING Match completed; waiting for verified result. RESULT_CONFIRMED Winner or draw confirmed. SNAPSHOT_TAKEN Eligible holders identified. DISTRIBUTION_READY Payout calculations completed and ready for execution. DISTRIBUTED Platform fee and holder payouts completed. CLOSED Match settlement finalized. 11. Settlement Formulas platformFeeAmount = matchPoolBalance * platformFeePercent / 100distributableAmount = matchPoolBalance - platformFeeAmountif result == TEAM_A_WIN: eligibleNftCount = count(Team A NFTs held by users, excluding match account)if result == TEAM_B_WIN: eligibleNftCount = count(Team B NFTs held by users, excluding match account)if result == DRAW: eligibleNftCount = count(Team A + Team B NFTs held by users, excluding match account)rewardPerNft = distributableAmount / eligibleNftCount 12. Unsold NFT Exclusion Rule Unsold NFTs remain in the match account. They must never receive rewards. During snapshot, any NFT whose holder is the match account, treasury account, platform operator account, or other excluded system account must be marked ineligible. if holderAccountId == matchAccountId: eligible = false exclusionReason = "UNSOLD_NFT_IN_MATCH_ACCOUNT" 13. Suggested API Endpoints Endpoint Method Purpose /matches POST Create a new match. /matches/{id}/mint POST Mint both team NFT supplies. /matches GET List matches. /matches/{id} GET Get match details. /wallet/session POST Create wallet connection session. /matches/{id}/purchase-intent POST Create purchase transaction payload. /matches/{id}/close-sale POST Close NFT sale manually or by scheduler. /matches/{id}/result POST Submit or confirm match result. /matches/{id}/snapshot POST Run eligibility snapshot. /matches/{id}/distribution/preview GET Preview fee and holder payout calculations. /matches/{id}/distribution/execute POST Execute platform fee and holder distributions. 14. Smart Node Policy Rules match_pool_policy: default_platform_fee_percent: 10 platform_fee_configurable_per_match: true nft_sale_close_minutes_before_kickoff: 30 payment_token: HSUITE allowed_wallet_methods: - walletconnect - hsuite_native_protocol purchase_requires_wallet_signature: true purchase_requires_payment_to_match_account: true purchase_requires_nft_transfer_to_user: true unsold_nfts_excluded_from_distribution: true platform_fee_paid_first: true distribution_mode: equal_split draw_distribution: both_team_nft_holders winner_distribution: winning_team_nft_holders snapshot_time_requested: match_end_plus_30_minutes recommended_snapshot_time: sale_close_time freeze_nft_transfers_after_sale_close: true require_result_confirmation: true require_distribution_audit_log: true 15. Transaction Design 15.1 Purchase Transaction User signs:- Transfer x HSUITE from user wallet to match account- Transfer selected team NFT from match account to user walletRequired checks:- Sale is open- Match is not closed- Selected team NFT is available- User has sufficient HSUITE- Transaction memo includes matchId and selectedTeamId 15.2 Settlement Transaction Match account executes:1. Transfer platformFeeAmount to platformOperatorAccount2. Transfer rewardPerNft to each eligible holder3. Record distribution transaction IDs4. Mark match as DISTRIBUTED 16. Edge Cases and Failure Handling Case Handling Match cancelled Refund users or void match according to configured policy. Platform fee should normally not be taken. Match postponed Extend sale window only if no kickoff occurred and policy allows. Result disputed Pause settlement until final result confirmed. No winning NFT holders Define rule: carry pool forward, refund all, or send to campaign treasury. Recommended: refund minus no fee or carry forward based on terms. Zero eligible holders after exclusion Do not distribute. Escalate to admin review. Transaction failure during batch payout Retry failed payouts and track per-wallet status. NFT transfer after sale close Recommended: freeze transfers or snapshot at sale close to prevent manipulation. User holds multiple NFTs Pay per eligible NFT unless campaign rules cap payout per wallet. Insufficient pool balance Pause distribution and reconcile match account balance with purchase records. 17. Security Requirements All user purchases must be wallet-signed. Backend must never store user private keys. Admin actions require role-based access control and multisig for sensitive operations. Match account keys should be controlled by Smart Node/TSS or multisig policy. Sale closure must be enforced by Smart Node and backend scheduler. Distribution preview must be generated before execution. All snapshots and distributions must be immutable after confirmation. Audit logs must record who triggered setup, result confirmation, snapshot, and distribution. 18. Compliance and Risk Notes Because users pay HSUITE and receive pooled rewards based on match outcomes, this may be regulated. Do not launch publicly without legal review in target jurisdictions. Avoid marketing language such as bet, wager, odds, sportsbook, casino, or stake. Use terms such as fan pool, team NFT, supporter NFT, match pool, rewards, and distribution. Consider age gating, geo-blocking, campaign terms, responsible participation rules, and licensing analysis. 19. MVP Build Scope MVP Feature Included Admin match setup Yes Team NFT minting by match account Yes WalletConnect login Yes Hsuite Native Protocol login Yes Team NFT purchase with HSUITE Yes Sale closure 30 minutes before kickoff Yes Result confirmation Yes Snapshot engine Yes Unsold NFT exclusion Yes Configurable platform fee Yes Equal split distribution Yes Platform operator fee transfer Yes Distribution dashboard Yes Advanced leaderboards Phase 2 Referral campaign Phase 2 NFT transfer marketplace Phase 2 or later 20. Final Recommended User-Facing Positioning The product should be positioned as a fan participation launchpad: Pick your side. Own your team NFT. If your team wins, the match pool is distributed to eligible holders. This is simple, viral, and strongly demonstrates the Hsuite Wallet as a programmable participation wallet and Smart Nodes as the governed execution layer behind digital engagement.