NPS-Release

Roadmap

English 中文版

NPS is on a four-phase path from draft specification to formal standard. The current release — v1.0.0-alpha.11 — completes Phase 1 and makes significant progress on Phase 2. Notable additions since alpha.4: NWP error code parity across all six SDKs (30 constants), RFC-0004 Phase 3 STH gossip federation in nps-ledger, NPS-SERVER-UNSUPPORTED status code, and AssuranceLevel spec fixes in Python / TypeScript / Java.


Version convention

Tag Meaning
v0.x-draft internal draft; breaking changes allowed
v0.x-alpha public preview; API not stable
v0.x-beta feature-complete; external testing
v1.0 spec frozen; production-ready

Phase 0 — Spec Unification (2026 Q2) — ✅ done

Established the full NPS spec skeleton across all five protocols (NCP / NWP / NIP / NDP / NOP), unified the frame namespace, published the AaaS and Node conformance profiles, and released public repositories.


Phase 1 — Core Implementation (2026 Q3) — ✅ shipped

All five protocols production-ready in six reference SDKs (.NET / Python / TypeScript / Java / Rust / Go), with NIP CA Server reference deployments in all six languages. Key milestones:


Phase 2 — Ecosystem Expansion (2026 Q4) — 🚧 in progress

Adapters to MCP, A2A, and gRPC ecosystems; Tier-2 MsgPack production hardening; reference tooling.


Phase 3 — Ecosystem Validation (2027 Q1–Q2)

Real-world deployments, NPS Cloud CA v1.0, and the beginnings of de-facto standard status.


Phase 4 — Standardization (2027 Q3 onward)

Formal W3C / IETF standardization and NPS 1.0 spec freeze.


Next


📖 For tutorials, references, and operator guides, see the NPS Wiki.