IIP-057: Hosted and DePIN runtime nodes
IIP-057 is recorded on the Hypervisor Daemon roadmap with status Speculative horizon in Horizon 4 — enterprise and embodied: Hosted and DePIN runtime nodes. Hosted, DePIN, and TEE venue contracts beyond the working local runtime; advances only when proven scenarios require them.
IIP-057 Roadmap Record
IIP-057: Hosted and DePIN runtime nodes is an IOI roadmap record for the Hypervisor Daemon surface. Its status is Speculative horizon in Horizon 4 — enterprise and embodied and it belongs to the Substrate track. Canonical long-range direction with no current implementation claim. The canonical scope is: Hosted, DePIN, and TEE venue contracts beyond the working local runtime; advances only when proven scenarios require them.
Surface Context
This record should be read as part of the Hypervisor Daemon roadmap, not as a replacement for source papers or product pages. The parent surface gives the broader context for why this milestone exists, what it depends on, and which IOI surfaces it supports. The parent Hypervisor Daemon surface has no surface-level dependency in the current roadmap model. The parent surface unblocks later roadmap surfaces: hypervisor, ioi, decentralized.
Evidence And Verification
The record is designed to make roadmap evidence crawlable and separable from research claims. This item also names item-level dependencies: IIP-056. Evidence links below point to the paper, release, repository, developer documentation, or product page that supports this milestone.
Canonical Relationship
This page is the canonical roadmap record for IIP-057, while the parent roadmap surface and linked research pages remain the canonical sources for broader product and protocol context. Internal links point here when the milestone status, horizon, dependencies, or evidence trail for Hosted and DePIN runtime nodes matters.
Roadmap Role
IIP-057 exists to clarify roadmap status, bounded scope, horizon placement, and evidence relationships. Technical concepts flow through this page to canonical research pages, while product or runtime context flows to the relevant surface page. This preserves a complete status and evidence trail without making roadmap records compete with deeper IOI papers.