Audit Proof
Every compliance event in the CRYMBO Oracle produces a verifiable audit proof — a cryptographic record that can be independently verified by auditors, regulators, or compliance teams.
What Audit Proofs Contain
| Field | Description |
|---|---|
| Attestation ID | Unique identifier for the compliance event |
| Transaction Reference | On-chain transaction hash or internal ID |
| Compliance Rules Applied | Which regulations were evaluated |
| Validator Consensus | Which validators participated and how they voted |
| Timestamp | When the compliance event occurred |
| Block Reference | On-chain block where the attestation was published |
| Status | COMPLIANT, NON_COMPLIANT, PENDING, or EXEMPT |
Verification
Audit proofs can be verified:
- On-chain — By querying the attestation contract on the relevant blockchain
- Via API — Using the CRYMBO API to retrieve and validate attestation records
- Independently — By verifying validator signatures against their published public keys
Use Cases
- Annual audits — Provide auditors with complete compliance records for a given period
- Regulatory reporting — Generate jurisdiction-specific compliance reports
- Dispute resolution — Prove compliance status at the time of a specific transaction
- Internal compliance — Monitor compliance team performance and coverage