Skip to content
HEY Research Lab
Menu

Chainrom Archive

Is this your project? Claim it →

Verified archive of the chainrom reader and its on-chain data, kept so the project can be continued.

What HEY knows

Development

Quiet for 46 daysQuiet: 0 counted ships in 30 days; latest ship on 2026-09-19. Evidence Source

Build Momentum 0How it is measured

Latest: v0.1.0: first complete archive

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts Chainrom Archive 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 Chainrom Archive

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

View latest ship
Share
More detail
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Quiet.
“Quiet” by the activity rule: 0 counted ships in the last 30 days, the newest 2026-09-19.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv0.1.0: first complete archiveCode changes, week of 2026-09-14 – 2026-09-20 · 40 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".
Verified Builder.
The quality gate found counted building from the project's own sources.
Source1 registered source, 0 of them context only.ReadRecordsv0.1.0: first complete archiveCode changes, week of 2026-09-14 – 2026-09-20 · 40 commitssource:e9d02afc-09d0-435d-a490-b1ad8dd46d42What 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 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 19h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 46d 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 7d ago.
  • Published packagesMeasuredRead 7d 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
LinksGitHub (opens in a new tab)Sources

Latest ship

Checked

v0.1.0: first complete archive

GitHub releaseSource-backed

Why it matters: The first release HEY has recorded for this project.

First complete snapshot of the chainrom archive, taken 2026-09-19 from upstream commit f6e8fc3. This is an unofficial archive; the original project is Bubbleduck10/chainrom. Contents · The site as published, plus a byte-exact capture of the 26 files the browser receives, with… Show all
  • First complete snapshot of the chainrom archive, taken 2026-09-19 from upstream commit f6e8fc3. This is an unofficial archive; the original project is Bubbleduck10/chainrom. Contents
  • The site as published, plus a byte-exact capture of the 26 files the browser receives, with headers
  • 4 ROMs and their 31 chunk contracts, verified against the sealed on-chain hashes
  • Engine .js, .wasm and README.txt extracted from every ROM
  • Creation and setup transactions of all contracts, with full inputs and receipts
  • Creator records from the block…

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

Release, read from the team’s GitHub · no deployment linked
What it names
The team’s release names it: “v0.1.0: first complete archive”.
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
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 established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to 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 2026-09-19 17:10 UTC; HEY first knew on 2026-09-20. HEY indexed it later, as history.
Not known
  • HEY does not hold the commit the release was cut from.
  • HEY has not observed a deployment of this change.
  • Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.

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.

View evidence ↗ (opens in a new tab)Post this ship on X

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.

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-09-14 – 2026-09-20 · 40 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in chainrom-cto/chainrom-archive.

    How HEY read this week

    This week HEY looked inside 5 of 40 commits to see what changed: 3 changed code, 1 documentation or maintenance only, 1 could not be classified. 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 · 40 commits (opens in a new tab)

Other changes on HEY’s record

3 changes on HEY’s record for Chainrom Archive: 1 release · 1 new Verified Builder or owner proof · 1 week of code pushed.

All 3 changes for Chainrom Archive →

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)

Sources

1 place HEY reads for Chainrom Archive