Token unverified: The project’s own site named this contract when HEY read it, but the site has not answered HEY’s reads since. HEY keeps that reading as context and does not treat the token as confirmed until the site answers again. Token market
Contract 0x503be5eeb51c2653fd8e84b049849a358e3d5555
The gene that mews. Mix original mutant cats. Four organs. Keep the wrong ones.
Build Momentum 0How it is measured
Why it matters: The first week of code changes HEY has recorded for this project.
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.
Follow puts Meogen on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
Or read its RSS feed.
Counted from the chain. Usage says the contracts are used, not that anyone is building.
HEY can answer 14 of the 19 research questions that apply · Research coverage
Checked
Code activitySource linked
What changed, in the repository’s own words:
2 active days in meogenxyz/meogen.
This week HEY looked inside 4 of 21 commits to see what changed: 1 changed code, 3 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.
Record ship:04ed2194… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.
Shared change · Verified Builder
Builder status: Quiet.
Observed by HEY on 2026-10-11Source: HEY’s research record
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 Meogen? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.
3 changes on HEY’s record for Meogen: 1 verification change · 1 token verification change · 1 week of code pushed.
Token verification moved from Verified to Unverified
Research standing moved from Published to Verified builder
Code changes, week of 2026-08-31 – 2026-09-06 · 21 commits
The full change record holds 3 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)
HEY can answer 14 of the 19 research questions that apply.
Not applicable here: Package advisories, 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.
Posts by @meogenXYZ, as HEY last read them. Context only: a post is never counted as building and never sets the activity status.
Observed after, over 7 days: calls 2.7/day · volume $206/day · active contracts 1.
Code changes, week of 2026-08-31 – 2026-09-06 · 21 commitsCode activityin the week of 31 Aug (week precision)
| Measure | Observed before24–30 Aug | Observed after7–13 Sep |
|---|---|---|
| Volume per day | Not measured: HEY began reading this market’s price, liquidity and volume on 2026-09-06, during this ship’s week | $206/day |
| Calls per day | Not measured: HEY began counting this project’s calls on 2026-09-05, during this ship’s week | 2.7/day |
| Calls to own functions per day | Not measured: HEY began counting this project’s calls on 2026-09-05, during this ship’s week | 0 |
| Active contracts (busiest day) | Not measured: HEY began counting this project’s calls on 2026-09-05, during this ship’s week | 1 |
| Distinct caller addresses (busiest day) | Not measured: HEY began counting this project’s calls on 2026-09-05, during this ship’s week | 17 of 7 days |
Not shown: Price and valuation: the market is not live · Liquidity: not a market reading — the launch pool holds the token’s own supply
Observed around the same time — HEY does not claim this event caused it.
Market context and product usage, placed by time. Seven days either side; the day in progress is never compared. Open evidenceAs data
