The network

No central registry. A mesh of domains.

GOVP has no blockchain and no central authority. The network is domains: each publishes its identity at .well-known, discovers peers, and — when configured — witnesses other domains' records. Trust is computed from independence, never granted by a registrar.

How a domain becomes a node

Publish, discover, witness

1 · Publish

Identity at .well-known

The domain serves govp.txt (its key + metadata), a discovery index and its records. That alone makes it a verifiable issuer.

2 · Discover

Peers find each other

Nodes learn about peers through the discovery index and peer exchange — the same mechanism the reference mesh uses, hardened against SSRF and rebinding.

3 · Witness

Independent observation

A witnessing node fetches a peer's record, verifies it and signs what it saw and when. Backdating gets harder with every independent witness.

4 · Corroborate

Trust is computed

A claim's trust weighs how many independent, well-verified parties stand behind it — not who paid for a seal.

Corroborated trust

T = V × I × Q

verified sources × effective independence (anti-Sybil) × verification quality — details in the protocol.

Consortium mode

Closed groups, same math

A supply chain, an industry association or a group of plants can run the mesh among themselves: a defined member set, mutual witnessing, and a shared anchor registry for their source types. The trust calculation is identical — what changes is who participates. One member cannot manufacture consensus, because copies of itself add no effective independence.

Honest boundary: a node's local transparency log is a useful journal, but it is not public transparency — its own admin could rewrite it. Cross-witnessing between independent nodes, or an external anchor (RFC 3161 / QTSP), is what makes history hard to rewrite. The reference implementation states this in its own documentation, and so do we.

Directory · early network

Issuing domains

The network is young and we list it honestly: real nodes as real, illustrative ones as illustrative. Every entry resolves to a fetchable identity and verifiable records.

Domain	Role	Records	Status
this site	Protocol home · its own issuer	.well-known/govp.txt · reference library	live
evidence.acerosdelnorte.eu	Industrial manufacturer (steel)	manufacturing · quality inspection	illustrative
trust.northbridge.example	Compliance / audit / ESG office	compliance · audit · ESG	illustrative
winery.example	Conformance suite publisher	vector records	illustrative

Running a public GOVP node? Ask to be listed: contact@gemacode.org. Listing requires a reachable .well-known/govp.txt whose records verify.

Run your own node The HTTP surface