APT-CasinoLitepaper

APT-Casino is a multichain GambleFi platform that treats casino play as verifiable, on-chain probabilistic compute — not opaque server-side RNG.

The product combines provably fair games, gasless UX, house ledgers per chain, and an APTC token layer that routes protocol revenue back to players through buyback, burn, and staking.

Live chains today: Solana and Aptos (Move contracts + aptos_framework::randomness on Aptos). Sui, EVM, and Starknet are registered as coming soon in the chain registry.

Design objective: Web2-grade onboarding (keyless Google/Apple + Petra) with Web3-grade transparency — every bet, deposit, and withdrawal is auditable.

APT-Casino was born after a firsthand experience with legacy online casinos: misleading bonus terms, hidden wager limits, and custodial balances that trap users.

The founder deposited into a major Web2 platform, received a 200% bonus, then discovered bets were capped at $1 and withdrawals required tens of thousands in play-through — classic opaque house rules.

That frustration became a product mandate: no hidden wager traps, no rigged outcomes, and no custodial lock-in. Players own their assets and can verify fairness on-chain.

The platform evolved from an Aptos hackathon project into a multichain product with live play on Solana and Aptos, APTC economics, live streaming, and community programs (referrals, volume cups, OTC lottery).

Traditional online gambling is centralized: opaque RNG, high fees, restrictive withdrawals, misleading bonuses, and no true asset ownership.

Web3 adoption friction remains high — wallet setup, gas, and transaction confirmations scare Web2 users away from decentralized alternatives.

Social layers are missing on most crypto casinos: no integrated live streaming, limited chat, and no shareable proof of wins/losses for community growth.

APT-Casino targets this gap with provably fair games, treasury-funded gasless play on Aptos, per-chain house balances, and transparent fee economics published in env/config.

Games (live): Plinko, Mines, Roulette, Spin Wheel — each with configurable risk, multipliers, and on-chain or server-verified outcomes depending on chain.

Multichain play: Solana (server house balance) and Aptos (client balance mode + Move modules). Chain switcher in navbar follows PLAY_CHAINS registry order.

Social: Livepeer-powered /live streams, Socket.IO wallet-signed chat, leaderboards, Volume Cup competitions, and ROI share links on withdrawals.

DeFi surfaces: Stake (APTC staking pools), referral APTC rewards with cliff unlock, OTC lottery (SOL → APTC, lock period), and GGR-driven APTC buyback dashboard.

Wallet UX: Google/Apple keyless login, Petra wallet, and gasless Aptos transactions sponsored by treasury relayer — users play without signing every micro-action.

APT-Casino is a Next.js application with chain-specific API routes under /api/chains/{chainId}/, Supabase for profiles, balances, referrals, and audit logs, and Move contracts on Aptos for core game logic.

Sensitive writes (deposits, withdrawals, referral unlocks, GGR estimates) run server-side with service-role Supabase and validated env economics — never trusted from the client alone.

Live features (streaming, chat) sit beside the gaming core: Livepeer for video, Socket.IO for real-time messages bound to wallet identity.

APTC lives on Solana (SPL); price and market stats integrate via DexScreener when NEXT_PUBLIC_APTC_SOLANA_MINT is configured.

A single chain registry (lib/chains/registry.ts) is the source of truth for UI labels, treasury env keys, balance modes, and API paths.

Each live chain has isolated treasury and platform-fee wallet addresses — reducing cross-chain blast radius.

Solana uses server-side house balances (balanceMode: server); Aptos uses client balance mode with on-chain module interaction.

Coming-soon chains (Sui, EVM, Starknet) are pre-wired in the registry so adapters can go live without restructuring the app.

Deposit: user sends native asset to chain treasury; platform fee (default 10% = 1000 bps) is collected to the fee wallet; net amount credits house balance.

Bet: game module or server handler debits balance, records play event, resolves outcome via RNG or on-chain randomness, credits payout.

Withdraw: user requests withdrawal; amounts above manual USD threshold queue for review; treasury signs outbound transfer.

Referral: on qualifying first deposit, referrer earns APTC (not native play token) — unlock after 14-day cliff or referee volume milestone (default $100 USD play volume).

Aptos games use aptos_framework::randomness and on-chain Move modules — outcomes are verifiable from transaction data and module events.

Randomness inputs include block context, player address, and game nonces; contracts enforce reentrancy protection and input validation.

Solana play paths use server-side resolution with logged play events in Supabase for volume, GGR, and competition accounting — designed for high-throughput UX.

The platform publishes provably-fair messaging on-site; contract source and deployment addresses are intended for public audit (see GitHub).

Native ecosystem token: APT Casino Token (APTC) on Solana (SPL).

Max supply: 1,000,000,000 (6 decimals).

Public launch on Bags app. Public launch on Bags — protocol accumulates to a 10% holding (100M APTC) via launch buys and Meteora / open-market purchases.

Acquisition path: ~2% (20,000,000 APTC) purchased at launch on Bags, then incremental open-market buys on Meteora, Bags, and other venues until the protocol holds 10% of supply (100,000,000 APTC).

House staking: Stake APTC in fixed-term pools on the Stake page. Yield is funded from protocol revenue, staking emissions (12% of the protocol bucket), and GGR buyback. Referral rewards: Referrers earn APTC (not native play tokens). Rewards unlock after a 14-day cliff or when your referee hits a volume milestone — routed from the community bucket. GGR buyback & burn: A share of gross gaming revenue is used to market-buy APTC on open markets. A portion is burned, reducing circulating supply. OTC & volume programs: OTC lottery and Volume Cup prizes allocate APTC from the community bucket without forcing large size through thin DEX books at launch.

APTC is not required to place bets in native SOL/APT — it is the rewards, staking, and value-accrual layer on top of core casino play.

1. Play — Bets on Plinko, Mines, Wheel, Roulette across Solana & Aptos. 2. House edge — Configurable edge per game (≈1–4%) produces gross gaming revenue (GGR). 3. Buyback — Protocol allocates a % of GGR to open-market APTC purchases (Bags / Meteora / DEX). 4. Burn & stake — Bought APTC is split between burn, staking rewards, and treasury reserves.

Default economics (env): 30% of GGR allocated to APTC buyback (GGR_BUYBACK_BPS_OF_GGR=3000).

Buyback split: 50% burn · 35% stakers · 15% treasury (GGR_BURN/STAKER/TREASURY_BPS_OF_BUYBACK).

Average house edge assumption for estimates: 2.5% (GGR_AVG_HOUSE_EDGE_BPS=250). Actual edge varies per game (~1–4%).

Dashboard surfaces estimated GGR and buyback from play events — live execution requires APTC mint + DEX liquidity configured.

Platform fees (default): 10% on deposits and 10% on withdrawals (PLATFORM_FEE_BPS_DEPOSIT/WITHDRAW = 1000 bps).

Referrer share: 2% of gross first deposit (REFERRER_FEE_SHARE_BPS_OF_DEPOSIT = 200), capped so payout never exceeds platform fee collected.

House edge on wagers is the primary GGR source; a portion funds APTC buyback rather than opaque bonus traps.

Additional rails: OTC lottery spreads, staking protocol fees, future NFT/profile monetization, and partner promotions.

Manual withdrawal review triggers above USD threshold (MANUAL_WITHDRAW_USD_THRESHOLD, default $50) to protect treasury continuity.

Each user gets a referral code; referees attach on signup or first deposit.

Rewards are denominated in APTC, not SOL/APT play balance — aligning growth incentives with the ecosystem token.

Unlock rules: 14-day cliff (REFERRAL_APTC_CLIFF_DAYS) OR referee reaches volume unlock (default $100 USD from play events).

Referral page shows pending vs unlocked rewards; on-chain APTC payout wiring activates when staking/APTC infra is fully live.

The /stake page offers fixed-term APTC staking pools with transparent APY display and vault address when configured.

Staking yield combines emission schedule (12% allocation) and GGR staker share from buyback (35% of buyback by default).

Env gates: APTC_STAKING_ENABLED and NEXT_PUBLIC_APTC_STAKING_ENABLED must be true once mint and vault are production-ready.

Stakers participate in the same value loop as players — protocol revenue returns to long-term holders, not only active gamblers.

OTC lottery: users swap SOL for discounted APTC with a lock period — sized for power users who would otherwise move thin DEX books.

Volume Cup (/competition): seasonal leaderboard competition rewarding high-volume players with APTC prizes.

Both programs route distribution through the community allocation bucket rather than discretionary airdrops.

Leaderboards and public stats depend on Supabase play events — no fabricated volume when DB is unconfigured.

Move contracts: input validation, reentrancy guards, event logging for transparency.

Server: treasury keys only in server env; never exposed to client bundles.

Supabase: RLS on user tables; service role restricted to API routes.

Withdrawals: manual review for large USD amounts; audit log for balance mutations.

Ongoing: contract audits before major mainnet expansions; bug bounty planned as TVL grows.

Shipped / live: core casino games, Solana + Aptos play, gasless Aptos UX, referrals, Stake UI, GGR dashboard, live streaming shell, ecosystem partners section.

Near term: APTC public launch on Bags app, protocol accumulation to 10% (100M APTC), Meteora/Bags liquidity, staking writes enabled at TGE.

Mid term: Sui + EVM chain adapters live, AI-generated NFT profiles, developer SDK for third-party provably-fair games on the hub.

Long term: largest multichain GambleFi hub — transparent game marketplace, creator revenue share, and community governance over APTC parameters.

The homepage “What’s coming” section lists 30 curated milestones (Platform, Governance, Community, Security, Tournaments, Partnership) via /api/roadmap — editable in Supabase roadmap_items or src/lib/config/publicRoadmap.js.