> For the complete documentation index, see [llms.txt](https://docs.playnance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playnance.com/token-flows/token-flows.md). # Token Flows GCoin (G) is the native utility and settlement token of the PlayBlock ecosystem.\ Its flow is intentionally simple, deterministic, and fully observable on-chain. Every movement of GCoin follows strict rules designed to ensure: * Transparency * Auditability * No hidden balances * No off-chain manipulation This document describes how GCoin moves, who controls it, and why the model is safe by design. ### High-Level Principle GCoin never moves implicitly. Every GCoin transfer is: * Initiated by a smart contract * Executed on-chain * Visible in the PlayBlock explorer * Final and deterministic There are no internal ledgers, no virtual balances, and no off-chain settlement. ### Core Actors in the GCoin Flow GCoin moves between a small, well-defined set of actors: 1. User Wallets 2. Product Treasuries 3. System Executors (Relayers) 4. Reward Distribution Contracts 5. Liquidity & System Vaults Each actor has a single responsibility and limited permissions. *** ### Primary GCoin Flow Paths #### 1. User → Treasury (Spending GCoin) This is the most common flow. **When it happens** * Casino bets * Prediction bets * Game entry fees * Any paid interaction **Flow** ``` User Wallet → Product Treasury ``` **Properties** * Triggered by a smart contract call * Funds leave the user wallet immediately * Treasury balance increases atomically * No intermediary custody This ensures the system never holds user funds off-chain. #### 2. Treasury → User (Winnings & Payouts) When a user wins, GCoin is paid directly from the treasury. **Flow** ``` Product Treasury → User Wallet ``` **Key properties** * No batching delays * No internal accounting * One transaction per payout * Fully traceable winner → treasury → tx hash This guarantees that winnings are real funds, not credits. #### 3. Rewards Distribution Flow Rewards are distributed for: * User registration * Engagement actions * Campaigns and promotions * Gamified features (e.g. spinners, quests) **Flow** ``` Rewards Contract → User Wallet ``` **Important** * Rewards are minted or allocated according to predefined rules * Distribution logic is deterministic * Rewards never pass through operator wallets Users can immediately verify reward transactions on-chain. *** #### 4. System-Initiated Transfers (Executor Flow) Certain flows are executed by authorized system executors. Examples: * Settling multi-step games * Batch reward execution * Operational transfers between vaults **Flow** ``` Executor → Smart Contract → Target Wallet ``` **Security guarantees** * Executors are whitelisted * Executors never custody funds * Contracts enforce destination and amount * Executors cannot redirect funds This prevents operator abuse while enabling high throughput. #### 5. Treasury ↔ Treasury Transfers (Internal Accounting) In some cases, funds move between treasuries: * Product balancing * Migration between game versions * System-level reallocation **Flow** ``` Treasury A → Treasury B ``` **Constraints** * Explicit contract calls * Logged events * No hidden rebalancing Every treasury remains independently auditable. ### What Never Happens (By Design) GCoin **does not**: * Sit in off-chain databases * Move without a transaction * Get “credited” without transfer * Exist as IOUs or shadow balances * Get settled later When user sees a balance change there is a transaction hash behind it. ### Observability & Auditability Every GCoin movement can be: * Traced by wallet * Grouped by treasury * Replayed via event logs * Verified via transaction receipts This enables: * Independent audits * Partner verification * User trust * Real-time monitoring ### Why This Model Works The GCoin flow model prioritizes: * Determinism over convenience * Transparency over abstraction * On-chain truth over internal accounting This keeps the ecosystem: * Secure * Scalable * Regulator-friendly * Partner-ready GCoin is not just a token; it is the settlement layer of PlayBlock. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.playnance.com/token-flows/token-flows.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.