Skip to content
HEY Research Lab
Menu

Ultravein App

Is this your project? Claim it →

Mine with your agent on Robinhood Chain.

What HEY knows

Development

Last shipped yesterdayShipping: 1 counted ship in 30 days; latest ship yesterday. Evidence Source

Build Momentum 23How it is measured

Latest: Code changes, week of 2026-11-02 – 2026-11-08 · 7 commits

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Ultravein App 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 Ultravein App

No account? Email me Ultravein App’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
Unknown6 gaps: Repositories (source unavailable), Releases (no source), Published packages (no source), Official docs (no source), API description (no source), Official site changes (no source). Every repository HEY holds has stopped answering.
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: 1 counted ship in the last 30 days, the newest 2026-11-08.
SourceHEY holds no repository, changelog or feed it can read for this project; the status rests on building events it counted from the chain or from corroborated sources.ReadRecordsCode changes, week of 2026-11-02 – 2026-11-08 · 7 commitsWhat 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.ReadRecordsCode changes, week of 2026-11-02 – 2026-11-08 · 7 commitssource:b2c79cf0-27b0-4faf-a3ed-df571763db1fWhat 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 3 of the 9 research questions that apply.
3 of 9 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 11h ago.

Building

  • Building activityMeasured
  • RepositoriesSource unavailableEvery repository HEY holds has stopped answering.
  • ReleasesNo sourceNo source HEY reads releases from.
  • 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

  • Published packagesNo sourceNo repository the project claims as its own.

Not applicable here: Repository details, 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

Code changes, week of 2026-11-02 – 2026-11-08 · 7 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 ultravein/ultravein-app.

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

Record ship:01067426… · 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-11-08; HEY first knew on 2026-11-09.
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

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.

What changed

3 changes on HEY’s record for Ultravein App: 1 new Verified Builder or owner proof · 1 new project on HEY · 1 week of code pushed.

All 3 changes for Ultravein App →

The full change record holds 1 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Sources

1 place HEY reads for Ultravein App