Price feeds

Every money-market and liquidation decision in ClearPortX depends on a reliable price. This page documents how prices are sourced, validated, and ultimately consumed inside our contracts.

The source

ClearPortX integrates independently operated oracle networks that run on Canton Network as first-class participants. We do not operate our own oracle nodes; the price surface is externalized to reduce the attack surface on our contracts.

Multi-layer validation

Raw oracle prices do not reach the money-market contracts directly. They pass through a validation pipeline:

1. Signature verification — every price report is cryptographically signed by the oracle network and verified inside a Daml verifier contract before use.
2. Staleness check — reports older than a per-asset maximum age are rejected, forcing the reader to fetch a fresh report.
3. Deviation cross-check — prices are compared against an on-chain TWAP from the DLMM pools themselves. Large deviations trigger a soft halt.
4. Guardian circuit breaker — deviations beyond a hard threshold escalate to the Guardian for manual intervention before trading can resume.

Failure modes

The system is designed to fail safely in the following scenarios:

• Oracle offline: staleness check triggers, operations requiring fresh prices revert. User funds remain untouched.
• Single oracle compromised: median aggregation and cross-check with DLMM TWAP detect the deviation, halting affected markets before bad decisions are made.
• Coordinated oracle attack: Guardian can pause the entire lending module, preventing any state transition until the attack is resolved.

Full technical integration details, including the Verifier contract interface, will be published alongside the money market launch.