Skip to content
Menu

EVM Chains

No narrative yet

Is this your project? Claim and verify →

A relatively complete source of EVM-compatible blockchain information. Data updates every day.

What HEY knows

Building
Dormant0 meaningful events in 30 days; no meaningful ship recorded yet. Details

Build Momentum 0How it is measured

Latest change
Derived18 days ago: Code changes, week of 2026-09-28 – 2026-10-04. Not counted as building. Evidence Source

Maintenance only, read from the team’s GitHub · not a new capability

What this change is
What it names
Maintenance only, not a new capability: 0 of 0 commits HEY read were documentation, dependency or maintenance changes, and none changed code.
Stage
Maintenance is not a new capability, and code is not a deployment.
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-01; HEY first knew on 2026-09-29.
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 preview
Share

Follow puts EVM Chains 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 EVM Chains’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
Dormant.
“Dormant” by the activity rule: 0 meaningful events in the last 30 days.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadWhat HEY derivedHEY’s activity rule reads the counted events as “Dormant”.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.
Source2 registered sources, 0 of them context only.ReadRecordssource:67ec5c92-7641-418e-b157-d989d560f0daWhat 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
LinksWebsiteGitHubSources

Latest ship

Checked

HEY has not recorded a source-backed update for this project yet.

Builder activity

No meaningful, source-backed updates in the 8 weeks since HEY began reading this project’s sources; earlier weeks are not yet read.

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

Is EVM Chains still being built?
DerivedDormant: 0 meaningful events in 30 days; no meaningful ship recorded yet. Details
What does HEY not know about EVM Chains?
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

Build timeline

  1. Code changes, week of 2026-09-28 – 2026-10-04 · 3 commits

    Code activitySource linked

    3 active days in amazingandyyy/evm-chains.

    Automated commits only — not counted as building. 5 automated commits (bot accounts or a repeating scripted message) not counted.

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

  2. Code changes, week of 2026-09-21 – 2026-09-27 · 7 commits

    Code activitySource linked

    7 active days in amazingandyyy/evm-chains.

    Automated commits only — not counted as building. 7 automated commits (bot accounts or a repeating scripted message) not counted.

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

  3. Code changes, week of 2026-09-14 – 2026-09-20 · at least 6 commits

    Code activitySource linked

    6 active days in amazingandyyy/evm-chains.

    Automated commits only — not counted as building. 6 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 6 commits (opens in a new tab)

  4. Code changes, week of 2026-09-07 – 2026-09-13

    Code activitySource linked

    75 active days in amazingandyyy/evm-chains.

    Automated commits only — not counted as building. 7 automated commits (bot accounts or a repeating scripted message) not counted.

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

  5. Code changes, week of 2026-08-31 – 2026-09-06

    Code activitySource linked

    74 active days in amazingandyyy/evm-chains.

    Automated commits only — not counted as building. 7 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 (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 EVM Chains? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

6 changes on HEY’s record for EVM Chains: 1 build pace change · 5 weeks of code pushed.

All 6 changes for EVM Chains →

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 2d 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 1d ago.
  • Published packagesMeasuredRead 1d 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