Skip to main content

Overview

Attesters are trusted entities that can create and verify attestations in the ZKScore Trust Layer V1. This comprehensive guide covers the complete journey from application to becoming a successful attester, including the whitelisting process, technical integration, and best practices.
Attesters are the backbone of the ZKScore ecosystem. They verify and certify information about users, creating the foundation for trust-based decisions across Web3 applications.

What are Attesters?

Attesters are organizations, individuals, or automated systems that can create cryptographically signed attestations about users’ identities, skills, behaviors, or achievements.

Types of Attesters

  • Identity Verifiers: KYC providers, government agencies
  • Skill Assessors: Educational institutions, certification bodies
  • Protocol Operators: DeFi protocols, NFT marketplaces
  • Community Moderators: DAO administrators, social platform moderators
  • Automated Systems: Smart contracts, oracles

The Attester Whitelisting Process

ZKScore Trust Layer V1 uses a whitelist model to ensure quality and prevent spam. All attesters must go through a comprehensive approval process.

Why Whitelisting?

The whitelist model provides several benefits:
  • Quality Control: Ensures only reputable organizations become attesters
  • Spam Prevention: Prevents low-quality or fraudulent attestations
  • Trust Building: Users can trust that attestations come from verified sources
  • Ecosystem Health: Maintains the integrity of the trust layer
  • Regulatory Compliance: Helps meet compliance requirements

Attester Tiers

ZKScore offers different attester tiers with varying requirements and capabilities:

Application Requirements

1. Organization Identity

  • Legal Entity: Must be a registered legal entity
  • Business License: Valid business license or registration
  • Website: Professional website with clear information
  • Contact Information: Verifiable contact details

2. Technical Capability

  • API Integration: Ability to integrate with ZKScore APIs
  • Technical Team: Dedicated technical team or expertise
  • Infrastructure: Reliable infrastructure for attestation services
  • Security: Basic security practices and procedures

3. Trustworthiness

  • Reputation: Established reputation in relevant field
  • References: Professional references from industry peers
  • Track Record: History of reliable service delivery
  • Compliance: Adherence to relevant regulations

4. Use Case

  • Clear Purpose: Well-defined use case for issuing attestations
  • Business Model: Sustainable business model
  • Target Users: Clear understanding of target user base
  • Value Proposition: Clear value proposition for users

5. Staking Requirements

  • SCORE Tokens: Required amount of SCORE tokens for staking
  • Lock Period: Minimum staking period (varies by tier)
  • Slashing Risk: Understanding of slashing conditions
  • Financial Capacity: Ability to maintain stake

Step-by-Step Application Process

Step 1: Initial Application

Submit your initial application through the ZKScore attester portal:

Step 2: Technical Review

The ZKScore team will conduct a technical review: Technical Requirements Checklist:
  • API integration capability demonstrated
  • Security practices documented
  • Infrastructure reliability verified
  • Data handling procedures reviewed
  • Backup and recovery procedures in place
Technical Interview:
  • Architecture discussion
  • Security practices review
  • Integration timeline assessment
  • Performance requirements discussion
  • Support and maintenance plans

Step 3: Business Review

Business Model Assessment:
  • Sustainable business model
  • Clear value proposition
  • Target market analysis
  • Competitive positioning
  • Revenue projections
Use Case Validation:
  • Attestation schemas defined
  • Verification processes documented
  • Quality assurance procedures
  • User experience design
  • Dispute resolution procedures

Step 4: Compliance Review

Legal and Compliance Assessment:
  • Legal entity verification
  • Business license validation
  • Regulatory compliance review
  • Data protection compliance
  • Liability and insurance coverage

Step 5: Staking and Approval

Once approved, you’ll need to stake the required SCORE tokens:

Application Timeline

Application Tips

1. Prepare Thoroughly

  • Documentation: Prepare all required documents in advance
  • References: Line up professional references
  • Demo: Prepare a demonstration of your technical capabilities
  • Business Plan: Have a clear business plan and use case

2. Technical Readiness

  • API Knowledge: Familiarize yourself with ZKScore APIs
  • Security: Implement basic security practices
  • Infrastructure: Ensure reliable infrastructure
  • Testing: Test your integration thoroughly

3. Business Clarity

  • Value Proposition: Clearly articulate your value proposition
  • Target Market: Define your target market clearly
  • Attestation Types: Specify what types of attestations you’ll issue
  • Quality Standards: Define your quality standards

4. Compliance Preparation

  • Legal Structure: Ensure proper legal structure
  • Regulatory Compliance: Understand relevant regulations
  • Data Protection: Implement data protection measures
  • Insurance: Consider appropriate insurance coverage

Common Rejection Reasons

Understanding common rejection reasons can help you prepare a stronger application:

Technical Issues

  • Insufficient Technical Capability: Unable to integrate with APIs
  • Poor Security Practices: Inadequate security measures
  • Unreliable Infrastructure: Infrastructure not suitable for production
  • Lack of Technical Team: No dedicated technical resources

Business Issues

  • Unclear Use Case: Vague or poorly defined use case
  • Unsustainable Model: Business model not viable
  • No Target Market: Unclear target market
  • Poor Value Proposition: No clear value for users

Compliance Issues

  • Legal Issues: Problems with legal entity or registration
  • Regulatory Non-compliance: Failure to meet regulatory requirements
  • Data Protection Issues: Inadequate data protection measures
  • Insurance Coverage: Insufficient insurance coverage

Post-Approval Onboarding

Once approved, you’ll go through an onboarding process:

1. Credential Setup

2. Schema Creation

3. Testing Phase

4. Production Launch

Creating Attestations

Basic Attestation Creation

Batch Attestation Creation

Attestation Schemas

Skill Verification Schema

Education Certificate Schema

Work Experience Schema

Attester Dashboard

Managing Attestations

Trust Modules

Custom Trust Logic

Best Practices

Attestation Quality

  1. Accurate Data: Only attest to verified information
  2. Clear Schemas: Use well-defined, consistent schemas
  3. Appropriate Expiration: Set reasonable expiration times
  4. Regular Review: Periodically review and update attestations
  5. Revocation Process: Have clear revocation procedures

Attester Reputation

  1. High Standards: Maintain high verification standards
  2. Transparent Process: Be transparent about verification process
  3. Responsive: Respond to disputes and inquiries
  4. Consistent: Apply standards consistently across all attestations
  5. Continuous Improvement: Regularly improve verification processes

Data Privacy

  • GDPR Compliance: Ensure compliance with data protection regulations
  • Data Minimization: Only collect necessary data
  • User Consent: Obtain proper consent for data processing
  • Data Retention: Implement appropriate data retention policies
  • Jurisdiction: Understand applicable laws and regulations
  • Liability: Consider liability for false attestations
  • Dispute Resolution: Have clear dispute resolution procedures
  • Terms of Service: Maintain clear terms of service