N-PAMP — Native Post-Quantum Agent Messaging Protocol¶
A binary, multi-channel, wire-level protocol for authenticated communication between autonomous software agents. N-PAMP sits beneath application-layer agent protocols and gives them one thing they all lack: a single fixed-size frame, a registry of multiplexed channels, and negotiated post-quantum security — on the wire, before any application semantics.
This site renders the public reference material for N-PAMP: the Internet-Draft, the
normative core and companion specifications, the code-point registries, the ten
reference implementations with copy-paste quickstarts, and the conformance corpus and
harness. The authoritative sources are the Markdown files in the
npamp_protocol repository; this
is a browsable mirror of them.
Specification status
The current specification is draft-bubblefish-npamp-01 (Internet-Draft,
Independent Submission stream, Informational). Wire-format version 2 (the
Ver nibble, invariant); crypto generation 3, ALPN identifier n-pamp/3.
License: Apache-2.0.
What N-PAMP provides¶
- A single fixed 36-octet frame header with mandatory authenticated encryption (AEAD) and a header CRC32C (Castagnoli) for fast rejection of corrupted frames before any cryptographic work.
- Twenty multiplexed, full-duplex channels, each with an independent per-direction sequence space and independent traffic keys: Control, Memory, Capability, Identity, Governance, Immune, Federation, Settlement, Compliance, Sensory, Telemetry, Audit, Stream, Bridge, Commerce, Interaction, Discovery, Workflow, Knowledge, and Spatial.
- Three negotiated security profiles — Standard, High, and Sovereign — that hold the wire format constant while escalating the cryptographic primitives.
- Hybrid post-quantum key establishment combining an elliptic-curve ECDH with ML-KEM (FIPS 203); the concatenation order is per-group (X25519MLKEM768 is ML-KEM-first, SecP384r1MLKEM1024 is ECDHE-first), aligned to NIST SP 800-56C Rev. 2.
- A 1.5-RTT, mutually-authenticated handshake with transcript binding, an HKDF key schedule, forward secrecy, and downgrade protection.
- QUIC as the primary transport and TCP with TLS 1.3 as a fallback, negotiated
via the ALPN identifier
n-pamp/3.
N-PAMP is deliberately scoped as a transport substrate. It does not define application-layer semantics for the data carried on its channels; those are the subject of the companion specifications and bridge mappings shipped alongside it.
Start here¶
- Read the specification — the Internet-Draft:
draft-bubblefish-npamp-01. - Pick a language and go — ten reference implementations, each with a copy-paste quickstart: Go · Rust · Python · TypeScript · C# · Swift · Java · Kotlin · PHP · Ruby.
- Understand the wire format — the core specification: Frame format, Channels, Cryptographic suites, Handshake binding.
- Check conformance — the conformance requirements, the test-vector corpus, and the harness.
- Choose a cryptographic provider — the per-language ML-KEM + ECDH provider matrix (which library each SDK uses to produce the hybrid key-exchange component secrets).
Reference implementations at a glance¶
| Language | Quickstart | Build with |
|---|---|---|
| Go (primary reference) | QUICKSTART | go build |
| Rust | QUICKSTART | cargo build |
| Python | QUICKSTART | pip / pyproject.toml |
| TypeScript | QUICKSTART | npm |
| C# | QUICKSTART | dotnet build |
| Swift | QUICKSTART | swift build |
| Java | QUICKSTART | JDK |
| Kotlin | QUICKSTART | Kotlin/JVM |
| PHP | QUICKSTART | src/ |
| Ruby | QUICKSTART | lib/ |
Every SDK implements the same Standard-profile primitives — frame codec, AES-256-GCM AEAD record layer, HKDF key schedule, TLV codec, and the 1.5-RTT handshake binding — verified against the shared vectors in the test-vector corpus. See the implementation overview for the full matrix.