Contract 0xa15cd06dd305269a0f48bebeb30aa3588fba7b32
HEY holds 121 other Robinhood Chain tokens that use $MERRYMEN. This page is only the contract above. See them
MERRYMEN ,your own band of autonomous trading agents. WE run 24/7 on your machine, trade only within your on chain permission walls, and never take custody of your funds. Name them. Chat with them.
Build Momentum 65How it is measured
Why it matters: One of 7 meaningful events in the last 30 days: building continued, not a one-off.
Follow puts Merrymen 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.
It compares building with market attention; it is not a prediction and not a reason to trade.
Counted from the chain. Usage says the contracts are used, not that anyone is building.
HEY can answer 15 of the 19 research questions that apply · Research coverage
Checked
Code activitySource linked
What changed, in the repository’s own words:
7 active days in millw14/merrymen.
This week HEY looked inside 3 of 42 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.
Record ship:9cb55a56… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.
Shared change · Release
7 meaningful development events were recorded in the last 30 days. Builder status: Shipping.
Dated 2026-10-16 by the sourceSource: github
GitHub releaseSource verified
GitHub releaseSource verified
Code activitySource linked
What changed, in the repository’s own words:
7 active days in millw14/merrymen.
This week HEY looked inside 3 of 281 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.
Code activitySource linked
What changed, in the repository’s own words:
7 active days in millw14/merrymen.
This week HEY looked inside 4 of 75 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.
Code activitySource linked
What changed, in the repository’s own words:
at least 3 active days in millw14/merrymen since 2026-09-25; the count stops at the newest 100 commits listed.
This week HEY looked inside 4 of 73 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.
GitHub releaseSource verified
The native merrymen app for Android — Kotlin and Jetpack Compose — replacing the Expo demo. Your agent's book, its chat, the feed, trades and orders, the leaderboard, agent profiles and the group chat, against the hosted service at app.merrymen.dev (or your own merrymen server, set in Settings). Sign in with the same account you use on the web. The app holds no private key. Signing in, your agent's permission, its trading limits, adding funds and withdrawing open the web app's own screen inside the app; only your session comes back. Install 1. Download merrymen-0.2.0.apk below and…
Code activitySource linked
What changed, in the repository’s own words:
at least 5 active days in millw14/merrymen since 2026-09-16; the count stops at the newest 100 commits listed.
This week HEY looked inside 3 of 171 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.
GitHub releaseSource linked
GitHub releaseSource linked
Code activitySource linked
What changed, in the repository’s own words:
5 active days in millw14/merrymen.
This week HEY looked inside 3 of 203 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.
GitHub releaseSource linked
GitHub releaseSource linked
GitHub releaseSource linked
GitHub releaseSource linked
GitHub releaseSource linked
Code activitySource linked
What changed, in the repository’s own words:
4 active days in millw14/merrymen.
This week HEY looked inside 3 of 219 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.
GitHub releaseSource verified
This is the one that starts. 0.1.0 and 0.1.1 abort on launch on every Android 14+ device — delete them. What was actually wrong Self-inflicted, in two steps. expo-screen-capture was added to stop the recovery phrase being screenshotted. Inspecting the resulting APK showed it had pulled in android.permission.DETECT_SCREEN_CAPTURE. That looked like an unexplained permission for a wallet, so it was blocked. It is not optional. ScreenCaptureModule.kt registers a screen-capture callback inside OnCreate on Android 14+, with no permission check, at module creation — whether or not…
GitHub releaseSource verified
## ⚠️ Broken — do not install > > This build also aborts on launch on every Android 14+ device. > > Use Android demo 0.1.2 instead. > > These notes originally claimed this release fixed the 0.1.0 crash. That was > wrong. The TextDecoder polyfill problem described below is real and the fix > is kept, but it was never the cause of the crash. > > The actual cause was android.permission.DETECT_SCREEN_CAPTURE being blocked > in app.json while expo-screen-capture was installed. That library > registers a…
GitHub releaseSource verified
## ⚠️ Broken — do not install > > This build crashes on launch on every Android device. It is kept only so > the link in older messages resolves to an explanation instead of a 404. > > Use Android demo 0.1.2 instead. (0.1.1 is also broken.) > > The cause given below was WRONG — see 0.1.2 for the real one > (DETECT_SCREEN_CAPTURE blocked while expo-screen-capture was installed). > > Original, incorrect diagnosis: polyfills.ts asserts TextDecoder exists and throws if it does not — > the first code the app runs. The…
GitHub releaseSource verified
The one-click Windows build — bundles Node, boots the agent worker and the dashboard, opens it in a native window. No terminal, no npm. 147 MB, down from 260 MB in 0.1.6. Why it shrank That drop is a bug fix, not better compression. The desktop app depends on merrymen as a local path, which npm resolves to a symlink pointing at the repo root. The packager followed that symlink and copied the entire tree — including the build output directory holding previously built installers. Every release was packaging the previous release inside itself. 0.1.6 went out carrying 0.1.5; the…
GitHub releaseSource verified
GitHub releaseSource verified
Security update. The dashboard had a flaw where a malicious webpage could slip past the browser-origin guard and reach merrymen's API on your own machine — including the recovery endpoint. If you installed 0.1.4, please update. Keys and caps were never the weak point; the guard in front of the dashboard was. Bundles merrymen 0.17.0.
Down 55.9% from the HEY-tracked high, with 4 verified updates since.
A factual observation about past activity and market context. It is not a prediction, and not investment advice.
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 Merrymen? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.
33 changes on HEY’s record for Merrymen: 16 releases · 2 contracts in use again or for the first time · 1 market check · 4 build pace changes · 10 other changes in 2 more kinds.
Code changes this week (since Mon 12 Oct) · 42 commits
Android 0.4.1
3 meaningful ships in the 7 days to 16 Oct, 1 the 7 days before
Trading fell from 1,414 trades a day (the seven days to 2026-07-22) to 141 a day in the seven days to 2026-10-12, in HEY's decoded on-chain trades.
Code changes, week of 2026-10-05 – 2026-10-11 · 281 commits
The full change record holds 6 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)
HEY can answer 15 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.
Observed after, 17 Oct so far: price −2.1% (before: +9.1%) · calls 357/day (before: 670/day) · volume $5.2K/day (before: $19K/day).
The latest ship, in the week of 12 Oct (week precision) — the week is in progress, 12–17 Oct so far, is too recent to compare: the days after it have not begun. This is the newest ship whose days after HEY has observed.
Android 0.4.1GitHub releaseon 16 Oct
| Measure | Observed before9–15 Oct | Observed after17 Oct so far |
|---|---|---|
| PriceAround this event:down 15.5 percent over the day· 15 Oct–16 Oct closes | up 9.1 percent over 7 days | down 2.1 percent over the day16 Oct–17 Oct closes so far |
| Volume per day | $19K/day | $5.2K/day1 of 7 days so fardown 72.8 percent against the days beforevs beforeagainst before |
| Liquidity | $97.7K | $87.1Kat 17 Oct so fardown 10.8 percent against the days beforevs beforeagainst before |
| Valuation | $375K | $310Kat 17 Oct so fardown 17.2 percent against the days beforevs beforeagainst before |
| Calls per day | 670/day | 357/day1 of 7 days so far−46.8%vs beforeagainst before |
| Active contracts (busiest day) | 1 | 11 of 7 days so far |
| Distinct caller addresses (busiest day) | 96 | 521 of 7 days so far−45.8%vs beforeagainst before |
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
Merrymen’s code names the token of 1 published project.
Named in code or runs on a hook, read from public code and the chain: a link, never a partnership or an on-chain interaction. A code link is a reference: the code names the token, which shows neither a dependency nor use; only a hook link is a pool running on the other’s hook. As data
