Skip to content
Arenaton Docs

Arenaton Technical Docs

Learn the current Polygon-only, non-custodial exchange model, including REST, WebSocket, Smart Accounts, Raw EOA Mode, CTF Outcome Shares, Paper Trading, and explicit safety boundaries.
Quick start API reference Paper trading Resolution rules

These docs describe the planned and current exchange surfaces. Production real-money readiness remains gated by contracts, audits, indexer, paymaster, risk, and incident controls.

Current architecture

Go pulse server, PostgreSQL, Flutter web app, Polygon production path, and isolated Amoy Paper Trading infrastructure.

Trading APIs

REST plus WebSocket surfaces for markets, order books, orders, account projections, status, and paper operations.

Paper backend

Paper order intake, matching, settlement, lifecycle, faucet, indexer projection, and WebSocket events in one Go exchange spine.

CTF model

Condition IDs, collection IDs, position IDs, primary splits, resale transfers, and direct redemption boundaries.

EIP-712 orders

Typed order fields shared by Flutter signing, Go validation, and settlement-contract verification.

Resolution rules

Source policy, Invalid Path, Correction Window, Direct Redemption, and category rules for sports, esports, and crypto Markets.

Flutter app

Web-first app surfaces, paper-mode services, account flows, localization, and environment selection.

Account modes

Smart Accounts are default. Raw EOA Mode remains available for advanced users with direct signing requirements.

Safety boundaries

Arenaton does not hold user trading collateral, cannot seize user assets, and must keep environment separation intact.

Documentation Status

Section titled “Documentation Status”

Use this site as the public technical source for Arenaton Exchange behavior, APIs, account modes, contracts, paper trading, and resolution boundaries.

New Implementation Docs

Section titled “New Implementation Docs”
  • Paper Trading Backend documents the Go paper exchange engine from order intake through redemption.
  • Gnosis CTF Model documents CTF mechanics without treating third-party addresses as Arenaton production config.
  • EIP-712 Order Format defines the typed order payload used by Flutter, Go, and settlement contracts.
  • Resolution Rules define how Arenaton publishes source data, correction windows, invalid paths, and direct redemption boundaries.
  • Flutter Web App maps the current app architecture and paper-mode integration points.