Trading activity
A 5% trading fee routes creator revenue into the project’s treasury allocation.

A Solana-first token with legacy multichain infrastructure. Eligible creator-fee receipts support gaming rewards for PlayStation, Xbox and Steam gift cards. Hold longer, earn loyalty points and claim your share of funded rewards.

Rewards are funded by the project's allocated share of creator trading fees, not by guaranteed returns.




A 5% trading fee routes creator revenue into the project’s treasury allocation.
80% of creator fees earmarked for gift cards, 20% for project operations. Net rewards are calculated after gas, swaps and bridging costs.
Hold tokens over time to earn points. Monthly rewards depend on your share of total eligible points and net settled treasury funds. Choose PlayStation, Xbox or Steam when live claims open.
The main Solana treasury balance is displayed first, with Base ETH retained separately. Wallet balances are not claimable rewards; allocations and liabilities are tracked independently.

Checking Solana treasury wallet…
Treasury wallet: FaoPLigXKBPQkMSfK4ML4uoTxPiYkn6JX1Ej6dRmH4UA
The primary SOL balance is a public on-chain wallet balance, not the distributable rewards pool. Base ETH is displayed separately. Neither balance implies a funded holder claim.
Policy percentages are not live wallet balances. Verified reward allocations are administered separately.
Real finalized SOL receipts and separately recorded holder allocations. The neon bars show the 80/20 policy; metrics come from the SOL ledger, not wallet-balance estimates.
Loading chain funding figures…
Unreceived or unverified funding is never included in the available rewards balance. Chains with no published figures show “Not reported”, not £0 or 0 ETH.
Connecting to the live funding ledger…
Primary figures above are SOL. Legacy Base-settled funding is displayed below in ETH; the two currencies are never added together.
On-chain SOL balance and verified reward allocations are different values. SOL is never bridged to Base.
GTA Rewards maintains dedicated treasury wallets for Solana and legacy EVM operations. Displayed wallet balances are not reward entitlements. Sensitive signing material must never be included in website files or shared with visitors.
The Solana treasury is shown first and can be independently inspected on Solscan when configured. Legacy Base transactions remain verifiable on BaseScan. Signing keys and gift card credentials must remain server-side.
Solana is the primary vault. Base ETH is retained as a separate legacy treasury and is never combined with SOL for accounting.
Connect your wallet in the Rewards app to check your verified individual allocations, claim status and history.
Solana-first presentation with retained EVM accounting. A system designed to convert eligible trading-fee revenue into claimable gaming gift cards.
The production design separates on-chain tokenomics from off-chain gift card fulfilment. Verified live balances and claims are enabled when the connected services are operational.

The existing EVM tokens retain their original contracts and independent fee arrangements. The replacement Solana token will launch separately; its fee settings must be verified against the final Stonk configuration.
Our intended allocation remains 80% of net creator-fee revenue to rewards and 20% to operations. Actual receipts and any launchpad deductions must be reconciled on each network.
The GTA Rewards service monitors each chain’s payout wallet and reconciles actual receipts into separate SOL and EVM ledgers. SOL stays on Solana; EVM revenue alone may auto-bridge to Base. Each treasury retains its own asset accounting.
Verified historical balances produce daily points using √(tokens / 1,000) × loyalty multiplier. Monthly entitlements reflect each holder's share of total eligible points.
The GTA Rewards backend authenticates holders, reserves eligible credit, submits a paid gift-card order through the CryptoRefills API and securely delivers the resulting code. CryptoRefills orders are off-chain purchases paid through supported blockchain rails.

GTA Rewards runs a dedicated backend service alongside the public website. It connects to deployed token contracts using blockchain data providers; it does not require a second token factory or modification to the deployed token address.
Chain-specific indexers monitor confirmed token transfers, wallet balances and treasury receipts. Transactions are reconciled with confirmations and replay protection so the same event cannot be counted twice.
Daily balance snapshots establish eligible holdings and holding duration. Wallet ownership is proven with a signed message, not by typing in an address. Cross-chain rules prevent counting bridged holdings twice.
Each wallet earns points using the published loyalty formula. At monthly settlement, the backend apportions the net funded pool by eligible points, records a permanent entitlement ledger and makes claimable credit visible.
When a holder requests a gift card, the backend checks the wallet session, denomination, region, available credit and claim history. It atomically reserves the balance to prevent duplicate spending.
A restricted payment service uses funded purchasing balances to submit a paid CryptoRefills API order. Order status and fulfilment are reconciled before the claim is marked complete; failures are retried safely or released for review.
The site displays verified treasury inflows, allocations, settlement history and claim statuses. Sensitive purchase credentials and gift-card codes stay server-side; the treasury Safe signers never live on the web server.
Monthly rewards formula: daily points = √(tokens held ÷ 1,000) × loyalty multiplier. Points are not currency and do not guarantee a payout.
Points accrue each day based on balance and holding duration, with diminishing returns for very large holdings.
Available funds after applicable gas, EVM-only bridging and gift card costs are apportioned by eligible points across all chains.
Claim a supported gift card denomination only when it is funded and enabled in the Rewards app. Unused allocations are subject to the live app’s settlement rules.
The proposed loyalty multiplier grows from 1× to a maximum of 1.5× over 30 consecutive holding days. At launch, verified on-chain history and anti-duplication rules will be needed for accurate reward calculations.
Connect a supported wallet to see recorded rewards and gift card options. SOL cash-out and automated SOL gift-card checkout are being integrated; current ETH flows remain separate.

Reward balances, requests and claim history are managed in the app—not in a separate homepage demo.
The new Solana token address is awaiting confirmation. Existing chain history is retained; a wallet balance is not a reward entitlement. Payment availability is shown by the app.
SOL is retained in its separate Solana treasury. Native SOL rewards, SOL cash-out and gift-card checkout are implemented but remain subject to wallet ownership verification, signing configuration and live settlement checks. Only EVM funds may be bridged to Base. The backend never treats an unverified wallet balance as claimable reward credit.
Gift card rewards for compatible PlayStation Store regions.
Gift card rewards for compatible Microsoft / Xbox regions.
Wallet credit for PC games and other eligible Steam purchases.
Brand references are descriptive. This independent concept is not affiliated with Rockstar Games, Take-Two, Sony, Microsoft, Valve or CryptoRefills. Availability, denominations and redemption rules require validation.
Verified token addresses will appear here as each chain goes live. Copy the official CA for your network; never trust addresses from unsolicited messages.
Token address published at launchChoose your chain below to copy the verified contract address. Only addresses published here after deployment are official.
Solana mint address pending final confirmation. Existing EVM addresses remain separate.
80% of creator fees allocated to the global rewards treasury; 20% to operations. Estimated conversion reserve 5% of rewards allocation. Real fee routing and chain deployment must be verified at launch.