Skip to main content

Overview

The ZKScore Trust Registry is a decentralized attestation and verification system that manages trust relationships, credentials, and reputation signals on-chain. It enables verifiable claims about identities, behaviors, and achievements through cryptographically signed attestations.
The Trust Registry enables permissionless trust-building while maintaining privacy and decentralization. All attestations are cryptographically verifiable and immutable.

Contract Architecture

Core Components

The Trust Registry consists of several key components:
  1. Attestation Management: Creation and storage of attestations
  2. Verification System: Cryptographic verification of claims
  3. Trust Modules: Pluggable trust evaluation modules
  4. Reputation Tracking: Aggregation of trust signals
  5. Privacy Layer: Zero-knowledge proof integration

Trust Model

The trust model is based on:
  • Attesters: Entities that issue attestations
  • Subjects: Entities receiving attestations
  • Verifiers: Entities checking attestations
  • Trust Modules: Logic for trust evaluation
  • Reputation Scores: Aggregated trust metrics

Contract Addresses

Mainnet Deployments

Testnet Deployments

Attestation Structure

Attestation Data Model

Schema Structure

Common Schema Types

Contract Interface

Core Functions

Events

Attestation Types

1. Identity Attestations

Verify identity characteristics:

2. Skill Attestations

Endorse skills and expertise:

3. Participation Attestations

Verify protocol/community participation:

4. Reputation Attestations

Signal reputation and trustworthiness:

Trust Modules

Module Architecture

Trust modules are pluggable contracts that evaluate trust:

Built-in Modules

1. Attestation Count Module

2. Attester Reputation Module

3. Schema-Based Module

4. Time-Decay Module

Privacy Features

Zero-Knowledge Proofs

The Trust Registry integrates ZK proofs for privacy:

Selective Disclosure

Users can prove specific claims without revealing all data:

Gas Optimization

Efficient Storage

Batch Operations

Gas Estimates

Integration Examples

Basic Attestation

Security Considerations

Attestation Verification

Always verify attestations before trusting:

Sybil Resistance

Implement Sybil attack protection:

Best Practices

For Attesters

  1. Verify Claims: Thoroughly verify before attesting
  2. Use Expiration: Set appropriate expiration times
  3. Schema Standards: Follow established schemas
  4. Reputation: Build attester reputation
  5. Documentation: Document attestation criteria

For Verifiers

  1. Check Validity: Always verify attestation validity
  2. Attester Reputation: Consider attester trustworthiness
  3. Multiple Sources: Require multiple attestations
  4. Time Sensitivity: Consider attestation age
  5. Schema Matching: Verify correct schema