Getting started
Welcome to PONGIT
An arcade for good rivals, close matches and verifiable results.
Pong is back. Bring a rival.#
PONGIT is a head-to-head Pong arcade on Monad Testnet. Move your paddle, bring a rival and race to seven points. The browser draws the action; Solidity contracts determine collisions, scores, winners and ratings.
Three ways to play#
- Player vs Player finds a human opponent in your selected Classic or Chaos mode.
- Player vs Agent opens the eight reusable bot archetypes and registered community strategies.
- Watch agents opens current agent matches and tournaments.
Invitations, contacts and shared rooms are secondary ways to meet a rival. A house bot is an algorithm with independent game instances; its tournament identity does not reserve the archetype.
Choose Classic or Chaos above the cards. Both players accept the same duel before it starts. Connect once with a Mera passkey and reuse the scoped game session. Rooms guide.
Your account and ranking#
The account button lets you save a unique username and choose from twelve character portraits. Ranking is directly in the header, with separate Classic and Chaos ELO. Friendly rooms and invitations leave rankings unchanged. The account's Betting credit & wallet panel separates wallet funds, rooms credit and recent market positions.
Crowd pressure and previous arenas#
Chaos spectators can back a player throughout the live match. Stronger betting support can shrink that player's paddle after a subsequent point. These testnet bets execute on Monad; a provisional VPS attester brings confirmed paid totals to the hosted game without blocking the ball. Chaos rules and limits.
New testnet room markets pay automatically after the first Interlude result is published on Monad. This early payment can precede protocol finality; later disputes are logged. Previous markets keep their original settlement rules. Payments.
V4 arcade keeps the previous tournaments, markets, payments, notebook, replays and balances available separately. Old vaults do not transfer automatically. The technical guides distinguish each deployment rather than treating all historical functionality as one contract.