Skip to main content
In the product, this flow lives under Admin > Events > Calendar > Create Event. The form itself has 5 steps.

​
Before you start

Wallet, USDC, and POL

You need a connected EOA wallet. The flow checks both USDC and POL before it lets you continue.
The app fetches the required creator funding from market config and falls back to $5 USDC per market. This reward pays the UMA proposer who resolves the question correctly.
Your wallet must be listed in the allowed creator sources from General, otherwise the flow stops in the pre-sign step.
OpenRouter is required for the content checker and for the AI rules helper.

​
Step 1: Event

Basic event details

Add the event image, title, slug, resolution date, creator wallet, and categories.
Recurring events use title and slug templates, plus cadence. The resolution date shown in the form is always the date for the occurrence being generated.
When the main category is sports, extra fields appear: Games or Props, game start time, sport slug, league slug, home and away teams, abbreviations, and team logos.
Sports categories are generated automatically from the sports selections, so you do not manage them the same way as a regular event.

​
Step 2: Market Structure

Regular event types

Choose Binary, Multi-market with multiple true outcomes, or Multi-market with a single true outcome.
Sports events unlock templates such as Standard game lines, More Markets, Exact Score, Halftime Result, custom sports markets, and player props.
The custom mode lets you choose market type, question, title, short name, slug override, outcomes, line, group title, and optional team icon.
Props let you add player name, stat type, and line. Each prop becomes one generated market with Over and Under outcomes.

​
Step 3: Resolution

Resolution source URL

Optional, but useful when you already know the official source you want to cite.
Keep these clear and deterministic. Define source, UTC cutoff, tie handling, cancellation handling, and fallback logic.
The AI helper can draft rules, but you still need to review all text manually before publishing.
Recurring events also show preview samples for title, slug, and rules across occurrences, plus warnings when text looks too repetitive.

​
Step 4: Pre-sign checks

USDC reward check

The app checks whether the connected wallet has enough USDC for the UMA reward pool. The total grows with the number of markets being created, so multi-market events need more than a single binary market.
The same wallet also needs POL for the market creation transactions.
If the wallet is missing from your allowed creator sources, the flow offers a shortcut back to fix it.
Before signing, the app checks slug availability, confirms OpenRouter is active, and runs the content AI checker for language, rules, and consistency issues.

​
Step 5: Sign & Create

Auth challenge

First sign the EIP-712 auth challenge so the server can prepare the transaction plan.
Then approve the transactions required to create and register the markets.
After signatures are done, the server finalizes and registers the markets.
Allowed creator wallet errors usually point back to General. OpenRouter errors usually point to General too. Recurring events also require a configured server signer.
Keep the title and rules unambiguous, confirm the right creator wallet, and check the preview before you sign.