zkMe Dochub
GitHubTwitterDiscord
  • zkMe Network
  • Learn about zkMe Network
    • Introduction
    • Try a Demo
    • High Level Architectural Overview
      • High Level User Stories
      • zkMe Protocol Components
        • zkMe zkVault
        • zkMe DID Method
        • zkMe Credential Suites
        • zkMe Self-Sovereign Identity
    • Vision, Mission & Design Philosophy
    • Value Propositions & Use Cases
  • Verify with zkMe Protocol
    • Integration Checklist
      • zkMe Dashboard Setup
      • zkMe Supported Chains Overview
      • zkMe Protocol Smart Contract
    • Integration Guide
      • JavaScript SDK
        • zkKYC - Compliance Suite
        • MeID - Anti-Sybil Suite
        • Me - Profiling Suite
      • zkMe API
        • zkKYC - Compliance Suite
          • Verify zkKYC Status
          • Get KYT Results
      • Platform Integration
        • QuestN Integration
      • Smart Contract Verification
        • Compliance Suite
      • Customize Widget UI
    • zkKYC - Compliance Suite
      • zkMe zkKYC Levels
      • Regulatory Frameworks
        • EU - MiCA/TFR Regulations
        • US - Crypto Regulations
        • UK - Crypto Regulations
      • zkKYC Credentials
        • Proof-of-Citizenship (zkPoC)
        • Proof-of-Location (zkPoL)
        • Proof-of-Accredited-Investor (zkPoAI)
        • AML Check (AMLMe)
        • Know Your Transaction (KYT)
          • KYT Supported Scope
        • Know Your Business (KYB)
    • MeID - Anti-Sybil Suite
      • CKKS Homomorphic Encryption
      • DID Creation
      • MeID Credentials
        • MeID
    • Me - Profiling Suite
      • MeScores Credentials
        • zkCredit Score
        • zkSocial Network
        • zkDAO Management
        • zkGaming Status
    • zkMe Roadmap
  • Explore More
    • zkMe Bug Bounty Program
    • zkMe Brand Kit
    • zkMe Identity Hub
    • FAQ
    • Glossary
    • Link
      • GitHub
      • X / Twitter
      • Medium
      • YouTube
      • LinkedIn
      • Discord
      • Blog
    • Privacy Policy
Powered by GitBook
On this page
  • View Methods
  • hasApproved()
  • Resources
  • Smart Contract Address
  • ABI
  1. Verify with zkMe Protocol
  2. Integration Guide
  3. Smart Contract Verification

Compliance Suite

PreviousSmart Contract VerificationNextCustomize Widget UI

Last updated 1 month ago

The smart contract (ZKMEVerifyUpgradeable) is used for eligibility checks. The verify function provides yes/no answers to a list of predetermined eligibility questions for each credential verified. The hasApproved function provides information on whether the user has authorized the SBT.

View Methods

hasApproved()

This method verifies both that the user has authorized their SBT and that the user meets the project's KYC requirements. According to our design logic, users can only authorize their SBT to a project if their KYC meets the specified requirements. Therefore, a successfully authorized user, indicated by hasApproved() returning true, is one who meets your KYC settings.

function hasApproved(
    address cooperator, 
    address user
) public view returns (bool)

Parameters

Name
Type
Required
Description

cooperator

address

Yes

Account address of Program

user

address

Yes

User's wallet address

Note

You can obtain the cooperator address after completing the "Create Program" step on the .


Resources

Smart Contract Address

Please check zkMe Protocol Smart Contract.

ABI

You can download the following file or install it from .

npm
zkMe Dashboard
16KB
zkmeverify.abi.json