What is the ParlayMarket App?

The ParlayMarket App is a parlay construction and execution workspace for prediction markets. It lets users compose multi-leg tickets, simulate combined probabilities, and prepare execution plans before submitting transactions.

How do parlay tickets work?

A parlay ticket combines multiple market outcomes into one position. The combined result depends on all included legs, and projected payout is calculated from the selected prices and stake with transparent math in the interface.

Is real money execution enabled?

Execution depends on the connected wallet, network, and current deployment settings. The app can provide simulation and planning flows, while live transaction submission is controlled by configured runtime and access gates.

How is execution handled safely?

Execution flows are designed to be explicit and auditable, including deterministic ticket data, plan hashes, signature checks, and server-side policy gates. Users review details before any transaction is sent.

Who can execute trades?

Only eligible connected wallets can submit execution requests, and deployment-level authorization controls can further restrict who is allowed to execute intents and settlement actions.

Step 1 · Select legs

Markets explorer

0 markets

Browse normalized markets and add outcomes as legs to your parlay. This list is populated from a venue adapter feed (via Worker) and rendered locally.

Data stream status

fetch_url

status

parse_type

markets_count

fallback

fallback_reason

fetched_count

worker_status

error

Developer tools

Wallet events and resolver API responses appear here to aid QA without opening browser DevTools.

Step 2 · Build slip

Parlay slip

0 legs

Add one or more legs, choose a stake, and let the app compute composite odds, implied probability, and projected payout. This runs entirely in the browser.

Config: Max 8 legs · no correlated checks

Local pricing only

No legs yet. Use the markets panel to add outcomes. This slip will display each leg’s market, outcome, price, and cutoff time, plus remove controls.

Stake

Currency: USDC (simulated)

Composite odds 0.00

Implied probability: 0.0% Legs: 0

Projected payout: 0.00 Stake: 100

Composite odds = 1 / (joint probability of all legs), under an independence assumption. Projected payout = stake × composite odds. Demo app uses static probabilities from the adapter feed.

The JSON contract in the right column stays in sync as you modify legs or stake. This is the object a backend or resolver would ingest.

Step 3 · Export ticket

Ticket contract

Schema: parlaymarket-ticket-v0.2

This panel shows the structured parlay ticket JSON, including leg identifiers, locked prices, and simple pricing metrics. Copy this into a resolver or backend for quoting or settlement experiments.

Owner

—

EIP-712 signer

Ticket hash

—

Deterministic digest

Signature status

Unsigned

No signed payload detected

Ticket save status: —

Username (optional)

3–24 characters, letters/numbers/underscore only. Captured before signing.

Ticket JSON

Generated locally from current slip state. Ticket IDs are illustrative.

{
  "ticket_id": "pm-local-placeholder",
  "ticket_hash": "0x...",
  "created_at": "…",
  "owner": null,
  "stake_ccy": "USDC",
  "stake_size": 100,
  "legs": [],
  "composite_price_decimal": 0,
  "projected_payout": 0,
  "implied_combined_prob": 0,
  "notes": "no legs selected",
  "version": "parlaymarket-ticket-v0.3"
}

Execution Plan

Deterministic, read-only plan for executing the ticket on Polymarket.

Plan hash

—

Keccak256 digest

Total max cost

—

USDC allocation

Legs

—

Execution steps

Intent Transaction

Plan pending.

To —

Function —

Ticket hash —

Plan hash —

Tx hash —

Settlement Transaction

Settlement pending.

To —

Outcome —

Payout —

Tx hash —

Float / spread

0 bps

Simulated overround or internal spread. Extend this logic to model operational edge.

Ticket hash

n/a

Keccak256 over canonicalized ticket JSON.

Adapter notes

The app is designed so that a backend / adapter can:

Serve normalized markets to the app (instead of static JSON).
Receive this ticket object on a /api/quote or /api/float endpoint.
Respond with a live quote ID and expiry for execution.

Markets explorer

Parlay slip

Historical leaderboard

Resolver Playground (Beta)

Create Chain

Get Chain

Settle Chain

Ticket Simulation (Beta)