Skip to main content

Audit Trails & Compliance Proofs

CRYMBO Oracle generates secure and verifiable audit trails for all compliance events related to identity exchange. These trails serve as proof of regulatory adherence for VASPs, regulators, and third-party auditors.

What’s Included in an Audit Trail?​

  • Event Metadata: Event type, txHash, timestamp, sender & receiver
  • Validation Logs: Signed results from validators
  • VASP IDs: Master wallet + KYB status
  • Compliance Status: Whether PII exchange was completed successfully

Use Cases​

  • Regulatory reporting and audits
  • Legal dispute resolution
  • Partner due diligence
  • Network-wide compliance monitoring

How Proofs Are Constructed​

  1. Oracle logs all key compliance events on-chain
  2. Off-chain systems record validator signatures and validation status
  3. Data is combined into a tamper-evident compliance record
  4. Hashes and Merkle roots (optional) are published to ensure integrity

Accessing Proofs​

  • Regulators: Via audit dashboards or API
  • VASPs: From their CRYMBO dashboard or API export
  • Auditors: Provided by the VASP or with granted audit token

Long-Term Storage​

  • Proofs are stored indefinitely in an encrypted metadata store
  • Public events remain on-chain for permanent traceability
  • Private validator logs are retained per CRYMBO policy

Proof Structure (Sample)​

{
	"txHash": "0xabc...",
	"event": "PIIReceived",
	"timestamp": 1713600000,
	"validators": [{ "address": "0x123...", "signature": "0x...", "result": true }],
	"status": "validated",
	"vaspId": "CRY-0082"
}

📌 Next Step: Learn about Real-Time Monitoring & Hooks