Internet of Intelligence

IIP-050: dcrypt v1.1.0/v1.2.0 Constant-Time Assurance

IIP-050 is recorded on the dcrypt roadmap with status Shipped implementation in Built substrate: dcrypt v1.1.0/v1.2.0 Constant-Time Assurance. Gen-2 noise-aware constant-time verification harness, Holm-Bonferroni corrections, and shape tests.

IIP-050 Roadmap Record

IIP-050: dcrypt v1.1.0/v1.2.0 Constant-Time Assurance is an IOI roadmap record for the dcrypt surface. Its status is Shipped implementation in Built substrate and it belongs to the Cryptography track. Released implementation with verifiable code or release evidence. The canonical scope is: Gen-2 noise-aware constant-time verification harness, Holm-Bonferroni corrections, and shape tests.

Surface Context

This record should be read as part of the dcrypt 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 dcrypt surface has no surface-level dependency in the current roadmap model. The parent surface unblocks later roadmap surfaces: protocol.

Evidence And Verification

The record is designed to make roadmap evidence crawlable and separable from research claims. No item-level dependencies are listed for this record. 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-050, 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 dcrypt v1.1.0/v1.2.0 Constant-Time Assurance matters.

Roadmap Role

IIP-050 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.