project screenshot 1
project screenshot 2
project screenshot 3
project screenshot 4
project screenshot 5
project screenshot 6

Prove Me Wrong

Tag ProveMeWrong on X. Bet YES/NO in-tweet; AI resolves, contract pays

Prove Me Wrong

Created At

ETHGlobal Cannes

Winner of

Flare Network

Flare Network - MAIN TRACK: use protocols on Flare blockchain 3rd place

Project Description

Instant, autonomous prediction markets. 🔮⚡️

Prove Me Wrong lets anyone turn a tweet into a mini “bet me” arena. You write a claim (“Bitcoin will top $150 k by 2026”), tag ProveMeWrong, and publish. A small widget pops up under the tweet so friends can tap YES or NO with their crypto wallet. Behind the scenes a swarm of AI agents keeps watch on news sites, block-explorers and official APIs. The moment fresh, reliable evidence appears, the agents decide the outcome, set the odds as more votes come in and time progresses then after a resolution is found the Flare smart contract pays winners automatically.

No moderators, no waiting—just tweet, bet, and let the bots settle it. 🔮⚡️

How it's Made

🏗️ Architecture Overview • Market Generator – CLI/API that posts a claim, writes it to DB, mints YES/NO pools and LP vaults on Flare. • Browser Extension – scans every X.com timeline for prove-me-wrong tweets authored by the viewer; swaps the tweet’s link for an inline React widget with live odds and a custom WalletConnect button. • Market Coordinator – Railway-friendly daemon thread that polls open markets hourly and sends IDs to the Resolver via uAgent messaging. • Market Resolver – AI pipeline (ASI-1 Mini + scraper) that decides outcomes and pushes signed results on-chain.

🤖 AI-Powered Resolution • ASI-1 Mini API – custom prompt chain: search latest evidence → reason → JSON verdict + confidence. • Scraping fallback – aiohttp + BeautifulSoup behind a Cloudflare-Workers proxy when sites block requests. • Evidence links + reasoning pinned to IPFS; hash stored in the verdict TX for auditability.

⚡ Real-Time Orchestration • Coordinator thread (instead of cron) keeps Railway happy. • uAgents mesh • manager_agent broadcasts UAResolutionRequest for every open market. • resolver_agent gathers evidence, calls ASI-1 Mini, signs and returns UAReply. • P2P redundancy & Innovation-Lab compliance baked in.

🌐 Blockchain Layer (Flare) • Bonding-curve AMM for YES/NO tokens. • Contracts trustlessly read the signed verdict and release payouts. • Ready to consume Flare Data Connectors.

💾 Storage • SQLite for local hacking, PostgreSQL on Railway—same SQLAlchemy models in Generator and Resolver. • Resolutions auto-archived after 30 days.

🔗 Service-to-Service API • All internal calls are JSON over HTTPS on one Railway domain (/gen, /res, /agent). • Keeps deployment, SSL and env-var juggling trivial.

🚀 Deployment & Tooling • Docker multi-stage images: generator, resolver, extension build, front-end docs. • Railway handles container hosting, secrets and auto-scaling. • GitHub Actions ships to Railway and tags Docker Hub nightly.

🎯 Notable Tech Decisions 1. Browser-extension overlay sidesteps Twitter’s iframe limits while keeping UX fully in-tweet. 2. Cloudflare-Worker proxy eliminates CORS and per-origin throttle on scrapes. 3. uAgent abstraction means any third party can spin up their own resolver and challenge or mirror ours—true decentralisation of truth.

🔑 Stack Summary • Backend: FastAPI · SQLAlchemy · Python async/await • AI: ASI-1 Mini · BeautifulSoup • Agents: uagents 0.11 (manager_agent, resolver_agent) • Blockchain: Solidity · Web3.py · Flare Network • DB: SQLite (dev) · PostgreSQL (prod) • Extension/Front-end: React · Tailwind · custom WalletConnect • Deploy: Docker · Railway

background image mobile

Join the mailing list

Get the latest news and updates