Merrymen

Latest ship

Builder activity

Build timeline

1. Active development: 99 commits across 2 contributors

   1d ago

   Code Activity · Source linked

   4 active day(s) in millw14/merrymen.

   View evidence

2. Active development: 99 commits across 2 contributors

   2d ago

   Code Activity · Source linked

   4 active day(s) in millw14/merrymen.

   View evidence

3. Active development: 99 commits across 3 contributors

   3d ago

   Code Activity · Source linked

   4 active day(s) in millw14/merrymen.

   View evidence

4. Active development: 94 commits across 3 contributors

   4d ago

   Code Activity · Source linked

   4 active day(s) in millw14/merrymen.

   View evidence

5. Active development: 84 commits across 1 contributor

   5d ago

   Code Activity · Source linked

   5 active day(s) in millw14/merrymen.

   View evidence

6. Active development: 81 commits across 1 contributor

   5d ago

   Code Activity · Source linked

   4 active day(s) in millw14/merrymen.

   View evidence

7. Active development: 83 commits across 1 contributor

   8d ago

   Code Activity · Source linked

   4 active day(s) in millw14/merrymen.

   View evidence

8. Android demo 0.1.2

   1mo ago

   Github Release · Source 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.DETECTSCREENCAPTURE. 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 the

   View evidence

9. Android demo 0.1.1

   1mo ago

   Github Release · Source 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.DETECTSCREENCAPTURE being blocked > in app.json while expo-screen-capture was installed. That library > registers a screen-cap

   View evidence

10. Android demo 0.1.0

    1mo ago

    Github Release · Source 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 > (DETECTSCREENCAPTURE 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 t

    View evidence

11. Desktop 0.1.7

    1mo ago

    Github Release · Source 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 first

    View evidence

12. Desktop 0.1.6

    1mo ago

    Github Release · Source verified

    Windows desktop app — bundles merrymen 0.17.0. Includes fixes from three community contributors: - The vault sweep now sizes itself to your actual daily cap. Previously steady-basket could propose a deposit larger than the permission wall would ever accept, and re-propose the identical rejected deposit every tick, forever, while the cash never reached the vault. Found by @zeeonchain. - The Telegram /link code is minted as soon as merrymen starts, instead of only once Telegram is switched on — so a valid bot token no longer shows an empty code. Found by @Victory-byte. - Fixed a backtest b

    View evidence

13. Desktop 0.1.5

    1mo ago

    Github Release · Source 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.

    View evidence

Research notes

Written by Dawnscan researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

No published notes on Merrymen yet.

Know something about Merrymen? Sign in with wallet to submit a research note. Notes are reviewed before they appear here.

Sources

• https://merrymen.dev/Unverified
• https://merrymen.dev/docsOfficial
• https://merrymen.dev/docs#telegramOfficial
• https://github.com/millw14/merrymenOfficial
• https://github.com/millw14Official