Skip to main content

Proof Mechanism

The CRYMBO Oracle uses a cryptographic proof mechanism to ensure that compliance attestations are verifiable, tamper-resistant, and auditable.

How Proofs Work​

  1. Validator signs — Each participating validator cryptographically signs their validation result
  2. Aggregation — The Oracle aggregates signed results from multiple validators
  3. Consensus threshold — A configurable quorum threshold must be met (e.g., 2/3 of validators agree)
  4. Attestation generated — A composite attestation is created, containing the consensus result and validator signatures
  5. On-chain publication — The attestation is published to the relevant blockchain
  6. Verification — Any smart contract or party can independently verify the attestation

Attestation Structure​

{
  "attestationId": "att_abc123",
  "transactionHash": "0x...",
  "chain": "ethereum",
  "status": "COMPLIANT",
  "rules": ["FATF_TRAVEL_RULE"],
  "validators": ["val_1", "val_2", "val_3"],
  "signatures": ["sig_1", "sig_2", "sig_3"],
  "timestamp": "2026-02-11T10:00:00Z",
  "blockNumber": 12345678
}

Verification​

Smart contracts can verify attestations on-chain:

function isCompliant(bytes32 attestationId) public view returns (bool) {
    return crymboOracle.verifyAttestation(attestationId);
}

Immutability​

Once published, attestations cannot be altered. If a compliance status changes (e.g., new sanctions data), a new attestation is generated — the original remains as a historical record.