\n \n \n \n \n \n

\n \n

Experiments in Prediction Probabilities as a Consumer Product

\n \n

The Two Audiences Problem

\n \n

\n Prediction markets are on the rise, but there are actually two distinct demographics that can make use of them: those who bet on them, and the much larger percentage of people who might consume them for information. Think of it like the distinction between journalists and news consumers – a small circle of creators serving a much larger circle of consumers.\n

\n\n

\n Currently, prediction market platforms serve bettors, which makes sense and is needed for the markets to be useful at all. But these platforms are dizzying to the average person and look nothing like how they normally consume news. We've made progress on the first challenge – attracting traders and liquidity – but what doesn't appear to have been established is how to translate that generated data into something consumable by the average informed citizen.\n

\n\n \n

\n $\"Platform$ \n $\"Platform$ \n $\"Platform$ \n

Bettor friendly maybe. Normie friendly? Not so much.

\n\n

\n Prediction markets won't become mainstream until they're packaged in a way that appeals to folks who are unlikely to consider betting on them.\n

\n\n

\n My instinct: instead of trying to aggregate many predictions about many events, get one really good page going for one single topic, then expand from there.\n

\n\n

The Deep Dive Approach

\n\n

\n Picture this: the best page on the internet for understanding \"When will the war in Ukraine end?\" Every time the market moves, we research why it moved, building a digestible narrative from that movement.\n

\n\n

\n When odds shift from 15% to 23% for \"war ends by December 2024,\" readers don't just see numbers – they get context. What news broke? Which analysts are talking? What historical parallels apply?\n

\n\n

Russia Timeline Prototype:

\n $\"Russia$ \n

\n\n

\n (This would probably work brilliantly as a newsletter format too – imagine getting a weekly digest that not only tells you how the market moved, but why it moved and what that means.)\n

\n\n

From Prototype to Proof of Concept

\n\n

\n I built a single-page treatment for my prediction market about the USA World Cup roster. Instead of covering every sport, I went deep on one question that soccer fans genuinely care about.\n

\n\n

\n USA World Cup Roster Prediction Market\n \n

\n \n

\n\n

Why This Works

\n\n

\n The traditional aggregator approach: you need lots of markets to be useful, but you need users to make markets liquid. By starting with one exceptional page, you can perfect the format, build expertise, and create something people actually bookmark.\n

\n\n

Tools for Building Bespoke Market Pages

\n\n

\n I built a site where you can add URLs from Manifold or Polymarket markets, and it creates a dashboard that shows them all nicely formatted.\n

\n\n

\n The Rundown - Market Dashboard Maker\n \n

\n \n

\n\n

\n I also built a bot (@manifoldmaven) that tweets whenever a Manifold market moves by more than 35%. Manifold Maven itself is just another aggregator of prediction markets, of course, but it does make an attempt to show the \"story\" of the day by only tweeting markets that have moved significantly. It also exists in the context of Twitter, meaning that as you're seeing lots of editorialization (maybe too much), you're also getting pieces of more solid probabilities. Prediction market platforms have the opposite problem in that sense.\n

\n\n \n

Market: Will Musk still be on good terms with Trump at the end of 2025? (URL: https://t.co/UNd3aifXFl)
Change: 42.8% down
From: 48.2% to 5.4%
Duration: 3 hours
— manamaven (@manifoldmaven) June 5, 2025

\n \n

\n\n

The Bigger Picture

\n\n

\n We don't want to be overwhelmed with data, we want to be informed by intelligence. The difference between showing someone a market price and helping them understand what that price means is the difference between a tool and a service.\n

\n\n

\n Sometimes the best way to aggregate everything is to start by perfecting something.\n

\n\n

\n What do you think? Are there specific markets or topics where this deep-dive approach could work particularly well? I'd love to hear from other folks pursuing interesting ideas in this space.\n

\n\n \n\n",[],[192],{"_105":199,"_95":100,"_156":200,"_158":-5,"_159":139,"_160":161,"_162":163,"_107":201,"_101":32,"_165":202,"_167":203,"_169":22,"_170":-5,"_171":204,"_99":205},"0c359af0-46d7-11f0-a914-76b3cceeab13","32c4e6bc-fb08-4602-a994-7832c4ce30f6",["D",1749654988511],"http","import { readFile } from \"https://esm.town/v/std/utils/index.ts\";\nimport { sqlite } from \"https://esm.town/v/stevekrouse/sqlite\";\n\nconst EMAIL_TABLE = 'prediction_blog_emails_v1';\n\n// Initialize database table\nasync function initDatabase() {\n await sqlite.execute(`CREATE TABLE IF NOT EXISTS ${EMAIL_TABLE} (\n id INTEGER PRIMARY KEY AUTOINCREMENT,\n email TEXT NOT NULL UNIQUE,\n pred_markets BOOLEAN DEFAULT 0,\n build_moi BOOLEAN DEFAULT 0,\n charlie_updates BOOLEAN DEFAULT 0,\n frequency TEXT DEFAULT 'weekly',\n created_at DATETIME DEFAULT CURRENT_TIMESTAMP\n )`);\n}\n\nexport default async function(req: Request): Promise {\n const url = new URL(req.url);\n \n // Handle email signup\n if (url.pathname === \"/api/signup\" && req.method === \"POST\") {\n try {\n await initDatabase();\n \n const data = await req.json();\n const { email, preferences, frequency } = data;\n \n // Insert or update email subscription\n await sqlite.execute(`\n INSERT OR REPLACE INTO ${EMAIL_TABLE} \n (email, pred_markets, build_moi, charlie_updates, frequency) \n VALUES (?, ?, ?, ?, ?)\n `, [\n email,\n preferences.predMarkets ? 1 : 0,\n preferences.buildMoi ? 1 : 0,\n preferences.charlieUpdates ? 1 : 0,\n frequency\n ]);\n \n return new Response(JSON.stringify({ success: true }), {\n headers: {\n \"Content-Type\": \"application/json\",\n \"Access-Control-Allow-Origin\": \"*\",\n },\n });\n } catch (error) {\n console.error('Email signup error:', error);\n return new Response(JSON.stringify({ \n success: false, \n error: 'Failed to save email' \n }), {\n status: 500,\n headers: {\n \"Content-Type\": \"application/json\",\n \"Access-Control-Allow-Origin\": \"*\",\n },\n });\n }\n }\n \n // Get all emails (for future access)\n if (url.pathname === \"/api/emails\" && req.method === \"GET\") {\n try {\n await initDatabase();\n const result = await sqlite.execute(`SELECT * FROM ${EMAIL_TABLE} ORDER BY created_at DESC`);\n \n return new Response(JSON.stringify(result), {\n headers: {\n \"Content-Type\": \"application/json\",\n \"Access-Control-Allow-Origin\": \"*\",\n },\n });\n } catch (error) {\n console.error('Get emails error:', error);\n return new Response(JSON.stringify({ \n success: false, \n error: 'Failed to retrieve emails' \n }), {\n status: 500,\n headers: {\n \"Content-Type\": \"application/json\",\n \"Access-Control-Allow-Origin\": \"*\",\n },\n });\n }\n }\n \n // Serve contributors JSON\n if (url.pathname === \"/contributors.json\") {\n const contributors = await readFile(\"/contributors.json\", import.meta.url);\n return new Response(contributors, {\n headers: {\n \"Content-Type\": \"application/json\",\n \"Access-Control-Allow-Origin\": \"*\",\n },\n });\n }\n \n // Serve main HTML\n const html = await readFile(\"/index.html\", import.meta.url);\n \n return new Response(html, {\n headers: {\n \"Content-Type\": \"text/html\",\n },\n });\n}",[],[100],"files",[153,174,182,190,198],"counts",{"_210":32,"_211":212,"_213":161,"_214":215},"pulls","branches",7,"forks","envVars",{"_216":32,"_217":32},"count","emptyCount","contents",[],{"_105":199,"_95":100,"_156":200,"_158":-5,"_159":139,"_160":161,"_162":163,"_107":221,"_101":32,"_165":202,"_167":203,"_169":22,"_170":-5,"_99":222},["D",1749654988511],[100],"upstreamProject","upstreamBranch",{"_105":142,"_107":226,"_227":228,"_95":43,"_140":106,"_101":144,"_141":-5,"_143":-5,"_229":230,"_109":-5,"_150":22,"_111":112,"_149":94,"_16":120,"_148":96},["D",1749584342693],"updatedAt",["D",1749654671446],"lockfileKey","1756537636967-esm.town_v_dcm31_marketnewsblogpost@23-main","emptyEnvVars","isNew","flags",[],"routes/_app.x.$handle.$name.branch.$branch.version.$version.code.$",{"_93":94,"_95":96,"_97":98,"_101":102,"_99":100,"_103":237,"_151":242,"_206":258,"_166":259,"_218":262,"_263":264,"_267":-5,"_268":269,"_270":32,"_271":272},{"_105":106,"_95":96,"_107":238,"_109":-5,"_110":22,"_111":112,"_113":-5,"_114":-5,"_14":115,"_116":-5,"_117":22,"_118":-5,"_119":32,"_16":120,"_121":122,"_123":122,"_124":125,"_126":125,"_127":125,"_128":122,"_129":122,"_23":239,"_133":240,"_136":241,"_150":22},["D",1749584342693],{"_93":94,"_131":132},{"_93":94,"_135":132},{"_101":138,"_95":98,"_105":139,"_140":106,"_141":142,"_143":144,"_145":112,"_146":106,"_147":120,"_148":96,"_149":94},[243,246,249,252,255],{"_105":154,"_95":155,"_156":157,"_158":-5,"_159":139,"_160":161,"_162":163,"_107":164,"_101":32,"_165":166,"_167":168,"_169":22,"_170":-5,"_171":244,"_99":245},[],[155],{"_105":175,"_95":176,"_156":177,"_158":-5,"_159":139,"_160":161,"_162":163,"_107":178,"_101":32,"_165":166,"_167":179,"_169":22,"_170":-5,"_171":247,"_99":248},[],[176],{"_105":183,"_95":184,"_156":185,"_158":-5,"_159":139,"_160":161,"_162":163,"_107":186,"_101":32,"_165":166,"_167":187,"_169":22,"_170":-5,"_171":250,"_99":251},[],[184],{"_105":191,"_95":192,"_156":193,"_158":-5,"_159":139,"_160":102,"_162":22,"_107":194,"_101":161,"_165":166,"_167":195,"_169":22,"_170":-5,"_171":253,"_99":254},[],[192],{"_105":199,"_95":100,"_156":200,"_158":-5,"_159":139,"_160":161,"_162":163,"_107":201,"_101":32,"_165":202,"_167":203,"_169":22,"_170":-5,"_171":256,"_99":257},[],[100],[243,246,249,252,255],{"_105":199,"_159":139,"_156":200,"_95":100,"_167":203,"_165":202,"_101":32,"_158":-5,"_107":260,"_160":161,"_170":-5,"_99":261},["D",1749654988511],[100],[],"upstream",{"_105":142,"_107":265,"_227":266,"_95":43,"_140":106,"_101":144,"_141":-5,"_143":-5,"_229":230,"_109":-5,"_150":22,"_111":112,"_149":94,"_16":120,"_148":96},["D",1749584342693],["D",1749654671446],"pull","ahead",10,"behind","templates",[],"actionData","errors"]