youknObtainium – Plan

This page describes the planned token and tournament system: goals, flows, what is implemented, and what cannot be done (on-chain and pump.fun constraints).

Goals

Wallet-optional: "Play as guest" (no wallet); later connect wallet and "Recover" past wins into your account (one-time migration of guest stats).
5 players per game: Every game has exactly 5 players, from 1 user vs 4 bots up to 5 users vs 0 bots. Users play against each other and against bots; only the winner of each game gets the win and triggers the automatic buy of obtaniumcoin.
Universal rules: The Event Horizon rule and all other game rules (matching, molecules, ferromagnetism, temperature, decay, etc.) are the same for every game—whether 1 user vs 4 bots or 5 users vs 0 bots.
Automatic buy of obtaniumcoin on every win: Only the winner of each game wins and gets the buy. If a bot wins, the system automatically buys obtaniumcoin (proportional to that win’s efficiency, 1/turns) to the bot pool or treasury. If a connected user wins, the same rule applies and the user receives the buy (or their wallet is charged, per design). Efficient wins (e.g. Event Horizon in 1 turn) = larger buy.
Ranking: Rank = wins per turns (efficiency). Event Horizon wins count as high-value (bonus or separate badge).
Security: Win records and token buys are handled server-side; private keys never exposed in the client.
Guest rule: Guest wins are attributed to bots (so a bot win triggers the auto-buy) until the user links a wallet and recovers.
Token (obtaniumcoin): Created on pump.fun. One winner per game; that winner’s win triggers an automatic buy proportional to that game’s efficiency. Optional: scheduled tournament for entry fee and rewards pool.

Diagrams

5-player game (1–5 users, rest bots)

flowchart LR A[5 players: 1–5 users + bots] --> B[One winner per game] B --> C[Only winner gets win] C --> D[Auto-buy obtaniumcoin]

Guest vs linked flow

flowchart LR A[Play as guest] --> B[Wins stored locally] B --> C[Recover: connect wallet] C --> D[Sign & migrate wins] D --> E[Wins tied to wallet] F[Connect wallet first] --> G[Wins tied to wallet] G --> E

Auto-buy obtaniumcoin on win

flowchart LR subgraph One winner per game BW[Bot wins game] --> AB[Auto-buy obtaniumcoin] UW[User wins game] --> AB end AB --> R[Amount ∝ 1/turns] R --> T[obtaniumcoin] T --> U[User wallet if user won] T --> P[Bot pool / treasury if bot won]

Tournament (optional)

flowchart TB T[Tournament date TBD] T --> E[Entry: obtaniumcoin / fee] E --> P[Play] P --> R[Rank by efficiency] R --> W[Winners] W --> D[Rewards pool] D --> N[Token rewards]

Ranking (efficiency + Event Horizon)

flowchart LR subgraph Rank R[efficiency = wins / turns] end EH[Event Horizon win] --> Badge[High-value badge] R --> Leaderboard Badge --> Leaderboard

Backend

Firebase: Auth, win records (scoreboard), and guest recovery. Cloud Functions for win recording and (when ready) executing automatic obtaniumcoin buys.
Recovery flow: user signs a message; backend migrates guest wins to the linked wallet so future wins count as user wins and trigger user-side auto-buy.

obtaniumcoin (pump.fun) & automatic buy on win

The project token obtaniumcoin is created on pump.fun. Each game has 5 players (1–5 users, rest bots); only the winner of the game gets the win and triggers the buy. Core mechanic:

When a bot wins: The system automatically buys obtaniumcoin proportional to that win’s efficiency (1/turns). The token goes to a bot pool or treasury.
When a connected user wins: The system automatically buys obtaniumcoin proportional to that win’s efficiency; the user receives it (or the user’s wallet is charged, depending on design).

Efficient wins (e.g. Event Horizon in 1 turn) yield a larger buy. Who pays (house treasury vs user wallet) and who receives (user vs bot pool) will be set before launch.

Phase one: Maximum supply of 1B (one billion) obtaniumcoin, with an expected reach of 100M (100 million) users.

Optional: Scheduled tournament with entry fee and rewards pool in obtaniumcoin. Link to pump.fun token: (to be added when token is created).

Price visualization (conceptual)

Below is a simplified model of how obtaniumcoin price could rise over time. Each game has 5 players and one winner; only that winner’s win triggers an automatic buy (size = efficiency, 1/turns). The price curve is aligned with a bonding-curve (pump.fun-style): price rises as buy volume fills the curve. The chart shows a hypothetical first year.

Price (left axis) follows a bonding-curve shape: it rises with cumulative buy volume (right axis) from user wins and bot wins. Formula approximates constant-product behavior (price ∝ buy pressure²) as on pump.fun.

Average gameplay time & games for the curve

Average time per game: Each game is 5 players, turn-based (no fixed timer). Each player starts with 9 cards and must empty their hand to win. A typical game lasts on the order of tens of turns (one turn = one player’s move). In real time, with human players taking ~15–30 seconds per turn, that’s roughly 5–15 minutes per game; with bots only it can finish in under a minute. Event Horizon wins in 1 turn (instant win).
Games needed for the curve to look exponential: The price curve is quadratic in buy progress (price ∝ progress²), so it steepens as more games are won. “Exponential” here means strong, accelerating price growth. That happens when cumulative buy volume (efficiency-weighted wins) is large enough that progress along the curve is significant. In the chart model, progress = totalBuy / 400,000 (capped at 2). So you need on the order of hundreds of thousands of winning games (with average efficiency ~0.1–0.2) for price to rise sharply; e.g. ~200k–400k+ games for progress ≈ 1 and clear curve steepening. On pump.fun, the real curve is filled with SOL (e.g. ~86 SOL to complete); the number of games that equates to depends on how much SOL each win converts into.

What we can do

Store guest wins locally and in Firebase (with guest id or session).
Connect wallet (MetaMask / WalletConnect) and identify the player.
One-time "Recover" flow: link wallet, sign message, migrate guest wins to the linked account.
Run games with 5 players (1–5 users, 0–4 bots); only the winner gets the win and triggers the auto-buy of obtaniumcoin. Attribute guest wins to bots until the user recovers.
Compute efficiency (wins/turns) and Event Horizon count for ranking; use it to size automatic obtaniumcoin buys for each winning game.
Backend executes win recording and (when ready) token buys; client never touches private keys for those operations.
Static plan page (this page) and documentation.

What we cannot do

On-chain limits: Gas and chain rules apply; we cannot bypass transaction costs or chain finality.
pump.fun constraints: Token creation and trading follow pump.fun rules; we do not control their platform.
Proving guest wins on-chain: Until recovery, guest wins are off-chain (Firebase + local); only after "Recover" are they tied to the wallet for user-win auto-buy and ranking.

Implementation status

Done: Plan page (this page); win records in Firebase (scoreboard) with eventHorizon and turns; efficiency can be computed (wins/turns). Wallet & Recover page: Connect wallet (MetaMask via window.ethereum), "Play as guest" (default), "Recover wins" flow (UI in place; backend migration when Cloud Functions are ready). Guest wins stored in localStorage and shown on recover page; recovery message explains attribution to bots until backend is live.
In progress / planned: 5-player games (1–5 users, rest bots); only winner triggers buy. WalletConnect; automatic buy of obtaniumcoin per winning game (backend executes buy ∝ 1/turns; bot wins → bot pool/treasury, user wins → user wallet or user-pays flow); Cloud Functions for recovery migration and buy execution; pump.fun token (obtaniumcoin) creation and tournament rules.

← Back to game