Skip to content
HEY Research Lab
Menu

Flat War

Is this your project? Claim it →

FLAT WAR — a persistent multiplayer war game on Robinhood Chain: claim cities, build armies, burn $WIF to conquer the flat world.

What HEY knows

Development

Shipped this weekShipping: 2 counted ships in 30 days; latest ship yesterday. Evidence Source

Build Momentum 36How it is measured

Latest: FLAT WAR — demo build

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Flat War on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow Flat War

No account? Email me Flat War’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.

More detail
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 2 counted ships in the last 30 days, the newest 2026-11-07.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsFLAT WAR — demo buildCode changes this week (since Mon 2 Nov) · 1 commitWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.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 counted building from the project's own sources.
Source1 registered source, 0 of them context only.ReadRecordsFLAT WAR — demo buildCode changes this week (since Mon 2 Nov) · 1 commitsource:52787570-ddda-49ec-8140-2eaaf52c41a1What 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.
Research coverage: HEY can answer 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 11h ago.

Building

  • Building activityMeasuredRead 2m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 22h ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 10h ago.
  • Published packagesMeasuredRead 10h ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, 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.

Market figures are context only and never change activity status. Methodology
LinksGitHub (opens in a new tab)Sources

Latest ship

Checked

FLAT WAR — demo build

GitHub releaseSource-backed

Why it matters: The first release HEY has recorded for this project.

Demo video of the World is Flat hackathon submission: multiplayer war on Robinhood Chain with real $WIF burns.

Record ship:07d4972b… · HEY counts it as building; it does not judge the release’s quality.

Release, read from the team’s GitHub · no deployment linked
What it names
The team’s release names it: “FLAT WAR — demo build” (v1.0).
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it 2026-11-07 13:28 UTC; HEY first knew on 2026-11-08.
Not known
  • HEY does not hold the commit the release was cut from.
  • HEY has not observed a deployment of this change.
  • Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to a deployment.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

View evidence ↗ (opens in a new tab)Post this ship on X

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: 11 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes this week (since Mon 2 Nov) · 1 commit

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in ryasinfar/flat-war.

    How HEY read this week

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

    View evidence: Code changes this week (since Mon 2 Nov) · 1 commit (opens in a new tab)

Other changes on HEY’s record

4 changes on HEY’s record for Flat War: 1 release · 1 new Verified Builder or owner proof · 1 new project on HEY · 1 week of code pushed.

All 4 changes for Flat War →

Sources

1 place HEY reads for Flat War