Play for a public token.
Send inside the app.
Open the site. Play a pixel runner. Receive eligible rewards into a company-held balance. A simple front end, backed by verifiable game rules and funded reward accounting.
A funded reward pool
The proposed pool is 10% of the token supply, actually acquired and held by the company before rewards begin. Pump's current creation arguments do not include a free 10% creator allocation. The pool distributes existing tokens; it does not mint more tokens.
PCASH is not issued yet. Wallet connection and signed run registration are available; rewards activate after the company reserve is confirmed.
Play first. Verify the run.
Space or tap to jump. The game records a seed and jump inputs, then replays the exact mechanics to check the result. Active play earns 10 points per second at the starting rate. Each 250 pixels adds a compounded 5% distance bonus, capped at 8×. Paused time earns nothing.
The server issues the seed, checks elapsed time and checkpoints, and independently replays fixed-point mechanics. Each run is bound to a wallet and private receiving keys. Browser-reported scores alone cannot authorize payouts.
A valid replay can be produced by a bot. ZK proves computation, not that a human played. Daily/global reward budgets and capped participation keep the reserve bounded; further eligibility controls need an explicit policy.
Internal balances. Public withdrawals.
Rewards enter a company-held internal balance. Spending-key signatures authorize sends; the server checks balances and prevents repeated requests. Internal sends are not published to Solana. Withdrawals send the actual public token to your wallet.
| Activity | Visibility |
|---|---|
| Pump trades | Public wallets, amounts and timing. |
| Reward reserve | Public company token account. |
| Game and internal sends | Visible to the operator; kept offchain. |
| Withdrawals | Public destination, amount and timing. |
The company controls custody. Encrypted storage does not make balances noncustodial or ZK-enforced. Timing and provider logs can still link activity.
A finite emission schedule
Daily rewards are shared in proportion to verified points. 80% of the reserve is scheduled; 20% stays unallocated. Half of the scheduled amount is spread over the first 180 days, then the daily cap halves. Rewards use the larger of 40 million points or the day’s total as their denominator. Low participation pays less, and more players share the same cap. Unused budgets stay in reserve. A wallet contributes at most 30 active minutes and 100,000 points per day.
Claim. Send. Withdraw.
Claim credits the internal balance once. Send moves it to another PCASH account. Withdraw requires wallet approval and a company co-signature. The app confirms payment only after finalized Solana receipts and matching token amounts. Encrypted account backups restore access on a new device while the company preserves the ledger.
Before live payouts
Issue PCASH, acquire the reserve and connect company custody. No custom vault deployment or GPU proof is needed for this path. Source checks are separate from actual mainnet payments.