Implement freely
The spec, the immutable conformance fixtures and the verifier cores are open (Apache-2.0). Build a verifier in any language; agreement across independent implementations is the trust anchor.
Conformance · the TSP-Certified mark
Anyone can implement it. Only conformant builds wear the mark.
The protocol name is open and generic on purpose — like HTTP or 802.11, anyone is free to implement TSP. What is governed is a distinct certification mark: you earn the right to display it by passing conformance against the register, not by declaring yourself conformant.
The model · a conformance test kit (TCK)
Open standard, governed mark — the proven split.
Wear the mark
The TSP-Certified mark is a distinct, registrable certification mark — granted only to implementations that pass conformance and hold a licence. The mark, not the protocol, is the controlled asset.
The same shape every durable standard uses: the spec is generic, the mark is distinctive — IEEE 802.11 → Wi-Fi, OpenJDK → Java, Kubernetes → Certified Kubernetes.
How conformance is verified
Checked against the register — never self-declared.
- Your implementation recomputes the public fixtures and must match across the required checks — the same math everyone else runs.
- Conformance status is resolved against the public register, so a relying party can confirm it independently — not take your word for it.
- Payment never grants official status: a licence lets a conformant build wear the mark; it cannot buy conformance.
The mark itself
A distinct mark and seal, separate from the open TSP glyph.
"TSP" and "Trust Standard Protocol" are generic and descriptive — deliberately unprotected, so the protocol stays free to adopt. The TSP-Certified mark and its seal are the governed certification mark: controlled and licensed, in the UL / Fairtrade model, and kept separate from the open protocol glyph — so the standard stays open while the mark that vouches for it stays controlled.