PolyGram Whitepaper — Architecture & Tokenomics

A technical overview of how PolyGram operates: order routing, custody, on-chain settlement, USDC flow, the PGUSD attribution layer, and the trust assumptions that bind the system.

1. What PolyGram is

PolyGram is a prediction-market interface and execution layer that aggregates liquidity from Polymarket's central-limit order book (CLOB) on Polygon. Users deposit USDC, trade YES/NO outcome shares, and receive on-chain payouts at market resolution. PolyGram does not custody outcome shares directly — these settle on Polymarket's contracts on Polygon — but holds the user's working USDC balance in a multi-signature treasury wallet so that small in-app trades do not require a separate on-chain transaction per order.

2. Trade lifecycle

A user opens a market, selects YES or NO, and submits an order. The order is placed against Polymarket's CLOB through the official trading API using a builder-fee enabled signer. Fills are recorded in the user's PolyGram balance and a corresponding on-chain position is held in the user's behalf. When the market resolves, the underlying contract pays out $1 per winning share; PolyGram credits the user's balance once the resolution is final. Limit, market, and time-in-force (GTC, IOC, FOK) order types are supported; advanced types such as stop-loss and take-profit are implemented client-side and trigger market orders at the user-set price.

3. Custody & the PGUSD attribution layer

Working balances are held in a multi-signature treasury wallet on Polygon. To make balances auditable, PolyGram exposes a PGUSD attribution layer: an on-chain ledger that mirrors every deposit, trade, and withdrawal so users can verify that the total user-side liability equals the treasury's USDC holding. The PGUSD contract address is published in the site footer and can be inspected on PolygonScan at any time. PGUSD is not transferable, not tradeable, and not a token in the cryptocurrency sense — it is purely an accounting primitive.

4. Settlement & resolution

Market resolution follows the underlying UMA optimistic-oracle outcome on Polygon. PolyGram does not adjudicate market outcomes; we wait for UMA's two-hour dispute window to close and then mirror the on-chain resolution into user balances. This means PolyGram resolutions are deterministic, transparent, and trust-minimised: any disagreement about the outcome is resolved on-chain through the UMA dispute mechanism and is independent of PolyGram operational decisions.

5. Withdrawals

Users may withdraw their USDC balance to any Polygon wallet they control. Withdrawals are processed through the treasury signer; typical confirmation time is 30 minutes. Withdrawals are subject to identity verification and applicable AML/KYC procedures as set out in /terms. Network gas is paid by PolyGram below a per-transaction threshold; above that threshold, gas is deducted from the withdrawn amount.

6. Security model

Private keys are stored under AES-256-GCM encryption with scrypt-derived keys; in-memory buffers are zeroed after use. Treasury operations require multi-signature approval. Account-level controls include two-factor authentication (TOTP), session-level rate limits, withdrawal-address allowlists, and email confirmation on sensitive operations. Audits are performed by independent third parties on a recurring schedule.

7. Fees

PolyGram charges a small fee on trades; the fee is itemised on the trade ticket before confirmation. There is no platform fee on deposits. Withdrawals are free below the gas threshold described above. Bonuses, rakeback, and VIP-tier rewards are paid in real withdrawable USDC subject to a 2× trading-volume unlock — no clawback traps.

8. APIs & integrations

The PolyGram REST API exposes live odds, historical prices, order-book depth, and trade volume. A Server-Sent Events stream provides real-time price ticks and resolution events. White-label partners can use the same endpoints to power their own branded prediction-market front-ends with full custody handled by PolyGram. See /docs for technical documentation.