Verifiable Trust Concept

Building a native trust layer for the internet through verifiable credentials and cryptographic proof of identity, authenticity, and ownership.

On-chain rules, off-chain proofs

Concept

The Verifiable Trust concept relies on a hybrid trust model, combining web3, DIDs and Verifiable Credentials.

On-Chain Rules

Ecosystems publish their Decentralized Identifier (DID), governance framework, trust registries, credential schemas, and issuer/verifier lists on-chain.

Public and auditable
Tamper-resistant
Transparent governance

Off-Chain Proofs

Ecosystems prove off-chain control of their DID by updating their DID Document. Only the DID controller can do this.

Cryptographic proof of ownership
References to on-chain data
Verifiable authenticity

Benefits

Ledger Benefits
Public, transparent information
Immutable history
Token-based business models
DID + VC Benefits
Data doesn't have to be public
No personal data stored on-chain
DID verification is straightforward
Combined Power Hybrid Trust Model

Example

Ecosystem did:example:ecosystem created a trust registry and a credential schema on-chain. To prove ownership, they will refer to the trust registry and attach a verifiable credential to their DID Document.

Ecosystem DID Self-Issues Verifiable Credential

Ecosystem DID will self-issue a Verifiable Credential to prove control over the on-chain credential schema:

json-schema-credential.json
{
  "@context": [
    "https://www.w3.org/ns/credentials/v2"
  ],
  "id": "https://ecosystem/shemas-example-jsc.json",
  "type": ["VerifiableCredential", "JsonSchemaCredential"],
  "issuer": "did:example:ecosystem",
  "issuanceDate": "2024-01-01T19:23:24Z",
  "credentialSchema": {
    "id": "https://www.w3.org/ns/credentials/json-schema/v2.json",
    "type": "JsonSchema",
    "digestSRI": "sha384-S57yQDg1MTzF56Oi9DbSQ14u7jBy0RDdx0YbeV7shwhCS88G8SCXeFq82PafhCrW"
  },
  "credentialSubject": {
    "id": "vpr:verana:mainnet/cs/v1/js/12345678",
    "type": "JsonSchema",
    "jsonSchema": {
      "$ref": "vpr:verana:mainnet/cs/v1/js/12345678"
    },
    "digestSRI": "sha384-ABCSGyugst67rs67rdbugsy0RDdx0YbeV7shwhCS88G8SCXeFq82PafhCeZ"
  }
}

Ecosystem DID Document Service Entries

Ecosystem DID Document will contain references to the verifiable presentations and trust registries:

did-document.json
"service": [
  {
    "id": "did:example:ecosystem#vpr-schemas-example-jsc-vp",
    "type": "LinkedVerifiablePresentation",
    "serviceEndpoint": ["https://ecosystem/schemas-example-jsc-vp.json"]
  },
  ...
]

Generalizing the Concept: Proof-of-Trust

The Proof-of-Trust doesn’t just apply to ecosystems, it extends to every participant and service:

Every service is identified by its own DID

Services collect multiple verifiable credentials from different ecosystems

Apps display a clear Proof-of-Trust snapshot

Proof-of-Trust

Futuristic diagram showing multiple colorful credential badges connecting to a central service icon

Proof-of-Trust

DID Directory

To make all this work, Verana also provides a public DID Directory:

Register

Anyone can register their DID on-chain

Index

Verana Resolver indexes, verifies credentials, and stores results

Query

Apps and search engines can query this verifiable database

Ready to Deep-Dive?

Learn how Trust Resolution works in practice and see the full potential of verifiable discovery.

Continue to Trust Resolution