English 中文版
Six official SDKs — each implementing all five protocols (NCP + NWP + NIP + NDP + NOP) — aligned to suite release 1.0.0-alpha.16. Package-manager availability is tracked per ecosystem.
alpha.16 release note: SDK docs now call out typed remote NIP CA clients, native-mode NWP serving helpers, and TC-N1/TC-N2 conformance helpers.
npm note:
@labacacia/nps-sdk@1.0.0-alpha.16fixed the earlier alpha.11 tarball issue; install@labacacia/nps-sdk@alphafor the latest published alpha.
| Language | Package | Min version | Repo | Wiki deep-dive |
|---|---|---|---|---|
| .NET | LabAcacia.NPS.Core (+ .NWP / .NIP / .NDP / .NOP) |
.NET 10 | NPS-sdk-dotnet | Wiki: SDK-dotnet |
| Python | nps-lib |
3.11 | NPS-sdk-py | Wiki: SDK-Python |
| TypeScript | @labacacia/nps-sdk |
Node 22 | NPS-sdk-ts | Wiki: SDK-TypeScript |
| Java | com.labacacia.nps:nps-java |
Java 21 | NPS-sdk-java | Wiki: SDK-Java |
| Rust | nps-sdk |
Rust stable | NPS-sdk-rust | Wiki: SDK-Rust |
| Go | github.com/labacacia/NPS-sdk-go |
Go 1.25 | NPS-sdk-go | Wiki: SDK-Go |
For install commands, minimal examples, and per-feature coverage tables, see the per-language Wiki pages above or SDK-Quickstart for a language-agnostic walkthrough.
Standalone deployable Certificate Authority for the Neural Identity Protocol (NPS-3 §8). Independently versioned from the SDKs since v1.0.0-alpha.11; current public docs track the alpha.16 signed-CRL and remote-client boundary.
| Repo | Stack | Quickstart |
|---|---|---|
| labacacia/nip-ca-server | C# / ASP.NET Core 10, PostgreSQL or SQLite, single-Docker | docker compose up -d |
For operator guides and embedding options (SQLite vs PostgreSQL) see Wiki: NIP-CA-Server-Ops.
Reference deployment binaries for the standard three-layer NPS topology, currently published at v1.0.0-alpha.16 with alpha.16 release docs for native NCP TLS/mTLS and NWP serving.
| Repo | Daemons | Quickstart |
|---|---|---|
| labacacia/nps-daemons | npsd (L1, :17433) · nps-runner (L1 FaaS) · nps-ingress (L2, :8080) · nps-registry (L2 NDP, :17436) |
docker compose up -d |
nps-ingress is a process-level Internet ingress daemon name, not the retired
NWP Gateway Node logical role. CR-0001 replaced that logical role with
Anchor Node and Bridge Node.
The Layer-3 trust-anchor daemons (nps-cloud-ca and nps-ledger) are private under the innolotus org and ship publicly with NPS Cloud GA (2027 Q1+). For operator and architecture detail see Wiki: Operators-QuickStart.
| You are… | Suggested SDK |
|---|---|
| Writing an agent that calls NPS nodes | Python or TypeScript — fastest iteration |
| Building a Memory Node for an existing service | match the service language (.NET / Java / Go for enterprise; Python / TS for startups) |
| Writing a high-throughput orchestrator (NOP) | Rust or Go |
| Bundling with a React frontend | TypeScript (dual ESM + CJS) |
| Shipping to a JVM-heavy environment | Java 21 |
All SDKs produce wire-identical frames — mix languages freely (e.g. a Python agent calling a Rust Memory Node, orchestrated by a Go NOP server).
📖 For tutorials, references, and operator guides, see the NPS Wiki.