Skip to main content

Regulator Access

CRYMBO Oracle supports selective and controlled access for regulatory bodies, ensuring transparency and auditability without compromising user privacy or data sovereignty.

Purpose of Regulator Access​

  • Monitor Travel Rule compliance
  • Audit encrypted identity exchanges
  • Review VASP onboarding and KYC history
  • Analyze metadata trends across the network

How Access is Granted​

  • Audit Tokens: Time-bound and scope-limited credentials issued to regulators
  • Metadata Portals: Dashboard access to transaction metadata, logs, and validator signatures
  • Delegated Consent: VASPs can opt to share decrypted data with regulators on request

What Regulators Can See​

  • Compliance Events: PIIRequested, PIIReceived, validation logs
  • VASP Status: KYB status, public keys, master wallets
  • Quorum Outcomes: Validation proof signatures and scores
  • Audit Trails: Timestamps, hashes, and compliance metadata

What Regulators Cannot See (By Default)​

  • Decrypted PII or personal user details
  • Any data not explicitly shared by VASPs or validated by oracle

Regulatory Benefits​

  • Independent, tamper-proof audit capabilities
  • Visibility into identity flows across networks
  • Aligned with FATF, MiCA, and jurisdictional frameworks

Optional Escrow Access​

In some cases, regulators may:

  • Use multi-party escrow to decrypt specific data
  • Be assigned temporary shared decryption rights

📌 Next Step: Explore Audit Trails & Compliance Proofs