Traditional health insurance keeps plans, reserves, and decisions inside closed systems. Nakama is building the onchain health insurance layer: organizations launch tailored, funded plans; members claim privately; AI lowers operating costs; reserves and payouts are verifiable; and approved excess capital can earn yield. $NAKAMA coordinates the people, agents, and capital growing these plans into an open global insurance network.
Read moreBuild Momentum 0How it is measured
Why it matters: The first week of code changes HEY has recorded for this project.
Follow puts Nakama Health by Virtuals 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 16 of the 19 research questions that apply · Research coverage
Checked
Code activitySource linked
What changed, in the repository’s own words:
6 active days in nakama-health/nakama-protocol.
This week HEY looked inside 1 of 12 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.
Record ship:43c12fcb… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.
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 Nakama Health by Virtuals? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.
15 changes on HEY’s record for Nakama Health by Virtuals: 1 verification change · 1 contract in use again or for the first time · 12 market moves · 1 week of code pushed.
Liquidity $49K → $21K in a week
Token market moved from Active market to Trading inactive
Research standing moved from Published to Verified builder
Token market moved from Active market to Trading inactive
Liquidity $52K → $25K in a week
All 15 changes for Nakama Health by Virtuals →
The full change record holds 2 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)
HEY can answer 16 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, over 7 days: calls 220/day (before: 0/day) · active contracts 1 (before: 0).
Code changes, week of 2026-07-27 – 2026-08-02 · at least 12 commitsCode activityin the week of 27 Jul (week precision)
| Measure | Observed before20–26 Jul | Observed after3–9 Aug |
|---|---|---|
| Calls per day | 0/day3 of 7 days | 220/day |
| Active contracts (busiest day) | 03 of 7 days | 1 |
| Distinct caller addresses (busiest day) | 03 of 7 days | Not measured: no day has a count |
Not shown: Price and valuation: the market is not live · Volume per day: HEY began reading this market’s price, liquidity and volume on 2026-07-29, during this ship’s week · Liquidity: HEY began reading this market’s price, liquidity and volume on 2026-09-03, after this ship
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
