> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kuest.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Events

> Review events, manage visibility and context, configure sync behavior, and operate sports results.

<AccordionGroup>
  <Accordion title="Table and filters" icon="filter" defaultOpen>
    This page is for operating events that already exist. You can search by text and filter by main category, creator, series, and active-only status. The table also shows status, 24h and total volume, created date, and end date.
  </Accordion>

  <Accordion title="Visibility toggle" icon="eye-off">
    The eye icon hides or shows an event in public event lists. This does not delete the event. It only controls whether users can discover it on the site.
  </Accordion>

  <Accordion title="Livestream URL" icon="radio">
    The radio icon opens the livestream field for an event. Use it when you want the event page to link out to a live broadcast or live coverage page.
  </Accordion>

  <Accordion title="Additional Context" icon="notebook-pen">
    Add or remove event-specific context shown in the Rules area. This is separate from the AI-generated Market Context configured in [General](/admin/general#market-context).
  </Accordion>

  <Accordion title="Sports final status and source matching" icon="trophy">
    Sports moneyline events get a trophy action for the final score and ended state. When TheSportsDB or PandaScore is configured in [General](/admin/general#integrations), search for the source match, select a candidate, and review its provider IDs, league, confidence, score, and livestream data before saving. Synced source metadata is also used by sports-score automation.
  </Accordion>

  <Accordion title="Sync settings" icon="settings-2">
    The settings dialog controls whether newly synced events auto-deploy or stay manual until your team reviews them. Turn auto-deploy off if you want a human review step before new synced markets go live.
  </Accordion>

  <Accordion title="Calendar and manual creation" icon="square-plus">
    Click <strong>Create Event</strong> to open the calendar-based workflow documented below. The form creates the event and its prediction markets together.
  </Accordion>
</AccordionGroup>

## Create Event

<Info>
  In the product, this flow starts from **Admin > Events > Create Event** and opens the event calendar. The form has 5 steps.
</Info>

### Before you start

<AccordionGroup>
  <Accordion title="Wallet, USDC, and POL" icon="wallet" defaultOpen>
    You need a connected EOA wallet. The flow checks both USDC and POL before it lets you continue.
  </Accordion>

  <Accordion title="USDC resolution funding" icon="coins">
    The app fetches the required USDC amount from market config and falls back to `$5 USDC` per market. In the current Direct mode this is an on-chain direct-resolution fee; in UMA mode it funds the proposer reward.
  </Accordion>

  <Accordion title="Allowed creator wallet" icon="user-check">
    Your wallet must be listed in the allowed creator sources from [General](/admin/general), otherwise the flow stops in the pre-sign step.
  </Accordion>

  <Accordion title="Resolution proposers whitelist" icon="user-check">
    The creator wallet needs an on-chain proposer whitelist before creating markets. It controls the trusted wallets that can submit results for Direct resolution and propose outcomes when UMA mode is available.
  </Accordion>

  <Accordion title="OpenRouter" icon="sparkles">
    OpenRouter is required for the content checker and for the AI rules helper.
  </Accordion>
</AccordionGroup>

### Step 1: Event

<AccordionGroup>
  <Accordion title="Basic event details" icon="file-text" defaultOpen>
    Add the event image, title, slug, resolution date, creator wallet, and categories.
  </Accordion>

  <Accordion title="Recurring events" icon="repeat">
    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.
  </Accordion>

  <Accordion title="Sports extra fields" icon="trophy">
    When the main category is `sports` or `esports`, extra fields appear for Games or Props, start time, sport and league, teams, abbreviations, and logos. If a sports provider is configured in [General](/admin/general#integrations), search for a source match or enter its provider IDs manually so scores can sync later.
  </Accordion>

  <Accordion title="Sports categories" icon="tags">
    Sports categories are generated automatically from the sports selections, so you do not manage them the same way as a regular event.
  </Accordion>
</AccordionGroup>

### Step 2: Market Structure

<AccordionGroup>
  <Accordion title="Regular event types" icon="layout-grid" defaultOpen>
    Choose Binary, Multi-market with multiple true outcomes, or Multi-market with a single true outcome.
  </Accordion>

  <Accordion title="Sports templates" icon="trophy">
    Sports events unlock templates such as Standard game lines, More Markets, Exact Score, Halftime Result, custom sports markets, and player props.
  </Accordion>

  <Accordion title="Custom sports markets" icon="sliders-horizontal">
    The custom mode lets you choose market type, question, title, short name, slug override, outcomes, line, group title, and optional team icon.
  </Accordion>

  <Accordion title="Player props" icon="users">
    Props let you add player name, stat type, and line. Each prop becomes one generated market with Over and Under outcomes.
  </Accordion>
</AccordionGroup>

### Step 3: Resolution

<AccordionGroup>
  <Accordion title="Resolution source URL" icon="link" defaultOpen>
    Optional, but useful when you already know the official source you want to cite.
  </Accordion>

  <Accordion title="Resolution rules" icon="scroll-text">
    Keep these clear and deterministic. Define source, UTC cutoff, tie handling, cancellation handling, and fallback logic.
  </Accordion>

  <Accordion title="Generate with AI" icon="sparkles">
    The AI helper can draft rules, but you still need to review all text manually before publishing.
  </Accordion>

  <Accordion title="Recurring preview" icon="eye">
    Recurring events also show preview samples for title, slug, and rules across occurrences, plus warnings when text looks too repetitive.
  </Accordion>
</AccordionGroup>

### Step 4: Pre-sign checks

<AccordionGroup>
  <Accordion title="Resolution mode" icon="scale" defaultOpen>
    Direct resolution is currently used for new markets: approved proposers submit the final result directly. UMA remains visible in the selector but is temporarily unavailable in the admin flow.
  </Accordion>

  <Accordion title="USDC funding check" icon="coins">
    The app checks whether the connected wallet has enough USDC for the active resolution mode. In Direct mode this pays the direct-resolution fee. The total grows with the number of markets, so multi-market events need more than a single binary market.
  </Accordion>

  <Accordion title="POL gas check" icon="fuel">
    The same wallet also needs POL for the market creation transactions.
  </Accordion>

  <Accordion title="Allowed creator wallet check" icon="user-check">
    If the wallet is missing from your allowed creator sources, the flow offers a shortcut back to fix it.
  </Accordion>

  <Accordion title="Resolution proposers whitelist" icon="user-check">
    The flow checks whether the selected creator wallet already has a proposer whitelist. If it does not, click **Create whitelist** and sign with the creator wallet before continuing. Existing whitelists can be managed from the same check.
  </Accordion>

  <Accordion title="Slug, OpenRouter, and content checks" icon="shield-check">
    Before signing, the app checks slug availability, confirms OpenRouter is active, and runs the content AI checker for language, rules, and consistency issues.
  </Accordion>
</AccordionGroup>

### Resolution proposers

<Warning>
  Only add wallets you trust. A proposer can submit outcomes for markets created by that creator wallet.
</Warning>

Use **Admin > Events > Calendar > Proposers** to manage the wallets allowed to submit results for markets created by each creator wallet.

<Steps>
  <Step title="Create the whitelist">
    Select the creator wallet and click **Create whitelist** if no whitelist exists yet. This deploys the creator-owned whitelist contract.
  </Step>

  <Step title="Register it on-chain">
    The creator wallet registers that whitelist in the proposer whitelist registry. Market creation checks this registry before continuing.
  </Step>

  <Step title="Add proposer wallets">
    Add the trusted wallets that can submit Direct results or propose UMA outcomes for this creator. You can add or remove proposers later; open unresolved markets use the current on-chain list.
  </Step>
</Steps>

The modal lets you:

* Select a creator wallet from the allowed market creator wallets.
* Create the creator's on-chain whitelist if it does not exist yet.
* Add one wallet or many wallets at once, separated by commas.
* Remove a wallet whenever you no longer want it proposing outcomes.

The whitelist is read live on-chain when a market is resolved. If you add a proposer tomorrow, that wallet can also resolve older open markets created by the same creator wallet. If you remove a proposer, that wallet loses proposer access for unresolved markets from that creator.

<Info>
  The bond and reward requirements apply only when using UMA. UMA proposers need USDC for the bond/final fee and POL for gas; Direct mode does not use the UMA bond flow.
</Info>

### Step 5: Sign & Create

<AccordionGroup>
  <Accordion title="Auth challenge" icon="file-signature" defaultOpen>
    First sign the EIP-712 auth challenge so the server can prepare the transaction plan.
  </Accordion>

  <Accordion title="Transaction plan" icon="list-checks">
    Then approve the transactions required to create and register the markets.
  </Accordion>

  <Accordion title="Finalize" icon="check-circle-2">
    After signatures are done, the server finalizes and registers the markets.
  </Accordion>
</AccordionGroup>

<AccordionGroup>
  <Accordion title="If the flow gets blocked" icon="triangle-alert">
    Allowed creator wallet errors usually point back to [General](/admin/general). OpenRouter errors usually point to [General](/admin/general) too. Recurring events also require a configured server signer.
  </Accordion>

  <Accordion title="What matters most in practice" icon="star">
    Keep the title and rules unambiguous, confirm the right creator wallet, and check the preview before you sign.
  </Accordion>
</AccordionGroup>