Pari

Where it runs

Discord first. Everywhere a link goes after that.

Pari lives inside Discord. Everything else is a way for a market or a result to travel: a page, a board on a television, a card that unfurls when somebody pastes the link. Each surface below carries the same status vocabulary as the roadmap, so nothing here reads as a promise.

Shipped runs today · Building is in progress and visibly incomplete · Planned is specified with nothing running · Exploring is research, not a commitment

The only thing anyone installs is the Discord app, and removing it takes two clicks. Everything else on this page is a link, a page, or an image — nothing that asks for a permission.

A real share card
A Pari share card: a ticket with a stub column reading PARI, TEST POINTS and market #12 on pari-house, and a body with the question "Will this stream hit 10K viewers tonight?", the lock time, a YES row at 62% of pool paying about 1.58x with 26 stakers, the pool total, and the lifecycle strip.
Rendered by the repository’s own card renderer (packages/share) from the same market as the demo above, at 1200×630. The square and story sizes exist too, for the surfaces that want them.
  • 01DISCORD

    Discord

    The product. Markets, cards with stake buttons, claims, form, leaderboards — all inside the channel.

    Slash commands over HTTP, no gateway connection and no privileged intents. One click to add.

    Shipped

  • 02WEB

    Web

    Grandstand: market pages, the purse, the board, your form. Live on the test network today.

    Reads the chain directly rather than a database. Being finished, and the roadmap says so until it is.

    Building

  • 03TV AND STREAM OV

    TV and stream overlay

    The board route at 1920, for a living-room screen or an OBS browser source. Read-only, no interaction.

    Minimum 32 px type and 7:1 contrast so it reads from three metres. Verified in the design lab gates.

    Shipped

  • 04SHARE CARDS

    Share cards

    A market or a result as a ticket image at 1200×630, 1080×1080 and 1080×1920, so a pasted link unfurls properly.

    One renderer in TypeScript (packages/share) and the same renderer in Rust behind an Open Graph service (crates/billboard), checked against each other fixture by fixture.

    Building

  • 05ONE-TAP SHARE

    One-tap share

    Share a market or a claim straight to X, Telegram, WhatsApp, Discord or Snapchat.

    Plain web share links, no SDK and no tracking pixel. Your position is never in a share: what you send is what a stranger already sees.

    Building

  • 06SNAPCHAT

    Snapchat

    Share to Snapchat with a link sticker, and Snap Login as a third way to link an identity.

    Pari does not run inside Snapchat and will not: Snap Minis and Snap Games were both discontinued in 2023, so there is no third-party app surface in the chat any more. What is left is Creative Kit for sharing out and Login Kit for identity. We share to Snapchat; we do not live there.

    Planned

  • 07TELEGRAM

    Telegram

    A mirror of the same handlers: the same commands, inline keyboards instead of buttons, group markets.

    Specified and not built. There is no waitlist and nothing to sign up for — use Discord today and this will arrive beside it.

    Planned

  • 08TIKTOK AND YOUTU

    TikTok and YouTube

    Clip and post a resolved market: the question, the pool at lock, and what happened, as a story-shaped card.

    TikTok does not unfurl links, which is why the story card prints the market address on the image itself.

    Planned

  • 09ROBLOX AND CLASS

    Roblox and classroom platforms

    Research only, for a future Kids Mode. A prototype of the classroom interface exists; none of it is a shipping claim.

    Nothing here is committed, dated or sold. It is on this page so the list is complete rather than flattering.

    Exploring

Statuses were checked against the repository on . If a surface here matters to you, say so in the roadmap thread rather than waiting for it quietly.