Skip to content

Kalyx Mao Engine

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.

Is this your project? Claim it →

What HEY knows

Development

Last shipped 34 days agoActive: 0 counted ships in 30 days; latest ship 34 days ago. Evidence Source

Build Momentum 16How it is measured

Latest: Code changes, week of 2026-09-28 – 2026-10-04 · 10 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts Kalyx Mao Engine 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 Kalyx Mao Engine

No account? Email me Kalyx Mao Engine’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
Active.
“Active” by the activity rule's longer window: 2 counted ships in the last 45 days (the rule needs at least 2); the newest, 2026-10-02, is more than 30 days old.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 10 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 66 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 96 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 20h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • 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 19h ago.
  • Published packagesMeasuredRead 19h 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

Latest ship

Checked

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

Code activitySource-backed

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

4 active days in a-nuel/kalyx-mao-engine.

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:caaddaa3… · HEY counts it as building; it does not judge the release’s quality.

Shared change · Verified Builder

Kalyx Mao Engine is now a Verified Builder: HEY checked its builder sources.

Builder status: Active.

Observed by HEY on 2026-09-20Source: HEY Signal

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-10-26 – 2026-11-01 · 1 commit

    Code activitySource-backed

    1 active day in a-nuel/kalyx-mao-engine.

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

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

    Code activitySource-backed

    6 active days in a-nuel/kalyx-mao-engine.

    How HEY read this week

    This week HEY looked inside 3 of 66 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. Code changes, week of 2026-09-14 – 2026-09-20 · at least 96 commits

    Code activitySource-backed

    at least 2 active days in a-nuel/kalyx-mao-engine since 2026-09-19; the count stops at the newest 100 commits listed.

    How HEY read this week

    This week HEY looked inside 3 of 31 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.

Other changes on HEY’s record

5 changes on HEY’s record for Kalyx Mao Engine: 1 new Verified Builder or owner proof · 4 weeks of code pushed.

All 5 changes for Kalyx Mao Engine →

The full change record holds 1 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 Kalyx Mao Engine