Integration record: HEY holds no Robinhood Chain evidence for this project (no token, contract or registry listing on the chain), so its ships are recorded here but it is not a Verified Builder.
Follow puts Ethereum Data on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
“Quiet” by the activity rule: 0 counted ships in the last 30 days, the newest 2026-09-21.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-21 – 2026-09-27 · 10 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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".
Research coverage: HEY can answer 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.
Identity
IdentityMeasuredRead 46d ago.
Building
Building activityMeasuredRead 21h ago.
RepositoriesMeasured
ReleasesMeasured
TimelineMeasured
Official site
Official docsNo sourceHEY read its website and found no link to docs.
API descriptionNo sourceIts website links no API description.
Official site changesMeasuredRead 14d ago.
Code and packages
Repository detailsMeasuredRead 2d ago.
Published packagesMeasuredRead 2d ago.
Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, 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.
Market figures are context only and never change activity status. Methodology
This week HEY looked inside 1 of 10 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.
Record ship:feca905e… · 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-09-21; HEY first knew on 2026-09-21. HEY indexed it later, as history.
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: 5 weeks before HEY began reading this project’s sources — not yet read, not zero.
What changed
2 changes on HEY’s record for Ethereum Data: 1 new Verified Builder or owner proof · 1 week of code pushed.
The full change record holds 2 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)
Named in code or runs on a hook, read from public code and the chain: a link, never a partnership or an on-chain interaction. A code link is a reference: the code names the token, which shows neither a dependency nor use; only a hook link is a pool running on the other’s hook. As data
