Methodology
How we source and check drawing facts
Every money figure and winning-number claim on megapot.blog is tied to a verified drawing record. This page explains the pipeline in plain language.
1. Sources
- Megapot Data API (api.megapot.io): round summaries, ticket counts, and prize-tier payouts for each drawing.
- Megapot Jackpot contract on Base (chain id 8453): on-chain state for the same drawing, including winning ticket and settlement timing.
- megapotresults.com facts files: the network archive that stores one
verified JSON record per drawing at
data/facts/drawings/{n}.json, and publishes the human page at megapotresults.com/drawing/N.
2. Checks before publish
- Drawing status must be verified (not provisional).
- Winning numbers, ticket counts, and tier payouts in the recap must match the facts file.
- Recap posts in this repo carry front-matter flags (
fact_checked: trueand asources[]list). The Astro build refuses posts that omit them. - USD amounts shown to readers are on-chain integer units divided by 1,000,000 (USDC 6 decimals), the same conversion megapotresults.com uses.
3. What we publish vs what we leave out
- We publish aggregated drawing results and truncated public winner tables when the archive does.
- We do not put referral codes, wallet secrets, or invite codes in page HTML.
- Play links always go through
/gowithrel="sponsored nofollow". - We do not publish predictions, pressure copy, or claims that a number is about to hit.
4. Corrections
If a published figure is wrong, we update the page and note the change. The canonical numeric record remains the megapotresults.com drawing page for that number. For methodology questions, start with megapotresults.com/about.
5. Weekly reports
Weekly reports (drafts first, then edited) sum verified drawings for a Monday-Sunday UTC week: tickets, winning tickets, prize-pool range, and the largest single-ticket net payout. Every row cites a facts file and the live drawing URL. Drafts are not live until a human editor clears them.