Skip to content

KrystalDeFi

No narrative yet

Integration record: a multichain project that lists Robinhood Chain. Its code is filed under other ecosystems and HEY holds no Robinhood Chain evidence of its own, so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim and verify →

Show full list of token via Debank API, then quick swap it

What HEY knows

Building
Shipped this weekShipping: 2 meaningful events in 30 days; latest ship today. Evidence Source

Build Momentum 33How it is measured

Latest ship
Code changes this week (since Mon 19 Oct) · 2 commits · · Code activity

Why it matters: First week of code changes after 25 quiet days.

FollowCreate alertTerminal previewView latest ship
Share

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

No account? Email me KrystalDeFi’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.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

HEY can answer 7 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 2 meaningful events in the last 30 days, the newest 2026-10-19.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 19 Oct) · 2 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 1 commitCode changes, week of 2026-09-14 – 2026-09-20 · at least 1 commit+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.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".
Researched.
HEY researched this project; the gate has not found verified building evidence from its own sources.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 19 Oct) · 2 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 1 commitCode changes, week of 2026-09-14 – 2026-09-20 · at least 1 commit+6 moreWhat HEY derivedThe quality gate’s stored decision: “Researched”.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.
Market figures are context only and never change activity status. Methodology

Latest ship

Checked

Code changes this week (since Mon 19 Oct) · 2 commitskrystaldefi/krystal-vault-contracts-v2

Code activitySource linked

1 active day in krystaldefi/krystal-vault-contracts-v2.

This week HEY looked inside 2 commits to see what changed: 1 changed code, 1 documentation or maintenance only.

Record ship:dd9bcd5e… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

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: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about KrystalDeFi — as of 2026-10-19

Is KrystalDeFi still being built?
DerivedShipping: 2 meaningful events in 30 days; latest ship today. Evidence
What did KrystalDeFi ship last?
FactCode changes this week (since Mon 19 Oct) · 2 commits — Code activity, today. Evidence
What does HEY not know about KrystalDeFi?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record. Details

Build timeline

  1. Code changes, week of 2026-09-21 – 2026-09-27 · 1 commitkrystaldefi/krystal-vault-contracts-v2

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in krystaldefi/krystal-vault-contracts-v2.

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

  2. Code changes, week of 2026-09-21 – 2026-09-27 · 1 commitkrystaldefi/krystal-core

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in krystaldefi/krystal-core.

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

  3. Code changes, week of 2026-09-14 – 2026-09-20 · at least 1 commitkrystaldefi/krystal-core

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in krystaldefi/krystal-core.

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

  4. Code changes, week of 2026-09-07 – 2026-09-13 · at least 1 commitkrystaldefi/krystal-core

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in KrystalDeFi/krystal-core.

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

  5. Code changes, week of 2026-08-31 – 2026-09-06 · at least 1 commitkrystaldefi/krystal-core

    Code activitySource linked

    What changed, in the repository’s own words:

    4 active days in KrystalDeFi/krystal-core.

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

  6. Code changes, week of 2026-08-31 – 2026-09-06 · 6 commitskrystaldefi/multi-swap-app

    Code activitySource linked

    1 active day in krystaldefi/multi-swap-app.

    This week HEY looked inside 1 of 6 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

  7. Code changes, week of 2026-08-17 – 2026-08-23 · at least 1 commitkrystaldefi/krystal-vault-contracts-v2

    Code activitySource linked

    1 active day in krystaldefi/krystal-vault-contracts-v2.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

  8. Code changes, week of 2026-07-13 – 2026-07-19 · at least 1 commitkrystaldefi/krystal-core

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in KrystalDeFi/krystal-core.

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

  9. v1.0.0krystaldefi/krystal-vault-contracts-v2

    GitHub releaseSource verified

    Beta release

  10. Release v2.0.5krystaldefi/krystal-core

    GitHub releaseSource verified

    Customizable Univ2 swap contract

  11. Release v2.0.4krystaldefi/krystal-core

    GitHub releaseSource verified

  12. v2.0.3krystaldefi/krystal-core

    GitHub releaseSource verified

    Fix kyber proxy

  13. v2.0.2 Bug fixeskrystaldefi/krystal-core

    GitHub releaseSource verified

    Fix 0 transfer amount, which can fail the transfer on some tokens .i.e DGX

  14. v2.0.1 Update new uni v3 contractkrystaldefi/krystal-core

    GitHub releaseSource verified

  15. v2.0.0 - New generic contracts on chainskrystaldefi/krystal-core

    GitHub releaseSource verified

  16. Deploy to Ethereumkrystaldefi/krystal-core

    GitHub releaseSource linked

  17. Deploy to BSC and Polygonkrystaldefi/krystal-core

    GitHub releaseSource linked

  18. Draft v2.0.0 release to support generic evm chainskrystaldefi/krystal-core

    GitHub releaseSource linked

  19. v1.0.0krystaldefi/krystal-core

    GitHub releaseSource verified

    Support BSC

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about KrystalDeFi? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

20 changes on HEY’s record for KrystalDeFi: 11 releases · 9 weeks of code pushed.

All 20 changes for KrystalDeFi →

The full change record holds 2 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 2m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1y ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

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

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

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.

Sources