DeFi Debt Markets
DebtWatch

An aggregator experiment that collects and organizes the entire Cardano debt market into actionable alpha for investors.

The Problem

Cardano's lending ecosystem is growing — but fragmented. P2P protocols and pool-based lending platforms each expose their own interfaces, their own data formats, and their own risk surfaces. There was no single place to answer the most basic investor questions: where is capital deployed, which positions are approaching liquidation, and what does the aggregate debt picture actually look like?

Without that visibility, participating in Cardano DeFi credit markets meant operating partially blind.

The Approach

Rather than building another lending protocol, the opportunity was in the data layer — an aggregator that normalizes and surfaces what already exists. The Cardano blockchain's UTxO model and on-chain data availability made it possible to index lending activity across protocols without relying on centralized APIs.

The goal was a tool that felt less like a dashboard and more like an intelligence feed: something an active participant would open before making a credit decision.

The Implementation

DebtWatch ingests and normalizes data across both P2P and pool lending markets on Cardano. The core features built around answering the questions that matter:

P2P & Pool markets — unified view across protocol types
Positions at risk — real-time flagging of under-collateralized loans approaching liquidation thresholds
Wallet intelligence — borrower and lender behavior analysis at the address level
Loan calculator — model borrow/lend scenarios against current market rates

Access is currently invite-only while the data layer is being hardened and coverage is expanded across new protocols.

The Outcome

DebtWatch is live in a closed testing phase. Early users have used it to identify liquidation opportunities and monitor their own credit exposure across protocols they couldn't previously track in aggregate.

The biggest lesson: data normalization across Cardano protocols is harder than it looks — each protocol makes different architectural choices that don't map cleanly to a shared schema. That normalization problem turned out to be the real engineering challenge, not the UI.

Next: broader protocol coverage, public access, and alerting for position health changes.

Get in touch for access →