Introduction
Denpa is not a channel network. Denpa is a broadcast protocol where every prediction market becomes a programmable live media surface.
denpa.ai — one surface: picture, market, chart, channels.
Broadcast television binds media to a channel and a clock. Streaming binds media to a file or a creator. Neither binds media to a question that resolves. A prediction market is the first media object that arrives with a price, a settlement date and an oracle built in: a programme with its ending already scheduled.
Denpa gives every such market one addressable surface — https://denpa.ai/m/[marketId] — and defines what can happen on it:
- Operators bind live streams to it, so the video becomes that market’s live context.
- Anyone files a SIGNAL on it: a timestamped YES/NO call, locked with a snapshot of the market at that instant.
- A program clock airs it. Airing is a protocol event with a timestamp and a reason.
- The market resolves through its own oracle; signals settle; scores are stamped.
- Receipts record who broadcast on it, when, and to how many.
What Denpa is not
Section titled “What Denpa is not”- Not a betting product. The word on every surface is SIGNAL, never BET. Signals, scores and airtime are informational — never a recommendation, solicitation or advice to trade. Trades, where they exist, happen on the provider at the user’s own risk.
- Not a wallet-first product. Signal creation never requires a wallet. The signal layer never depends on the settlement rail.
- Not a set of channels. Channels CH0–CH9 were archived on 2026-06-10. A channel is a market; the schedule is a function of what resolves next.
The routing rule
Section titled “The routing rule”Forks own their surface — brand, theme, market scope, domain. Traffic, identity, receipts, stream binding and market context resolve through denpa.ai. A fork that re-implements binding or mints its own receipts is off-protocol: its streams do not appear on market pages, its sessions accrue no provenance, its keys work nowhere else.
Where to go next
Section titled “Where to go next”| You are | Start with |
|---|---|
| an operator or creator | Operator quick start |
| building on the API or SDK | Developer quick start |
| launching a vertical (sports, music, fashion, news…) | Fork quick start |
| reading the spec | DIP-1 |