mikodes.stack
3 surfaces builder code: not set non-custodial

One ladder. Three surfaces.
One builder code, planned.

What ships today: the Scanner checks Kalshi prices for differences in pricing on historical data, and the Terminal is a read-only view of on-chain Polymarket fills and builder attribution on Polygon. Order signing with a builder fee, where the user signs with their own wallet, is specified, not built. The Bot has no code yet: its planned settings live in the operator admin (MIKODES Admin Kit), which runs on the operator's machine, not on this site. No relayer, no server key, nothing custodial.

?
Order book: unknown. Waiting for board.json.
?
Market titles: unknown. Waiting for tape.json.
?
Cross-venue: unknown. Waiting for board.json.
Kalshi markets ingested
On-chain notional in window
Fees charged in window
Builder codes seen
The ladder

Each surface is planned to hand the user to the next

Previews below are the real pages, loaded from this folder. Click one to open it. The hand-offs between them are not built yet.

Analytics · no keys

Spread Scanner

01
Kalshi ingestion on a scheduled runner, every fee counted on every leg, and a pair matcher that vetoes contracts about different subjects. A hand-off to the Terminal is planned, not built.
scanner-prototype/public/index.html
Open ↗
Markets
Checks run
Pairs
Open board
On-chain analytics · read-only

Prediction Terminal

02
Today: a read-only view of Polymarket fills, fees and builder attribution, read from Polygon because builder is a field in OrderFilled. Planned: orders the user signs with their own wallet, carrying the builder code. No order form or wallet connect exists yet.
terminal-prototype/public/index.html
Open ↗
Fills
Traders
Attributed
Open console
Distribution · no bot code yet

Prediction Bot

03
Planned: Telegram alerts with no Mini App and no keys, because Telegram's terms forbid signing an Ethereum transaction inside one. No bot code exists yet. Its settings (username, channel, send-rate budget, Mini App check) are in the operator admin; the public page only says where they moved. Requirements are in BOT-SPEC.md.
bot-prototype/public/index.html
Open ↗
Mini App
none
Keys held
none
Guards
3 required
Open bot page no bot code yet
Proof ledger

What is proven, and what is not

Status is read from the data files where one exists. Nothing is marked proven because it is written in a spec.

Claims

ClaimSurfaceStatus

Largest on-chain fills

Polygon

Largest spreads after fees

Kalshi
Only events where every outcome is listed, so one leg must pay. Single-venue check on historical data; not a cross-venue result.
No figure on this page is seeded, mocked or placeholder. Counts, amounts and statuses are read from scanner-prototype/public/board.json and terminal-prototype/public/data/tape.json; operator settings (brand, builder code, links) from config/public.json when it exists. Fixed facts from a spec (the Bot's three required guards, no Mini App, no keys) are labelled as spec. Where something is unknown it says unknown. Nothing here promises a return.