Skip to content
Menu

curvefi

Dev Tools

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 →

Curve-frontend is a user-interface DApp designed to connect to Curve's deployment of smart contracts.

What HEY knows

Building
Shipping consistentlyShipping: 4 meaningful events in 30 days; latest ship yesterday. Evidence Source

Build Momentum 47How it is measured

Latest ship
Code changes, week of 2026-10-12 – 2026-10-18 · 94 commits · · Code activity

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

FollowCreate alertTerminal previewView latest ship
Share

Follow puts curvefi 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 curvefi’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.

Product usage

Curve DEX: TVL $594K · fees 24h $2 · revenue 24h <$1 (DefiLlama, 2026-10-19). Registry context, not a measure of building.

Token market · context
No token tracked
Not yet known
Unknown4 gaps: Published packages (not enough yet), Official docs (no source), API description (not enough yet), Official site changes (not enough yet). Packages name its repository, but none is confirmed as the project’s own.

HEY can answer 7 of the 11 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: 4 meaningful events in the last 30 days, the newest 2026-10-18.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 94 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 165 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 135 commits+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.
Source6 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 94 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 165 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 135 commits+7 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
LinksWebsiteGitHubXSources

Latest ship

Checked

Code changes, week of 2026-10-12 – 2026-10-18 · 94 commitscurvefi/curve-frontend

Code activitySource linked

What changed, in the repository’s own words:

7 active days in curvefi/curve-frontend.

This week HEY looked inside 3 of 94 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

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

View evidence ↗

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

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

Is curvefi still being built?
DerivedShipping: 4 meaningful events in 30 days; latest ship yesterday. Evidence
What did curvefi ship last?
FactCode changes, week of 2026-10-12 – 2026-10-18 · 94 commits — Code activity, yesterday. Evidence
What does HEY not know about curvefi?
Unknown4 gaps: Published packages (not enough yet), Official docs (no source), API description (not enough yet), +1 more. Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

  1. Code changes, week of 2026-10-12 – 2026-10-18 · 1 commitcurvefi/docs

    Code activitySource linked

    1 active day in curvefi/docs.

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

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit (opens in a new tab)

  2. Code changes, week of 2026-10-05 – 2026-10-11 · 165 commitscurvefi/curve-frontend

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in curvefi/curve-frontend.

    This week HEY looked inside 3 of 165 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 165 commits (opens in a new tab)

  3. Code changes, week of 2026-10-05 – 2026-10-11 · 1 commitcurvefi/docs

    Code activitySource linked

    1 active day in curvefi/docs.

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

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit (opens in a new tab)

  4. Code changes, week of 2026-09-28 – 2026-10-04 · 135 commitscurvefi/curve-frontend

    Code activitySource linked

    What changed, in the repository’s own words:

    6 active days in curvefi/curve-frontend.

    This week HEY looked inside 3 of 135 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count. 3 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 135 commits (opens in a new tab)

  5. Code changes, week of 2026-09-28 – 2026-10-04 · 4 commitscurvefi/docs

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in curvefi/docs.

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

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 4 commits (opens in a new tab)

  6. Code changes, week of 2026-09-21 – 2026-09-27 · at least 117 commitscurvefi/curve-frontend

    Code activitySource linked

    What changed, in the repository’s own words:

    at least 4 active days in curvefi/curve-frontend since 2026-09-22; the count stops at the newest 100 commits listed.

    This week HEY looked inside 5 of 117 commits to see what changed: 3 changed code, 2 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · at least 117 commits (opens in a new tab)

  7. Code changes, week of 2026-09-21 – 2026-09-27 · 3 commitscurvefi/docs

    Code activitySource linked

    3 active days in curvefi/docs.

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

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 3 commits (opens in a new tab)

  8. Code changes, week of 2026-09-21 – 2026-09-27 · 2 commitscurvefi/curve-core

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in curvefi/curve-core.

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

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 2 commits (opens in a new tab)

  9. Code changes, week of 2026-09-14 – 2026-09-20 · at least 127 commitscurvefi/curve-frontend

    Code activitySource linked

    What changed, in the repository’s own words:

    at least 4 active days in curvefi/curve-frontend since 2026-09-15; the count stops at the newest 100 commits listed.

    This week HEY looked inside 3 of 127 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 127 commits (opens in a new tab)

  10. Code changes, week of 2026-09-14 – 2026-09-20 · at least 5 commitscurvefi/docs

    Code activitySource linked

    2 active days in curvefi/docs.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 5 commits to see what changed: 5 documentation or maintenance only. 2 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 5 commits (opens in a new tab)

  11. Code changes, week of 2026-09-14 – 2026-09-20 · at least 15 commitscurvefi/curve-core

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in curvefi/curve-core.

    This week HEY looked inside 2 of 15 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.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 15 commits (opens in a new tab)

  12. Code changes, week of 2026-09-07 – 2026-09-13 · at least 165 commitscurvefi/curve-frontend

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in curvefi/curve-frontend.

    This week HEY looked inside 3 of 165 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 165 commits (opens in a new tab)

  13. Code changes, week of 2026-08-31 – 2026-09-06 · at least 1 commitcurvefi/curve-frontend

    Code activitySource linked

    What changed, in the repository’s own words:

    4 active days in curvefi/curve-frontend.

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

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 1 commit (opens in a new tab)

  14. Code changes, week of 2026-08-17 – 2026-08-23 · at least 8 commitscurvefi/docs

    Code activitySource linked

    18 active days in curvefi/docs.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 8 commits to see what changed: 8 documentation or maintenance only. 3 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-08-17 – 2026-08-23 · at least 8 commits (opens in a new tab)

  15. Code changes, week of 2026-08-10 – 2026-08-16 · at least 7 commitscurvefi/curve-core

    Code activitySource linked

    What changed, in the repository’s own words:

    11 active days in curvefi/curve-core.

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

    View evidence: Code changes, week of 2026-08-10 – 2026-08-16 · at least 7 commits (opens in a new tab)

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 curvefi? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

17 changes on HEY’s record for curvefi: 1 build pace change · 16 weeks of code pushed.

All 17 changes for curvefi →

The full change record holds 1 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 11 research questions that apply.

7 of 11 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 18m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

  • Repository detailsMeasuredRead 22h ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Protocol economics

  • Protocol economicsMeasuredRead today.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, 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.

Sources

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