Learning creates value. Most platforms fail to recognize it.
Traditional trivia ends when the score appears. Traditional learning platforms measure completion, not verifiable performance. Geek Protocol connects knowledge, competition, community-authored content, reputation, and transparent accounting in one system.
It began with index cards for a father and son. The mission grew, but the core idea did not: make learning feel worth doing.
A result should be earned, reproducible, and auditable.
The current Alpha keeps ranked questions, correct answers, deadlines, scoring, and leaderboards on the server. The browser receives only one shuffled question at a time and cannot directly write a score.
Correct choices never ship in the public game bundle.
Opaque tokens and atomic claims stop replayed or parallel answers.
Sources and explanations appear after an answer is locked.
Alpha credits remain visibly separate from real on-chain tokens.
Ten rounds. Rising risk. A reason to learn.
Players choose a knowledge category and face ten questions per round under a server clock. Round one is free. Later rounds spend Alpha GEEK from the practice ledger. After each completed round, the player can continue or close the run.
- Eight selectable knowledge categories
- Cryptographically shuffled questions and answer order
- Speed and streak scoring computed by the server
- Category-specific verified leaderboards
- Source-linked review after every locked answer
The community expands the game without weakening the truth.
Contributors submit an original question, four answers, an explanation, and a primary source. The submission stays private until a human moderator reviews and publishes it. A published question can earn one Alpha ledger credit when it is first used in ranked play.
Credits are not currently transferable, withdrawable, or guaranteed to become tokens.
Wallet-neutral rewards, gated settlement.
Geek Protocol is being designed so an eligible participant can choose any valid Kaspa mainnet receiving address. Kasware may provide a convenient connection, but it is not intended to control where rewards are sent.
- NETWORK
- Kaspa
- TOKEN STANDARD
- KRC-20 target
- ECONOMIC MODEL
- 70% rewards / 30% burn proposed
- LIVE STATUS
- Alpha ledger only
The canonical token identity, treasury authority, eligibility, limits, jurisdictional terms, transfer implementation, monitoring, and reconciliation must be publicly verified before on-chain payout activation.
No seed phrases. No hidden payout switch.
- Geek Protocol must never request or store a player’s seed phrase or private key.
- Wallet connection and signing happen only after an explicit player action.
- Identity uses short-lived, single-use server challenges, public-key/address matching, and server-side signature verification.
- Protected payout changes require fresh wallet proof; every destination starts a 72-hour future-settlement cooldown.
- Sensitive Alpha changes create pseudonymous integrity-protected audit evidence.
- Production requires both an independent Web3 application penetration test and a separate audit of value-moving settlement code.
Ship proof before promises.
- LIVE ALPHAServer-ranked games, selectable categories, lobbies, C.C.E. moderation, internal reward records, server-verified wallet proof, recoverable player identity, and protected wallet-neutral payout registration.
- IDENTITY HARDENINGIndependent replay and race testing, wallet-rotation policy, change notifications, high-risk review, and hardware-backed privileged access.
- SETTLEMENTCanonical token verification, treasury controls, reviewed KRC-20 transfer path, withdrawal limits, reconciliation, and external audit.
- EXPANSIONReal-time multiplayer, quests, achievements, creator reputation, marketplace systems, and community governance.