Cross-protocol risk view
Reprieve merges positions from multiple lending venues into a single health view instead of forcing users to monitor each protocol separately.
Reprieve
Cross-protocol liquidation protection
Powered by Chainlink CRE x Data Feeds x CCIP
Stop liquidation risk before it compounds across chains.
Reprieve is a professional monitoring and rescue interface for DeFi users with exposure across Aave, Compound, and Morpho. A per-user CRE workflow watches position health, simulates rescue actions, routes capital with same-chain priority, and records the proof on-chain.
Live rescue posture
One workflow handling detection to proof.
CRE Active
Aggregate health factor1.31
Aave Arbitrum
At risk
HF 1.08
Morpho Arbitrum
Stable
HF 1.82
Compound Base
Reserve source
HF 2.14
Cron-triggered health checks
Priority queue for same-chain rescue
CCIP escalation path
Immutable on-chain execution log
Product overview
Reprieve turns fragmented DeFi monitoring into a single rescue system.
The project focuses on preemptive liquidation protection. Users configure a personal rescue strategy, define health and budget thresholds, and let a CRE workflow handle monitoring and execution. The interface then surfaces live state, rescue readiness, and the final audit trail.
Autonomous CRE execution
Each user strategy is encoded into a dedicated CRE workflow so monitoring, decisioning, and execution do not depend on a centralized bot.
Verified rescue trail
Every rescue action produces a durable audit record with chain, protocol, amount, and execution context for downstream review.
CRE workflow
How the CRE workflow works on this project
Reprieve uses a per-user Chainlink Runtime Environment workflow as the coordination layer. It is not just sending alerts. It continuously checks risk, decides the rescue path, validates the execution, and records the result as a verifiable log.
01
Detect
Scheduled CRE checks monitor positions, read Chainlink Data Feeds, and collect off-chain risk inputs before liquidation risk is visible in the UI.
02
Evaluate
The workflow computes aggregate health, checks budget caps, ranks venues by rescue priority, and prepares the exact action plan.
03
Simulate
Preflight simulation validates the rescue before execution so bad routes fail early instead of wasting budget mid-incident.
04
Rescue + Log
If same-chain liquidity is insufficient, CCIP routes collateral across chains and the workflow writes an immutable on-chain rescue record.
Execution policy
Same-chain first, cross-chain only when necessary.
CronTrigger runs health checks before liquidation thresholds are reached.
Data Feeds provide price inputs, while off-chain quant signals enrich the risk model.
Priority queues determine which protocol should fund the rescue first.
CCIP and rescue escrow act as the fallback path when liquidity must move across chains.
Coverage
Built for multi-venue, multi-chain rescue operations.
The frontend presents the product as a clear operator surface: setup for strategy deployment, dashboard monitoring for health and budget posture, and on-chain logs for post-incident verification.
Aave
Position state is represented as part of a unified rescue decision instead of an isolated protocol alert.
Compound
Position state is represented as part of a unified rescue decision instead of an isolated protocol alert.
Morpho
Position state is represented as part of a unified rescue decision instead of an isolated protocol alert.
Demo routes
Explore the landing page, then move directly into the product surfaces.
The current implementation is a demo-ready frontend with mock data and deterministic rescue flows. It is designed to explain the product clearly while preserving access to the monitoring, setup, and audit experiences.