202602251610-sky-spark-vs-defi-data-comparison

🎯 Core Idea

This card is a research scaffold for comparing Sky and Spark against other DeFi products using publicly available data dashboards. The goal is not to declare a winner. The goal is to create a repeatable checklist so a non-expert can build intuition from consistent metrics.

A useful starting point is to separate three kinds of data:

Scale and composition data
- TVL, chain distribution, asset mix
Activity and demand data
- borrows, utilization, cashflows, user flows
Governance and control-plane data
- how changes are proposed, reviewed, ratified, and executed

What tends to make Sky and Spark feel different in data

Multi-line products: Spark has distinct lines (Savings, Spark Lend, Spark Liquidity Layer). Many protocols are primarily one line.
Allocation and balance-sheet behavior: some parts of Spark behave like capital allocation across venues rather than a single onchain pool.
Governance artifacts: Sky has a spec-like governance document (Sky Atlas) and structured processes that can be mapped to onchain changes.

Comparison checklist (what to look at)

Basic scale

protocol TVL
TVL by chain
top assets / collateral mix

Lending demand (if applicable)

total supply and total borrow
utilization trends
stable versus volatile collateral composition

Yield products

deposits and outflows
headline rate and how often it changes
whether yield appears subsidy-driven

Revenue and sustainability

fees and revenue
incentive dependence

Risk and concentration

concentration by asset
concentration by counterparty or protocol bucket
known risk committees or emergency mechanisms

Governance throughput

number of proposals per month
time from proposal to execution
who can propose and who must review

How to use DeFi dashboards efficiently

Start with DeFiLlama for TVL and chain distribution.
For deeper metrics (revenue, fees, user flows), you often need Token Terminal, Dune, or first-party dashboards.
Prefer first-party dashboards when they provide clear definitions for metrics.

🌲 Branching Questions

➡ Which 2–3 competitors should I use as the default comparison set (Aave, Morpho, Curve, Ethena, etc.) and why?

A good default comparison set depends on what you want to learn.

If your focus is Spark as a lending product:

Aave
- the baseline for large, multi-chain, generalized lending markets
- Spark Lend is described publicly as built on Aave v3 code, so the comparison is conceptually close
Morpho
- a leading alternative lending design with a different market structure and risk surface
- useful for comparing capital efficiency and how much of the market is driven by organic borrowing versus incentives

If your focus is Sky as a stablecoin and capital allocation system rather than only lending:

Frax or Liquity
- stablecoin designs that can be contrasted with Sky’s governance-heavy approach

A practical default that stays small and useful is:

Aave and Morpho for lending
one stablecoin-oriented competitor (Frax or Liquity) for system-level comparison

➡ For Sky and Spark, what are the three most meaningful metrics that are hard to game compared to TVL?

TVL is easy to inflate with incentives and short-term capital.

Three metrics that are usually harder to game:

Total borrow and utilization for lending

total borrow reflects real demand and willingness to pay
utilization approximates how productive the supplied capital is

Net revenue or net interest margin

if you can compare revenue to incentives, you can see whether growth is subsidized
net metrics resist vanity TVL if incentives are required to sustain it

Concentration and risk distribution

top asset concentration, top counterparty concentration, and top chain concentration
systems with fragile concentration look good in TVL until they do not

For Sky specifically, peg stability and liquidity depth are also high-signal because they reflect market trust.

➡ How should I compare multi-line products like Spark to single-line products without misleading myself?

Do not compare only one aggregate number.

A practical method:

Decompose Spark into lines

Savings
Spark Lend
Spark Liquidity Layer

Choose line-specific primary metrics

Savings: total supply, net inflows, headline rate changes, composition
Lend: total supply, total borrow, utilization, collateral mix
Liquidity Layer: AUM, allocation concentration, and drawdown behavior

Only then compare to single-line protocols

For a lending-only competitor, compare it only to Spark Lend metrics, not to the entire Spark footprint.

Use a system-level lens separately

for Sky and Spark as a combined system, compare balance-sheet behavior and governance control-plane data

This avoids mixing a system-level product with a single pool product.

➡ What is the best way to detect subsidy-driven growth from public data?

Subsidy-driven growth usually has these observable signals:

TVL and deposits rise without matching growth in borrow demand or revenue.
headline yield is consistently above market rates with no clear source.
growth drops sharply when incentives or rate promotions end.

Practical checks:

Compare revenue and incentives

if available, compare protocol fees or net revenue to token incentives

Track persistence

monitor the same metric one to four weeks after an incentive change

Look at utilization and borrow spreads

in lending, real demand tends to show up in borrow growth and utilization

Prefer first-party definitions when possible

third-party dashboards can differ; the best signal is consistency in one source over time

➡ What first-party dashboards should be considered canonical for Sky and Spark, and what definitions do they use?

For Spark, the most practical first-party sources are:

Spark documentation
- describes the product boundaries and governance structure
- https://docs.spark.fi/
Spark data dashboards
- Savings, Spark Lend, Spark Liquidity Layer dashboards
- https://data.spark.fi/
Spark dashboard API
- the underlying JSON endpoints used by the dashboard
- example endpoints include:

For Sky, the canonical sources are more about governance artifacts:

Sky Atlas
- governance spec-like document
- https://sky-atlas.io/
Sky governance voting portal
- on-chain ratification surface
- https://vote.sky.money/
Sky forum
- proposal discussion layer
- https://forum.sky.money/

In general, first-party sources are canonical for definitions, while third-party dashboards are best for fast comparisons.

➡ What governance or process metrics are most predictive of long-term protocol quality (throughput, reversibility, incident response)?

A few high-signal governance metrics:

Time to ship
- time from proposal to execution
- long delays can mean process fragility or political gridlock
Reversibility and rollback behavior
- how quickly a bad decision can be undone
- whether emergency mechanisms exist, and how often they are used
Incident response quality
- clarity of communication
- speed of mitigation
- completeness of postmortems
Role clarity
- who can propose
- who must review
- who can execute

These metrics matter because DeFi protocols are software systems with adversarial environments. Good governance behaves like good change management.

➡ What is a minimal weekly routine (15 minutes) to keep up with Sky and Spark using these dashboards?

A simple routine:

Spark scale snapshot

check Savings supply and rate
check Spark Lend total borrow and utilization
check Liquidity Layer AUM and any large allocation shifts

Governance scan

check the Sky forum for new Spark Prime threads
check vote.sky.money for active votes

Write one line of notes

record any major delta or new proposal link

The key is consistency. A small weekly delta log builds intuition faster than occasional deep dives.