Oracle Integration
CRYMBO Oracle is a decentralized compliance engine that enables privacy-preserving identity verification and transaction policy enforcement on-chain. It links encrypted PII to on-chain transactions while keeping identity data off-chain, allowing institutions and wallets to remain compliant with MiCA, FATF, and jurisdictional frameworks.
This section explains how to integrate your smart contracts, services, or infrastructure with the CRYMBO Oracle.
What’s Included
- Oracle event interface (on-chain triggers)
- PII submission APIs (off-chain encryption + posting)
- Role-based access for VASPs and validators
- Cross-chain compliance validation
- Event tracking:
PIIRequested,PIIProvided,TransactionCompliant - Privacy-first compliance architecture
System Components
Oracle Smart Contract
The on-chain contract emits events based on transaction context (e.g. wallet metadata, jurisdictional flags, known VASP interactions).
It never stores PII — only emits events to request off-chain identity resolution.
Off-Chain PII Resolver
Each VASP (or validator) listens to Oracle events and submits encrypted identity payloads for their own users.
The payloads are linked by transaction hash but remain private and off-chain.
Oracle Events
| Event Name | Description |
|---|---|
PIIRequested | Oracle requests sender or receiver PII |
PIIProvided | A VASP submitted encrypted PII for a transaction |
TransactionCompliant | Oracle confirms compliance has been fulfilled |
These events are emitted as part of on-chain execution and can be subscribed to via RPC, node monitor, or webhook.
This section will guide you through writing to, listening for, and verifying compliance with the Oracle