Events

An event is an organizational container that groups related prediction markets together under a single title, description, and cover image. Instead of browsing individual markets one by one, events let you discover a curated set of questions around a shared topic.

​

Events and markets

A market is where bets are placed. An event is simply a wrapper around one or more markets.

• One event can contain many markets
• Each market belongs to at most one event
• Betting always happens at the individual market level, not on the event itself
• An event must have at least two markets when it is created

Example: An event titled “SOL Price Weekly” might contain separate YES/NO markets for different price thresholds, all grouped together for easy discovery.

​

Event statuses

​

Browsing events

The Events page lists all active events sorted by creation date. Each event card shows:

• Cover image (or a procedurally generated gradient if none is set)
• Event title and description
• Status badge
• Creation date

Clicking a card opens the event’s markets page, where you can filter markets by status and navigate into individual market detail pages to place bets.

​

Creating an event

Any connected wallet can create an event. The creation wizard walks you through four steps.

​

Step 1: Details

Provide the event’s basic information:

• Title: A clear, descriptive name (max 200 characters)
• Slug: A URL-safe identifier used in the event’s link (e.g., sol-price-weekly). The slug is auto-generated from the title and is permanent once set.
• Description: Optional context about what this event covers (max 2000 characters)
• Cover image URL: Optional image shown on the event card and hero section

​

Step 2: Settings

Choose a default policy for markets in this event. The policy controls parameters like minimum bet size and fee rates. Individual markets can override this default during creation.

​

Step 3: Markets

Add at least two markets to the event. For each market, provide:

• Question: A clear YES/NO question
• Closing time: When betting stops for that market
• Liquidity: The initial pool backing from your creator bond
• Policy override: Optional per-market policy if it differs from the event default

Markets can be added, edited, or removed during this step before submission.

​

Step 4: Review

Confirm all details before submitting. On submission, Flew:

1. Creates the event record
2. Creates each market on-chain via Arcium
3. Links all markets to the event

Progress is shown inline: “Creating event… Creating market 1 of 3… Linking markets to event…”

​

Managing an event

After creation, the event creator can update:

• Title
• Description
• Cover image
• Status (active, closed, archived)

The slug cannot be changed after creation, as it forms the permanent URL for the event. Additional markets can be linked to an existing event at any time via the event management interface.