OpenVTC Wiki

3 min read

Verifiable Trust Communities (VTCs)

What They Are

A Verifiable Trust Community is a group of participants who have established a shared trust framework — agreed-upon rules for membership, credential issuance, and trust evaluation. Think of it as a club or professional association, but one where membership and trust relationships are cryptographically verifiable.

VTCs create denser clusters of trust within the broader Decentralized Trust Graph. While the DTG as a whole is an open, permissionless web of trust, a VTC adds structure: who can join, what credentials members can issue, what trust policies the community enforces.

How They Work

A VTC is identified by its own C-DID (Community DID) and has a community-level service — the VTC Service — that coordinates community operations. Members hold Membership Credentials issued by the community. When a VTC’s governance enforces personhood guarantees, these VMCs qualify as Personhood Credentials — determined by the community’s trust registry.

VTCs can belong to Verifiable Trust Networks (VTNs) — higher-level federations that enable trust paths to cross community boundaries.

The lifecycle looks like:

  1. A community is established with a DID and trust policies
  2. Prospective members are invited or apply
  3. The community evaluates the applicant (potentially checking their existing trust graph)
  4. Members receive Membership Credentials
  5. Members can issue credentials within the community’s scope (endorsements, witness attestations, etc.)
  6. The community maintains a registry of members and their roles

The Know Your Developer Use Case

The driving use case for OpenVTC is Know Your Developer — verifying that contributors to open-source projects are real people with genuine reputations. This matters increasingly because AI agents can now convincingly imitate human contributors: committing, reviewing, and communicating in ways indistinguishable from a person. In this context:

  • A VTC might be a Linux Foundation project, a GitHub organization, or a professional developer community
  • Membership proves you’re a verified human participant — not just an account or an agent
  • Relationship Credentials between members prove genuine connections
  • Endorsement Credentials attest to technical competence
  • Witness Credentials from conferences and meetups strengthen the graph

VTC Infrastructure

The VTI workspace includes a VTC Service (vtc-service) that handles community-level coordination. The OpenVTC tools include:

  • CNM CLI (Community Network Manager) — for managing multiple communities
  • PNM CLI (Personal Network Manager) — for individual participation in communities
  • OpenVTC Service — a background daemon that responds to community protocol messages (e.g., maintainer list queries)

Trust Policies

Communities can define their own policies for evaluating trust. For example:

  • “Require at least 3 VRCs from existing members to grant membership”
  • “Require at least 1 in-person witness attestation”
  • “Endorsements from members with >5 VRCs carry more weight”

These policies are the community’s own governance — the DTG provides the verifiable data, and the community decides how to interpret it.

See also: verifiable-trust-network, trust-registries, decentralized-trust-graph, membership-credential, first-person-network

Graph View

Backlinks