Follow puts MeiYanDong on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
“Active” by the activity rule's longer window: 2 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-08, is more than 30 days old.
This week HEY looked inside 2 of 5 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.
Record ship:cdb53567… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.
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: 2 weeks before HEY began reading this project’s sources — not yet read, not zero.
Questions HEY can answer about MeiYanDong — as of 2026-10-19
Is MeiYanDong still being built?
DerivedActive: 0 meaningful events in 30 days; latest ship 41 days ago.Evidence →
What did MeiYanDong ship last?
FactCode changes, week of 2026-09-07 – 2026-09-13 · 5 commits — Code activity, 41 days ago.Evidence →
What does HEY not know about MeiYanDong?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.Details →
Build timeline
Code changes, week of 2026-09-07 – 2026-09-13 · at least 7 commitsmeiyandong/robinhood-pair-liquidity
3 active days in MeiYanDong/robinhood-pair-liquidity.
This week HEY looked inside 2 of 7 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.
This week HEY looked inside 2 of 16 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.
This week HEY looked inside 2 of 20 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.
ClockIn Sniper v0.1.0 This is the first evidence-bound engineering release. Its production capability state is NOT_HOT_ARMED: it is a tested and packaged implementation, not proof of a profitable trade or authorization to broadcast. Traceability · Source commit…Show allShow less
ClockIn Sniper v0.1.0 This is the first evidence-bound engineering release. Its production capability state is NOT_HOT_ARMED: it is a tested and packaged implementation, not proof of a profitable trade or authorization to broadcast. Traceability
https://github.com/MeiYanDong/robinhood-chain-launchpad-dashboardContext onlyContext only because HEY found this repository by its owner alone and nothing the project controls ties it to the project; it counts once a moderator accepts it, or once the project’s verified owner adds it and a GitHub claim names it, it names the token’s contract, it carries a Robinhood Chain dedication HEY matched to this project, or its homepage is the project’s own site (one the owner did not type in).
HEY keeps these on record as context. None counts toward the activity status or Build Momentum; each says why.
Code activityCode changes, week of 2026-09-14 – 2026-09-202026-09-17Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.
GitHub releasev0.17.22026-09-08Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.
GitHub releasev0.17.12026-09-08Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.
