Skip to content

Nakama Health by Virtuals

$NAKAMA

AI Agents

Is this your project? Claim and verify →

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 more

What HEY knows

Building
Dormant: no ship for 77 daysDerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-08-01. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-07-27 – 2026-08-02 · at least 12 commits · · Code activity

Why it matters: The first week of code changes HEY has recorded for this project.

Latest change
DerivedMarket event yesterday: Liquidity $49K → $21K in a week. Context, not building. Evidence

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.

No account? Email me Nakama Health by Virtuals’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Product usage
Fact1 of 1 watched contract active · 18 calls in 7 days — all token transfers and approvals (ERC-20), which trading alone produces; none reached another function HEY watches.

Counted from the chain. Usage says the contracts are used, not that anyone is building.

Contracts
Fact1 contract on record for code changes, 1 with verified source; no implementation or interface change recorded.
Token market · context
Trading inactive$217K fully diluted valuationToken verified
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Contract activity (not enough yet). HEY read its website and found no link to docs.

HEY can answer 16 of the 19 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Dormant.
“Dormant” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-08-01.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-07-27 – 2026-08-02 · at least 12 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Dormant”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source4 registered sources, 0 of them context only.ReadWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Token verified.
Token verified: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedToken verified: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Trading inactive.
Trading inactive: the pool holds liquidity, but nothing traded in the last day.
Source8 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Trading inactive”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Market figures are context only and never change activity status. Methodology

Latest ship

Checked

Code changes, week of 2026-07-27 – 2026-08-02 · at least 12 commits

Code activitySource linked

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.

Shared change · Verified builder

Nakama Health by Virtuals is now a verified builder: HEY verified its builder sources.

Builder status: Dormant.

Observed by HEY on 2026-10-11Source: hey state

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about Nakama Health by Virtuals — as of 2026-10-17

Is Nakama Health by Virtuals still being built?
DerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-08-01. Evidence
What did Nakama Health by Virtuals ship last?
FactCode changes, week of 2026-07-27 – 2026-08-02 · at least 12 commits — Code activity, on 2026-08-01. Evidence
Is 0x2e098dC880E3c63B057E6ee83dC9Ef6945F7E370 Nakama Health by Virtuals’s own contract?
FactToken verified: The project’s own site names this contract. Details
What does HEY not know about Nakama Health by Virtuals?
Unknown3 gaps: Official docs (no source), API description (no source), Contract activity (not enough yet). HEY read its website and found no link to docs. Details

Research notes

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.

What changed

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.

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)

Research coverage

HEY can answer 16 of the 19 research questions that apply.

16 of 19 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 36m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 9h ago.

Code and packages

  • Repository detailsMeasuredRead 5d ago.
  • Published packagesMeasuredRead 5d ago.

Contracts

  • Contract creationMeasuredRead 6d ago.
  • Contract activityNot enough yetCalls were read, but the days’ events could not be decoded.
  • Verified sourceMeasuredRead 12h ago.
  • Contract interfaceMeasuredRead 12h ago.

Market

  • Current marketMeasuredRead 27m ago.
  • Market historyMeasuredRead yesterday.
  • Supply distributionMeasuredRead 4d ago.
  • LocksMeasuredRead 2h ago.
  • Market checksMeasured

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.

Sources

Contract
0x2e09…e3700x2e098dc880e3c63b057e6ee83dc9ef6945f7e370