GEXI Whitepaper v1.0

Status: Sui Testnet · Mainnet not launched Updated: November 5, 2026 Scope: Product, business model, proposed tokenomics and launch readiness

Table of Contents

1. Executive summary
2. Product and evidence
3. Market and growth
4. Business model and revenue sustainability
5. Token utility and rights
6. Tokenomics
7. Funding and sale readiness
8. Rewards and treasury
9. Architecture and security
10. Roadmap and team
11. Risks and legal
12. Technical reference and sources

1. Overview

GEXI is a mobile-first casual gaming platform on Sui. It brings short browser games, social play and creator publishing into one account. Everyday games are free to enter. Google sign-in provides an embedded wallet for supported features, without a separate wallet extension.

For players, the aim is easy discovery and repeat play alongside creators they follow. Every signed-in player can also create games without a separate creator role or application. It is a shared publishing platform with identity, scores, social features and payment infrastructure. Gexi Ai adds an optional way to create and revise games using service credits.

GEXI is a commercial platform. Its proposed revenue model combines competition fees, Ticket sales and paid AI services to fund operations and development. The proposed mainnet initial supply is 100,000,000 GEXI. Business revenue does not give token holders a right to company profits.

Product and launch status

This is a dated description, not a live operational feed. The sections below distinguish the testnet product from proposed economics and launch requirements.

2. Product & Evidence

Player experience

Players discover GEXI Originals and reviewed community-created games, build scores and XP, and connect through Following, Followers, chat, challenges and rankings. Following is a one-way connection; mutual follows support interactions that previously required friendship. Live Events, Duel and Brawl provide optional competition with mode-specific entry and settlement rules. Direct-message privacy is user-controlled.

Google sign-in connects the account to a Sui zkLogin wallet. Eligible new testnet wallets can receive a guarded SUI faucet bootstrap for gas. Frequent gameplay and social activity run in application services; supported value-sensitive actions are settled and checked on Sui.

Creator platform

Every signed-in GEXI account can create games automatically. No creator application, separate creator role, or approval is required to open the Creator Portal. Users can upload HTML5 games with the GEXI Game SDK or use Gexi Ai to generate and revise drafts, test on mobile and desktop, and prepare cover artwork. Listing details, versions and analytics share the same workspace. Profiles display published games when available, or a brief message if the account has not published any games.

Every game submission and update requires compatibility checks and admin review. Published games run in an isolated environment. The SDK connects readiness, run start, scores, checkpoints, game-over and replay to platform sessions. Submission requirements appear in the technical reference.

Each eligible account receives 50 Sparks once as its initial AI service-credit grant; this replaces the former 100-Spark welcome amount for new grants. Existing granted balances are not reduced or granted again because of this change. Sparks are reserved and reconciled in a service ledger. Tasks that may award additional Sparks are planned but not yet available. Free credits are not customer revenue.

Evidence and measurement

The product is available on testnet, but this paper does not publish realized retention, active-player, revenue or profitability figures. Feature availability is not proof of commercial demand.

The measurement priorities are first-play activation, D7/D30 retention, valid match completion, creator participation, AI draft success and reconciled payments. Reports need sample sizes, observation windows, test-account exclusions and clear data-quality limits. Definitions appear in section 12; testnet participation must remain separate from real-money spending.

3. Market & Growth

GEXI targets players who enjoy short mobile-friendly browser games and creators who want to publish without building their own account, social and payment systems.

The platform competes for attention with browser arcades, creator platforms and AI game-building tools. Its intended distinction is the combination of quick play, social interaction, reviewed publishing and shared Sui infrastructure. Whether that combination improves retention or creator earnings remains to be demonstrated.

These are distribution plans, not announced partnerships or proven acquisition channels. This version does not publish customer-acquisition cost, lifetime value or market-share estimates.

4. Business Model & Revenue Sustainability

GEXI is designed to earn operating revenue and build a sustainable gaming business. The proposed policy directs eligible product receipts to the GEXI Infrastructure Treasury, an operator-controlled destination for operating funds.

Revenue channels

These are proposed revenue routes, not a statement of current treasury income. Verified deployment, configuration, service integration and transaction records are required to report a route as active.

Competitive settlement

An eligible winner-settled Duel/Brawl pool uses a 10% gross commission: 2% for creators and 8% for the infrastructure treasury. The remaining 90% goes to the winning side.

The creator share is calculated from the gross pool, not from the winner's payout. The treasury share is part of the 10% commission, not an extra fee. Refunds and cancellations do not use this winner split; integer rounding can apply. This example is arithmetic, not observed revenue or a forecast.

Costs and sustainability

Revenue is intended to fund AI inference and artwork, game verification, hosting, storage, chain services, moderation, support, engineering, security and legal work. 100% of eligible Store proceeds means gross receipts before costs and taxes, not a 100% profit margin.

The business aims to cover service delivery and operating expenses through repeat product use. Paid AI pricing must account for generation, retries, verification, free grants and support. Sustainable operation depends on retained players and creators, reliable services and positive economics; no sales volume, margin or operating lifetime is established here.

Accounting must separate customer payments, delivered services, earned revenue and spendable cash. Player stakes, creator earnings, refundable balances and treasury reserve releases are not company revenue. Converting GEXI receipts into operating cash also involves token-price, liquidity and conversion risk.

5. Token Utility & Rights

Three different units

Tickets can be purchased or distributed through eligible Tasks, progression and campaigns. Store pack prices and sizes come from the canonical on-chain Store configuration. Paid GEXI-funded Sparks checkout remains disabled.

Why use GEXI?

The intended role is one shared utility asset across games and supported platform services, rather than a separate token for every title. Demand would depend on players and creators choosing those services. Rewards, creator payouts and treasury conversions can also return tokens to the market; transaction volume alone does not establish sustained purchase demand or value appreciation.

Holding GEXI does not confer company equity, a claim on fees or treasury income, or token-holder voting rights under this whitepaper. GEXI is currently operator-governed. No staking yield, price floor, guaranteed buyback, fixed earnings per play or token return is promised.

6. Tokenomics

The proposed mainnet token has 9 decimals and an initial supply of 100,000,000 GEXI. The table is a launch policy proposal, not an executed distribution or enforceable vesting arrangement.

Allocation

The shares total 100%. At the proposed token generation event (TGE), 13,400,000 GEXI, or 13.4% of initial supply, becomes eligible for controlled use. This includes liquidity and operational budgets; it is not a forecast of circulating supply.

Player and creator allocations have no cliff: 2M and 1M GEXI respectively are available for launch budgets. The remaining 25M and 17M become eligible in equal monthly amounts over 60 and 48 months. Eligibility does not require immediate spending or distribution.

Proposed cumulative vesting eligibility

Remaining allocations vest in equal monthly amounts after any stated cliff, with no bulk cliff-end release. A six-month cliff therefore starts monthly releases in month 7; the team allocation starts in month 13. Exact launch dates and enforceable arrangements still require publication.

These figures measure maximum cumulative release eligibility. Actual circulation depends on distribution, claims, liquidity deployment and treasury movements. Incentive spending is intended to follow demonstrated product activity rather than automatically spending every available tranche.

Supply and custody

The proposed token source creates the initial supply for the publication signer and removes ordinary post-initialization mint authority. It does not enforce allocation or vesting. Launch arrangements require separate custody, beneficiary assignments and verifiable locks, plus token registration and immutable token-package status. These are prerequisites, not proof of completed mainnet deployment.

Beneficiary wallets, locked balances, releases, operating controls and circulating-supply methodology require publication and reconciliation before mainnet distribution. A balance controlled by a signer is not proof of a time lock. Earned infrastructure revenue is separate from the strategic reserve allocation and does not create additional tokens.

7. Funding & Sale Readiness

The 12% Strategic Sale / Backers allocation reserves capacity for a potential financing arrangement. This whitepaper does not announce a sale, set a token price or valuation, or create a purchase right.

Any sale requires separate terms identifying the responsible entity, eligible participants, price, allocation, vesting, delivery conditions, use of funds, cancellation and applicable refund rights. Unsold-allocation treatment and any differences between investor groups also require disclosure. Company investment and token purchase are different instruments.

No quantified fundraising target, use-of-proceeds budget or cash runway is published here. The 10% liquidity allocation identifies GEXI tokens, not the matching SUI, stablecoin or other assets needed for a market. Liquidity funding, custody and withdrawal controls remain launch disclosures to complete.

8. Rewards & Treasury

Player rewards

Player rewards and Event commitments need explicit funding in dedicated budgets and vaults. The launch design calls for a pre-funded Rewards vault and a separately governed near-term top-up reserve. A token becoming eligible for use is not the same as a funded reward claim.

Ticket Store receipts are designated for the infrastructure treasury under the proposed policy. Event rewards therefore cannot be treated as automatically backed by new Ticket sales. Free Tickets, unused Tickets and accrued claims also matter when calculating obligations. Testnet reward settings appear in section 12; they are not fixed mainnet promises.

Creator payments

Under the current portal accounting model, eligible third-party Event activity allocates 20% of gross Event value to the creator. Eligible winner-settled Duel/Brawl activity allocates 2% of the gross pool, as described in section 4.

Confirmed creator balances are prepared for monthly payouts with a 100 GEXI minimum; smaller balances carry forward. Earned revenue shares are separate from grants funded by the 18% Creator Ecosystem allocation. These are configurable platform terms and may evolve before mainnet.

Treasury controls and operating funding

Operating receipts, strategic token reserves, player stakes, reward liabilities, creator balances and refundable payments must remain separately accounted for. A treasury transfer does not by itself prove profit or eliminate a customer obligation.

Each eligible Store withdrawal needs verified receipts, correct service delivery and a reserve calculation that protects outstanding obligations. Rewards, refunds and creator entitlements cannot be treated as unrestricted company funds. Source-specific records and reconciliation remain necessary even when revenue reaches the same treasury wallet.

This version does not publish an operating runway or a reward stress model. Mainnet readiness requires budgets for reward demand, unused entitlements, AI costs, token-price changes and liquidity constraints. Sustainable operations cannot be inferred from token reserves alone.

9. Architecture & Security

GEXI uses application services for frequent interactions and Sui settlement for supported value-sensitive actions. It is a hybrid platform, not a fully decentralized game or a trustless scoring system.

Controls and trust boundaries

• Wallet authorization: Google OIDC and Sui zkLogin support embedded access. Backend services handle wallet/proof requests; the active client retains the ephemeral signing context for user-authorized transactions.
• Gameplay integrity: Server-issued sessions, checkpoints, timing, score limits and replay checks support validation. An on-chain payment or checkpoint hash is not proof of human play or the absence of cheating.
• Settlement: PIN checks, expiry- and nonce-bound authorization, configured package verification and reconciliation protect sensitive flows. Match binding, disconnects, deadlines and duplicate-settlement prevention are critical to payouts and refunds.
• Creator isolation: Reviewed builds run in a sandboxed GEXI-controlled runtime without direct access to platform authentication or session DOM. AI-generated code and artwork remain untrusted inputs until checks and review.
• Abuse controls: Referral qualification, hashed network/client signals, risk scoring and manual review help limit duplicate accounts and reward abuse. They can still miss abuse or flag legitimate users.

Backend validation and verifier signing keys remain critical dependencies. Administrators operate configuration and applicable game, budget and campaign rules within technical controls. Google, wallet/proof providers, hosting, AI services and chain availability add operational dependencies. Recovery, custody and upgrade authority need separate verification; a published contract alone does not establish safe operations.

Independent assurance

The public GEXI Contracts repository provides Move source for Store, Rewards, Duel and Brawl. It does not include or certify the full application, verifier or signing infrastructure.

A professional independent smart contract audit is planned for mainnet readiness. Public source, successful tests and source verification are not an independent audit or a guarantee of safety. This paper does not present a completed audit report or claim an active bug bounty program or production insurance.

10. Roadmap & Team

Roadmap

No launch dates are promised. Mainnet requires verified contract provenance, completed review and remediation, sound custody, reconciled pools and ledgers, legal review and a controlled transition. Detailed cutover requirements are in section 12.

Team

The responsible operating entity, jurisdiction and treasury arrangements will be finalized and disclosed before any presale or broader public distribution, subject to applicable requirements.

11. Risks & Legal

Principal risks

Describing a feature as skill-based or a token as utility does not establish permission to offer it in every jurisdiction. Testnet operation is not approval for a real-value launch.

Testnet participation and transition

Tasks can grant Tickets, SUI or GEXI. Eligible testnet activities can also earn Activity Points through gameplay, referrals, selected social tasks, bug reports and rankings, subject to qualification and anti-abuse controls. No fixed conversion into mainnet GEXI is promised.

Gameplay progress, balances, Activity Points, reward claims and other testnet economic state are expected to reset before mainnet. Eligible identity, profiles, wallets, follow relationships, chat and creator content are intended to remain, subject to wallet continuity and migration checks.

Policy changes and rights

Allocation, vesting implementation, product parameters, eligibility and launch timing remain subject to technical, market and legal review before broader distribution. Significant changes affecting fees, distribution, rewards or security assumptions require public disclosure, before taking effect where practicable. This paper does not establish token-holder governance or replace applicable agreements and law.

See the Terms of Service and Privacy Policy. This document is informational, not an offer of securities or tokens or investment, legal or financial advice. Token value, liquidity, returns and long-term profitability are not guaranteed.

12. Technical Reference & Sources

Current testnet parameters

These settings describe the testnet product and can change. They are not mainnet pricing or reward commitments.

Implementation reference

Measurement definitions

These are reporting definitions, not published results. Use consistent event rules and time zones, exclude ineligible test/duplicate activity, disclose sample sizes and distinguish paid, granted and refunded activity.

Mainnet verification requirements

The cutover design includes maintenance restrictions on writes, paused scheduled jobs, fresh token/economy provenance checks, token registration and immutability, separate configuration/payout/recovery/upgrade authorities, verified object bindings and rollback-safe checks. Database attestations, wallet continuity and post-launch flow checks complete the transition evidence. Testnet-only economic grants must remain disabled outside an explicitly configured testnet environment.

Completion needs dated records for the relevant network, package, configuration and tested flows. A runbook or deployed entrypoint is not proof that those requirements have been met.

Source of Truth

An on-chain receipt does not by itself resolve a refund or contractual dispute. Activation, supply and financial claims require the appropriate evidence above.

Official references

• About GEXI
• Creator program
• How it works
• Token overview
• Whitepaper and downloadable Markdown
• Roadmap
• Frequently asked questions
• Public Move source and deployment references