A Verifiable Trust Community service is live at this endpoint. Once the operator publishes a community profile, its name and description will appear here.
openvtc.net explains what a Verifiable Trust Community is and walks you through getting a wallet and joining one.
Have Keyring? Scan the code to add this community.
Scan with Keyring On this phone? Copy the DID into Keyring instead.
…
A community that issues its members credentials they hold themselves, in their own wallet, under their own identifier. Anyone can check a membership without asking the community, and the community keeps a tamper-evident record of every decision it makes about who may do what.
Every grant, credential and decision is a signed record, checked against the community's live access list on every request.
The community decides who may create repositories, who owns each one and whose signed commits its checks accept. It then projects those rights onto every forge it has bound, and publishes them to its trust registry. Rights follow a repository's id, so a rename keeps them and a new repository under an old name inherits nothing.
Shared spaces whose membership is decided by credentials the room itself issued, not by a roster on this server. Sealed rooms store only ciphertext the host cannot read, and every membership change moves the room to a new key epoch.
Capability-based roles with ceilings. Sensitive acts take a step-up bound to that one operation, answered with a passkey or an approver device. Changes to other administrators wait for second-party consent. Everything lands in an HMAC-chained audit trail.
Members hold W3C verifiable credentials in their own wallet, under their own DID. A public status list lets anyone check that a membership is still current, without asking the community who is looking.
Communities recognise each other's credentials and publish what they trust to a trust registry, so a role earned in one community can count in another.
……