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:
Attestation Management : Creation and storage of attestations
Verification System : Cryptographic verification of claims
Trust Modules : Pluggable trust evaluation modules
Reputation Tracking : Aggregation of trust signals
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
Verify Claims : Thoroughly verify before attesting
Use Expiration : Set appropriate expiration times
Schema Standards : Follow established schemas
Reputation : Build attester reputation
Documentation : Document attestation criteria
For Verifiers
Check Validity : Always verify attestation validity
Attester Reputation : Consider attester trustworthiness
Multiple Sources : Require multiple attestations
Time Sensitivity : Consider attestation age
Schema Matching : Verify correct schema