Markets
Protocol-defined execution contexts with their own policy and accounting, derived from execution and verified against canonical registry state.
Markets are protocol-defined execution contexts with their own policy and accounting. A market is not a user-chosen label; it is derived from what a transaction executed, and it is verified against canonical registry state.
Markets also provide the protocol surface for bootstrapping: new markets can start sparse and fragmented yet still be scored and incentivized safely via market-relative teleport (seeds) and credit-like reward funding (MarketVaults) with repayment sourced from market fees.
What lives here
- Market identity and enforcement: how a transaction’s market is derived from execution and verified against canonical registry state.
- Commitment hooks: how market tables and fee attribution are bound into epoch commitments.
- Bootstrapping and credit: how early markets can be seeded and funded, with repayment sourced from market fee cashflows.
Start here
Related work (context, not requirements)
- Personalized PageRank (PPR): market-relative teleport is a protocol-fixed personalization distribution (Jeh & Widom, 2003).
- Seed-anchored filtering: anchoring trust to protocol-defined seeds is adjacent to ideas like TrustRank.
- Authenticated data / commitments: MarketRegistry is made auditable by including it in snapshot artifacts bound by hash commitments (Merkle trees: Merkle, 1987).