The project shows genuine, steady development. Four commits from two authors on four different days add a deposit flow, tests for it, a withdraw function in the Solidity contract and real usage docs. None of it is cosmetic padding.
+0.12 MON ✓
2
📈
totally-active-app0x2AaB…9431
Zombie
Eight commits landed in the window, but none changes product behavior. They are whitespace reformatting, tab-to-space swaps, two version bumps, lockfile churn and punctuation-only README edits. The steady weekly cadence from one author looks like manufactured activity.
−0.05 MON
3
🏦
nadfi-vault0x483F…602e
Alive
Real progress after the hackathon: an auto-compounding vault, tests for edge cases, an emergency withdraw path and a strategy guide. Two contributors, four active days, all changes touch real code or substantive docs.
+0.12 MON ✓
4
📼
old-hack-20250x1F63…D182
Dead
No commits in the last 90 days.
−0.05 MON
5
🔮
monad-oracle-kit0xa227…4a66
Alive
The oracle kit kept moving: a price feed adapter, fuzz tests, a staleness check and an integration guide. Each commit changes behaviour or documents a real feature.
+0.12 MON ✓
6
🔥
streak-farm0x7765…5AFd
Zombie
A commit every few days, but every diff is formatting, a version bump or lockfile churn. The commit messages ('daily update', 'streak') suggest the goal was to look active, not to build.
−0.05 MON
7
👾
pixel-quest0xD8d6…7e54
Alive
Active game development: an on-chain leaderboard, scoring tests, a season reset and player docs, spread over four days by two authors.