Skip to content
HEY Research Lab
Menu

louvr

Integration record: HEY holds no Robinhood Chain evidence for this project (no token, contract or registry listing on the chain), so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim it →

What HEY knows

Development

Dormant: no ship for 106 daysDormant: 0 counted ships in 30 days; latest ship on 2026-07-15. Evidence Source

Build Momentum 0How it is measured

Latest: Code changes, week of 2026-07-13 – 2026-07-19 · at least 14 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts louvr 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 louvr

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

View latest ship
Share
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
Dormant.
“Dormant” by the activity rule: 0 counted ships in the last 30 days, the newest 2026-07-15.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-07-13 – 2026-07-19 · at least 14 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".
Research coverage: HEY can answer 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 56d ago.

Building

  • Building activityMeasuredRead 17h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • 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 3d ago.
  • Published packagesMeasuredRead 3d ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, 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

Code changes, week of 2026-07-13 – 2026-07-19 · at least 14 commits

Code activitySource-backed

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

What changed, in the repository’s own words:

1 active day in 0xfps/louvr.

This week HEY looked inside 1 of 14 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

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

Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
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 a release or a deployment: code is not 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 to the week of 2026-07-15; HEY first knew on 2026-09-15. HEY indexed it later, as history.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

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)

Builder activity

No meaningful, source-backed updates in the 9 weeks since HEY began reading this project’s sources; earlier weeks are not yet read.

What changed

2 changes on HEY’s record for louvr: 1 build pace change · 1 week of code pushed.

All 2 changes for louvr →

Questions HEY can answer about louvr — as of 29 Oct

Show the answers
Is louvr still being built?
DerivedDormant: 0 counted ships in 30 days; latest ship on 2026-07-15. Evidence
What did louvr ship last?
FactCode changes, week of 2026-07-13 – 2026-07-19 · at least 14 commits — Code activity, on 2026-07-15. Evidence
What does HEY not know about louvr?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

Sources

1 place HEY reads for louvr