Skip to main content

KYC Validator Logic

KYC Validators are responsible for verifying the identity data submitted by Bussiness/ institution and ensuring it aligns with CRYMBO’s compliance rules and regulatory requirements.

Responsibilities​

KYC validators must:

  • Verify that PII payloads meet format and schema standards
  • Confirm encryption metadata (key, nonce, version) is valid
  • Ensure the payload is signed or authenticated by a known Bussiness/ institution
  • Validate timestamp and freshness for replay protection

Types of Validation Performed​

  • Schema Validation: Check structure and required fields in the identity payload
  • Key Matching: Validate public encryption key corresponds to the receiver Bussiness/ institution
  • Metadata Review: Verify nonce, version, and timestamp
  • Source Authentication: Confirm sender Bussiness/ institution identity and API token validity

Validation Flow​

  1. Oracle fetches or receives an encrypted PII payload
  2. Emits a PIIReceived(txHash, receiver, sender) event
  3. KYC validators retrieve the encrypted payload
  4. Validators apply off-chain rules and checks
  5. Results are signed and submitted to CRYMBO

Example Event​

event PIIReceived(
  bytes32 txHash,
  address sender,
  address receiver
);

Scoring and Reputation​

Validators are scored on:

  • Accuracy of validation decisions
  • Uptime and response latency
  • Consistency with majority quorum

High-reputation validators are prioritized in quorum formation and may receive higher rewards.

📌 Next Step: Understand the Proof-of-Validation Mechanism