DIP-1: Market-Bound Broadcast Surfaces
| DIP | 1 |
| Title | Market-Bound Broadcast Surfaces |
| Status | Draft |
| Type | Standards Track · Broadcast |
| Created | 2026-09-15 |
| Inspired by | ERC-6551, Non-fungible Token Bound Accounts |
Abstract
Section titled “Abstract”This proposal defines a system which assigns a live media surface to every resolvable market. A surface is addressed deterministically by its market id and is the unit of distribution. Surfaces bind live streams as context, accept signals (timestamped YES/NO calls locked with a market snapshot), are aired by a program clock, resolve through the market’s own oracle, and cut receipts of who broadcast on them, when, and to how many. Forks are implementations: they own the surface’s theme, scope and domain, while identity, binding, receipts and market context resolve through a single registry.
The analogy
Section titled “The analogy”| ERC-6551 | DIP-1 |
|---|---|
| ERC-721 token | Market |
| Registry | Registry (denpa.ai/m/[marketId]) |
| Token-bound account | Market-bound surface |
| Implementation | Fork (verticalConfig) |
| Owner | Operator |
execute() | signal() · bind() |
Specification
Section titled “Specification”The key words MUST, MUST NOT, SHOULD and MAY are to be interpreted as described in RFC 2119.
Registry
Section titled “Registry”- MUST resolve every market with a provider id to exactly one canonical surface address.
- MUST serve market context and the related-market graph.
- MUST resolve identity server-side for every write. The acting handle MUST NOT be taken from the request body.
- MUST cut a receipt for every broadcast session.
- MUST NOT require a wallet for any operation in this specification.
Surface
Section titled “Surface”See The surface. Bindings MUST be HLS. A surface MUST render live, empty and error states, and MUST show a price only when one exists.
Signal
Section titled “Signal”See Signals. One canonical scored signal per operator per market; first-call lock; signal_events append-only; snapshot at write time; no wallet; AI operators disclosed.
Air and Move
Section titled “Air and Move”See Air and Move. Every aired segment MUST record why it aired. MOVE MUST be captured, never reconstructed. Momentum MUST be normalised per liquidity. Editorial weight stays human. Schedules MUST NOT thrash.
Resolution and scoring
Section titled “Resolution and scoring”See Resolution and Scoring. Resolution MUST update signal statuses, MUST trigger scoring stamped with SCORING_VERSION, and MUST produce a receipt-like record.
Fork interface
Section titled “Fork interface”See denpa.config.ts and Rules every fork inherits. A fork MUST NOT rewrite Signal, Market, Identity, Follow, Outcome or Field Record logic. Traffic, identity, receipts, stream binding and market context MUST resolve through the registry.
Rationale
Section titled “Rationale”Market-addressed, not channel-addressed. Snapshot at write time. One canonical signal. The registry owns distribution. Wallet optional. Information, not advice.
Security and integrity
Section titled “Security and integrity”Capture (momentum can be bought — normalise per liquidity, keep editorial weight human, provenance on every preemption). Identity (server-side handle resolution, hashed keys, op_ ids). Reputation integrity (first-call lock, append-only events, versioned scoring, disclosed AI). Media rights (terms). Legal posture (information and interface layer; never advice).
Copyright
Section titled “Copyright”Licence to be confirmed by the author. EIP convention is CC0-1.0; this draft does not yet make that waiver.