ChainLex — RWA Compliance Oracle
RWA compliance oracle: CRE workflow fetches GoPlus risk data and writes to ChainlinkRisk; third-party vaults gate deposits.
What it is
ChainLex is an AI-driven RWA (Real World Asset) compliance platform. Our hackathon deliverable, LexOracle Risk Guard, is a Chainlink CRE workflow that provides DON-attested compliance data for tokenized assets — functioning as a "Compliance Feed" with the same trust model as Chainlink Price Feeds.
Problem: Third-party protocols (e.g. vaults accepting RWA token deposits) cannot trust compliance data self-reported by token issuers — regulators flag this as a conflict of interest. They need independently verifiable, DON-attested data.
Solution: The CRE workflow (1) listens for on-chain Transfer events or runs on a cron, (2) fetches wallet risk data from GoPlus Security API, (3) aggregates results via DON BFT consensus, (4) writes to ChainlinkRisk on Sepolia. A deployed ComplianceVault contract gates deposits by calling ChainlinkRisk.isUserAllowed() — the vault trusts the DON, not the issuer.
We integrate blockchain (Sepolia) with an external API (GoPlus), demonstrate successful simulation via CRE CLI, and have broadcast real Sepolia transactions.
How it Works
Stack:
- CRE Workflow: Go/WASM, dual triggers (Cron + EVM Log for Transfer events)
- Data source: GoPlus Security API (public, no auth) for address risk flags
- Smart contracts: Solidity 0.8.29 — ChainlinkRisk (Compliance Feed), LexOracleConsumer (IReceiver with 3-layer DON verification), uRWA (ERC-7943 token), ComplianceVault (third-party consumer)
- Frontend: Next.js 15, React, Tailwind, shadcn/ui — LexOracle Dashboard showing real-time event feed, pipeline, and vault gate
- Deployment: Foundry for contracts on Sepolia; CRE simulate + broadcast for on-chain proof
Architecture:
GoPlus API → CRE DON (BFT consensus) → LexOracleConsumer.onReport() → ChainlinkRisk.updateRiskAssessment()
ChainlinkRisk ← ComplianceVault.checkCompliance() (third-party gate)
Links
Created by
- Jiajia Chen