Key Links

• GitHub: https://github.com/jmakwana0x1/UHI-Project
• Deck / Slides: https://uhi-project.vercel.app/CrossHedge-Pitch-Deck.html
• Demo Video: https://www.youtube.com/watch?v=MDP-ZVi1KDs
• Live Project: https://uhi-project.vercel.app/crosshedge.html

Partner Integrations

Reactive Network isn't an integration in CrossHedge, it's the load-bearing wall.

The entire matching engine is three Reactive Smart Contracts live on Lasna:

• MatchingRSC subscribes to LPPositionOpened events on both Unichain Sepolia and Base Sepolia simultaneously, maintains a candidate pool, runs 4-gate pair matching (sign, horizon, gamma, correlation) on every Cron10 tick, and delivers recordMatch callbacks to the registries on both origin chains.
• Two StrategyRSCs (one per chain) ingest price snapshots on Cron100, maintain a realized-volatility EMA fully on-chain with no oracle, and trigger ERC-4626 vault rebalances via cross-chain callback.

We use Reactive as three things at once:

1. A matching engine
2. An oracle-free market-data feed
3. A cross-chain settlement layer

The RSCs are composed: one RSC's output event (PairMatched) becomes another contract's input on two destination chains. That composition is not possible on any other infrastructure we evaluated.

It's all verifiable on-chain today.

The keystone transaction is a PairMatched on Lasna (block 3,717,881) pairing two opposite-delta LPs from different chains, with both Callback events marked "successfully delivered and confirmed" to Unichain and Base, where the registries emit MatchRecorded, full cross-chain match closed in under two minutes.

All three RSCs are verified via Sourcify, Reactive's canonical verifier, and the README maps every claim to a clickable tx and every component to its source file.

We also did the homework on why Reactive specifically.

Our cost analysis (full derivation, sensitivity tables, and a reproducible Python script in the repo) shows the same workload costs: