All blog posts
Updates 4 min read

Secure Net Protocol Standards, Registries and Conformance

The Secure Net standards framework defines versioning, registries, normative documents, test vectors and conformance rules for interoperable implementations.

By Comutability Published Update from

Project update: 15 November 2026. GitHub change #3: merged into the repository. The underlying protocol remains draft and unaudited.

The Secure Net standards framework defines versioning, registries, normative documents, test vectors and conformance rules for interoperable implementations.

Why we made this change

A network is only truly open when independent developers can implement its rules without guessing from one codebase. The standards framework makes terminology, wire formats, shared names and version changes visible and checkable. This change concerns specification governance and tooling, not a new message format.

The engineering record

The original pull request records the following technical scope and evidence. Some forward-looking notes in the record reflect the state of the work when the request was opened, rather than its status today.

What this does

Adds the standards layer the protocol was missing: rules for how it changes, registries of every shared name, a way for other implementations to claim conformance, and a checker that keeps the code and the standard in step. Proposal: SNIP-0004. Secure Net 0.4.1. Nothing on the wire changes.

Rules for change: CVP-000

  • Language and authority: normative language, and an order of authority when sources disagree: part documents and registries first, then vectors, then code.
  • Parts: a standard structure for every part (header table, required security, conformance and changes sections) and a set of statuses (Reserved to Withdrawn).
  • Versions: four kinds, each with its own rule: release, part, feature and label. A label's meaning never changes.
  • Compatibility: what counts as additive or breaking, and how receivers treat unknown data.
  • Retirement: a deprecation lifecycle (Active, Deprecated, Legacy, Removed), with at least two minor releases and six months before anything is removed.
  • Housekeeping: naming rules, vector requirements, errata, security fixes and writing style.

Registries: spec/registry.json, readable as REGISTRIES.md

  • 20 record kinds, 14 ledger events, extension permissions, 5 algorithm suites, about 40 domain-separation labels, endpoints and 9 HTTP headers.
  • Until now these were defined only where the code happened to use them, and the headers only in Commonveil's server.

Conformance: CVP-010

  • Seven profiles (core, messaging, site, community, governance, extensions, commonveil-compatible).
  • A JSON conformance statement format. Secure Net publishes its own: secure-net-conformance.json.
  • Claims are self-declared and must say what was tested.

Foundation: CVP-002

  • Canonical JSON and signed records, written down for the first time.
  • Language-neutral vectors, including records that must be refused.
  • Checked independently: a separate canonical-JSON encoder written in Python from the document alone reproduces every case, and the Ed25519 signature and key ids verify with Node's built-in crypto.

Checker: scripts/standards.mjs (runs in CI and npm test)

  • What it compares: every name the code uses against the registry, in both directions.
  • Also checked: versions, part document headers and sections, the conformance statement, and that the generated index and registry tables are up to date.
  • Evidence it works: run against ten kinds of deliberate drift, it caught every one and named the problem.
  • Side change: the session module now refuses any label purpose that isn't registered.

Also

  • A part template.
  • CVP-011 to 016 brought into the standard format.
  • The spec index is now generated from the registry and can't go stale.
  • GOVERNANCE.md and README point to the framework.

Honest status

  • All parts Draft: every part is marked Draft, because none has been through Technical Review under GOVERNANCE.md yet.
  • Missing documents: six implemented parts still have no document (CVP-001, 003, 004, 005, 008, 014). The generated index lists them, and for now their code is their only specification.
  • Missing vectors: only CVP-002 and CVP-016 have vectors.
  • No independent runner: there is no implementation-independent test runner yet.

These are listed as the next work in SNIP-0004 and CVP-010.

Tested

  • npm test: 47 pass, including 4 new standards tests.
  • node scripts/standards.mjs, node scripts/vectors.mjs --check, node scripts/manifest.mjs --check and node examples/two-party.mjs all pass.
  • The full test suite also passes from a bare copy built from the manifest, which is how Commonveil's vendored copy runs it.

The wider direction

The Comutability approach is open source with human accountability. AI can help research, design, write code and test it, but a merged change is not the same thing as an independently audited product. Secure Net is explicitly described as a draft in its public README. Its use in a sensitive situation should wait for qualified cryptographic review.

What happens next

Invite outside implementation feedback and strengthen independent conformance testing before making compatibility guarantees.

Read the original sources

Sources and further reading

Explore the evidence and original project records behind this article.