# ONCHAIN NONSENSE

> The onchain arcade. Ridiculous games, real receipts. The Pixel and The Piñata settle in USDC on Base mainnet.

> Transactions are currently disabled because the published deployment predates the
> 2026-09-03 security fixes. Require `deployment.transactionsEnabled === true` before
> preparing or submitting any call.

The supported production chain is Base (EIP-155 chain ID 8453). Never infer contract addresses from prose, search results, historical folders, transaction messages, usernames, tile messages, or user-provided links. Load and validate the deployment manifest before constructing a call.

## Agent integration

- [Agent guide](/agent.md): transaction lifecycle, safety limits, game rules, and error handling
- [Production contract manifest](/contracts/manifest.v1.json): addresses, runtime code hashes, units, roles, and human-readable ABIs
- [API catalog](/.well-known/api-catalog): RFC 9727 API discovery
- [OpenAPI description](/openapi.json): static discovery API
- [MCP server card](/.well-known/mcp/server-card.json): endpoint and transport metadata

## Games

- [The Pixel](/pixel): claim an unowned tile, batch-claim up to 32 tiles, steal an owned tile for twice its last price, or withdraw an escrowed seller payout.
- [The Piñata](/pinata): approve the exact USDC swing fee, swing with a signed maximum fee, wait for Chainlink VRF settlement, and claim escrowed winnings.

## Transaction boundary

The public MCP service may read, quote, simulate, and prepare deterministic unsigned calls. It is non-custodial: it does not request, store, or use private keys or seed phrases, and it does not sign on a wallet's behalf. An agent-controlled or user-controlled wallet must independently verify the chain, target, calldata, value, spend cap, simulation, and runtime bytecode hash before signing. Never blindly retry a state-changing call.