Skip to content

Kaskad

Lending

Is this your project? Claim it →

Kaskad is a non-custodial lending protocol on Igra, an EVM-compatible Layer 2 anchored to Kaspa.

What HEY knows

Development

Last shipped 17 days agoActive: 2 counted ships in 30 days; latest ship 17 days ago. Evidence Source

Build Momentum 32How it is measured

Latest: Code changes, week of 2026-11-02 – 2026-11-08 · 1 commit

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Kaskad on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow Kaskad

No account? Email me Kaskad’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

More detail
Product usage

Kaskad: TVL $336K · fees 24h not tracked · revenue 24h not tracked (DefiLlama, 2026-11-22). Registry context, not a measure of building.

Not yet known
Unknown2 gaps: API description (no source), Protocol economics (no source). Its website links no API description.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule: 2 counted ships in the last 30 days, the newest 2026-11-05.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-11-02 – 2026-11-08 · 1 commitCode changes, week of 2026-10-26 – 2026-11-01 · 3 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 1 commitWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found counted building from the project's own sources.
Source16 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-11-02 – 2026-11-08 · 1 commitCode changes, week of 2026-10-26 – 2026-11-01 · 3 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 1 commit+5 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Research coverage: HEY can answer 9 of the 11 research questions that apply.
9 of 11 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 1h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 19h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 6d ago.

Code and packages

  • Repository detailsMeasuredRead 23h ago.
  • Published packagesMeasuredRead 23h ago.

Protocol economics

  • Protocol economicsNo sourceDefiLlama lists the protocol but tracks no fees, revenue or volume for it.

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Market figures are context only and never change activity status. Methodology

Latest ship

Checked

Code changes, week of 2026-11-02 – 2026-11-08 · 1 commit kaskad-lending/kaskad-pontifex-enclave

Code activitySource-backed

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

What changed, in the repository’s own words:

1 active day in kaskad-lending/kaskad-pontifex-enclave.

This week HEY looked inside 1 commit to see what changed: 1 changed code.

Record ship:4db1fa44… · HEY counts it as building; it does not judge the release’s quality.

Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or a deployment: code is not a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it to the week of 2026-11-05; HEY first knew on 2026-11-07.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

Shared change · Verified Builder

Kaskad is now a Verified Builder: HEY checked its builder sources.

2 meaningful development events were recorded in the last 30 days. Builder status: Active.

Observed by HEY on 2026-10-30Source: HEY’s research record

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 7 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-10-26 – 2026-11-01 · 3 commits kaskad-lending/kaskad-nuntius

    Code activitySource-backed

    1 active day in kaskad-lending/kaskad-nuntius.

    How HEY read this week

    This week HEY looked inside 2 of 3 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

  2. Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit kaskad-lending/kaskad-pontifex

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in kaskad-lending/kaskad-pontifex.

    How HEY read this week

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

Other changes on HEY’s record

6 changes on HEY’s record for Kaskad: 1 new Verified Builder or owner proof · 1 official source change · 1 new project on HEY · 3 weeks of code pushed.

All 6 changes for Kaskad →

The full change record holds 8 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Sources

16 places HEY reads for Kaskad
8 more sources (docs)

Security context: 2 audit reports found. An audit shows an audit took place; it is not a guarantee of safety.