Skip to content
HEY Research Lab
Menu

altiico

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 →

Static catalog + discovery pipeline for VRM-bearing avatar NFT collections across EVM/Solana/Tezos; emits avatar-manifest-v1.json for Hubzz

What HEY knows

Development

Shipped this weekShipping: 1 counted ship in 30 days; latest ship today. Evidence Source

Build Momentum 25How it is measured

Latest: Code changes this week (since Mon 9 Nov) · 3 commits

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

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

No account? Email me altiico’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
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.
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-14. Not called Resumed: HEY began reading the source of the newest ships after the quiet stretch before them began, so it did not watch that gap.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 9 Nov) · 3 commitsCode changes, week of 2026-08-17 – 2026-08-23 · 2 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".
Research coverage: HEY can answer 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 1m 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 17d ago.

Code and packages

  • Repository detailsMeasuredRead 3d ago.
  • Published packagesMeasuredRead 3d 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
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes this week (since Mon 9 Nov) · 3 commits

Code activitySource-backed

Why it matters: First week of code changes after 88 quiet days.

What changed, in the repository’s own words:

1 active day in russfranky/altiico.

This week HEY looked inside 3 commits to see what changed: 1 changed code, 2 documentation or maintenance only. 2 automated commits (bot accounts or a repeating scripted message) not counted.

Record ship:6168ef82… · 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 3 commits 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-14; HEY first knew on 2026-11-14.
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: 5 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, week of 2026-08-17 – 2026-08-23 · 2 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in russfranky/altiico.

    How HEY read this week

    This week HEY looked inside 2 commits to see what changed: 1 changed code, 1 documentation or maintenance only. 4 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-08-17 – 2026-08-23 · 2 commits (opens in a new tab)

Other changes on HEY’s record

5 changes on HEY’s record for altiico: 1 new Verified Builder or owner proof · 1 new project on HEY · 1 build pace change · 2 weeks of code pushed.

All 5 changes for altiico →

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

2 places HEY reads for altiico