Proof Generation

Dual-proof architecture: STARK (trustless) + Groth16 (on-chain verifiable). Partial success is valid.

Dual-proof (STARK + Groth16) with privacy-preserving options. Early-stage stack.

API key (optional)

Proof mode

JediSwap Metrics

Utilization (bps)

Volatility (bps)

Liquidity (0-3)

Audit score (0-100)

Age (days)

Ekubo Metrics

Utilization (bps)

Volatility (bps)

Liquidity (0-3)

Audit score (0-100)

Age (days)

Dual-Proof Architecture

STARK (Stone/Integrity) — Trustless verification via transparent setup. Proof verified by Starknet node via call_contract. Fact registered in ObsqraFactRegistry (~5K steps). Cannot invoke on-chain directly (exceeds 10M step limit).

Groth16 (Circom/Garaga) — On-chain verifiable via Garaga verifier contract (fits within 10M step limit). Requires trusted setup, but the STARK binding neutralizes this: the STARK fact_hash is a public input in the Groth16 proof, tying both together.

Partial success — Either proof system succeeding independently is a valid result. Both succeeding gives the strongest guarantee: trustless verification + on-chain verifiability.