Skip to content
Menu

RuneCurve

Launchpad

Is this your project? Claim and verify →

RuneCurve is a dual-chain protocol for launching Bitcoin Runes as reserve-backed tokens on Robinhood Chain.

What HEY knows

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

Build Momentum 25How it is measured

Latest ship
Code changes this week (since Mon 26 Oct) · 51 commits · · Code activity

Why it matters: The first week of code changes HEY has recorded for this project.

This change
Code changes, read from the team’s GitHub · not a deployment
What it names
3 of 3 commits 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-10-27; HEY first knew on 2026-10-27.
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.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts RuneCurve 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 RuneCurve’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 (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs.

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: 1 meaningful event in the last 30 days, the newest 2026-10-27.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 26 Oct) · 51 commitsWhat 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".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source3 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 26 Oct) · 51 commitssource:23a64377-da1c-4d99-8530-81f65881f28dsource:46c7ff4a-bc60-47d5-9e60-f5fc355bca71What 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.
Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)X (opens in a new tab)Sources

Latest ship

Checked

Code changes this week (since Mon 26 Oct) · 51 commits

Code activitySource linked

What changed, in the repository’s own words:

2 active days in runecurve/runecurve.

This week HEY looked inside 3 of 51 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:7bf16f0b… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗ (opens in a new tab)

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

Questions HEY can answer about RuneCurve — as of 27 Oct

Is RuneCurve still being built?
DerivedShipping: 1 meaningful event in 30 days; latest ship today. Evidence
What did RuneCurve ship last?
FactCode changes this week (since Mon 26 Oct) · 51 commits — Code activity, today. Evidence
What does HEY not know about RuneCurve?
Unknown3 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs. Details

What changed

3 changes on HEY’s record for RuneCurve: 1 verification change · 1 new project on HEY · 1 week of code pushed.

RuneCurve on What changed →

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 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 5h ago.

Building

  • Building activityMeasuredRead 29m 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 5h ago.
  • Published packagesMeasuredRead 5h 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