Skip to content

Hey Research Lab

$HEY

Infrastructure

Contract 0xb33eb16782776b4d738c0fd643577cb0284db610

HEY holds 123 other Robinhood Chain tokens that use $HEY. This page is only the contract above. See them

HEY’s own token — researched by the same rules

This is HEY’s own page, measured by the same rules as every other. What you see comes from the public repository; the private one, where most of the work happens, is not read.

Still Building

Coordination token for HEY Research Lab, the builder-discovery layer for Robinhood Chain.

What HEY knows

Building
Shipping consistentlyShipping: 14 meaningful events in 30 days; latest ship yesterday. Evidence Source

Build Momentum 85How it is measured

Latest ship
Code changes this week (since Mon 19 Oct) · 17 commits · · Code activity

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

This change
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-10-24; HEY first knew on 2026-10-19.
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.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts Hey Research Lab 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 Hey Research Lab’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.

Attention
Building and market attention rank about level among comparable projects: 99.8 of 100 for building, 82.9 of 100 for market attention (a gap of 17). What the Discovery Gap is

It compares building with market attention; it is not a prediction and not a reason to trade.

Product usage
Fact2 of 2 watched contracts active · 1 call to the contracts' own functions in 7 days; the other 2,889 of 2,890 calls were ERC-20 token transfers and approvals, which trading alone produces.

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

Contracts
Fact2 contracts on record for code changes, 2 with verified source; latest change 2 days ago: Deployed a new contract: ShipEscrow. Source
Not yet known
Unknown2 gaps: Published packages (not enough yet), API description (not enough yet). Packages name its repository, but none is confirmed as the project’s own.

HEY can answer 17 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
Shipping.
“Shipping” by the activity rule: 14 meaningful events in the last 30 days, the newest 2026-10-24.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 19 Oct) · 17 commitsDeployed a new contract: ShipEscrowCode changes, week of 2026-10-12 – 2026-10-18 · 35 commits+2 moreWhat 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 verified building evidence from the project's own sources.
Source59 registered sources, 15 of them context only.ReadRecordsCode changes this week (since Mon 19 Oct) · 17 commitsDeployed a new contract: ShipEscrowCode changes, week of 2026-10-12 – 2026-10-18 · 35 commits+7 moreWhat 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 owner signed for it on-chain.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Active market.
Active market: the pool holds liquidity and the token 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 “Active market”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
6.18% of supply locked.
Held at HoodLock, read from the locker contract; the next 3.64% unlocks on 22 Mar 2027, and the last on 9 Sep 2027. It says what cannot move today. It is not a safety check, not a score, and never an input to activity status.
Market figures are context only and never change activity status. Methodology

Latest ship

Checked

Code changes this week (since Mon 19 Oct) · 17 commits hey-research-lab/hey-research-open

Code activitySource linked

6 active days in hey-research-lab/hey-research-open.

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

Record ship:bffd7034… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

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.

Questions HEY can answer about Hey Research Lab — as of 25 Oct

Is Hey Research Lab still being built?
DerivedShipping: 14 meaningful events in 30 days; latest ship yesterday. Evidence
What did Hey Research Lab ship last?
FactCode changes this week (since Mon 19 Oct) · 17 commits — Code activity, yesterday. Evidence
Is 0xB33eb16782776b4D738c0Fd643577cb0284Db610 Hey Research Lab’s own contract?
FactToken verified: The owner proved control of the contract with an on-chain signature. Details
What does HEY not know about Hey Research Lab?
Unknown2 gaps: Published packages (not enough yet), API description (not enough yet). Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

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

  1. Deployed a new contract: ShipEscrow

    New contractSource verified

    The account that launched Hey Research Lab’s token deployed ShipEscrow at 0x3da1…25f2 on 2026-10-23. Read from the chain; the creating transaction is the evidence.

  2. Code changes this week (since Mon 19 Oct) · 1 commit hey-research-lab/hey-data

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in hey-research-lab/hey-data.

    How HEY read this week

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

  3. Code changes this week (since Mon 19 Oct) · 1 commit hey-research-lab/hey-check

    Code activitySource linked

    1 active day in hey-research-lab/hey-check.

    How HEY read this week

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

  4. Code changes, week of 2026-10-12 – 2026-10-18 · 35 commits hey-research-lab/hey-research-open

    Code activitySource linked

    7 active days in hey-research-lab/hey-research-open.

    How HEY read this week

    This week HEY looked inside 3 of 35 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

  5. Code changes, week of 2026-10-12 – 2026-10-18 · 10 commits hey-research-lab/hey-check

    Code activitySource linked

    1 active day in hey-research-lab/hey-check.

    How HEY read this week

    This week HEY looked inside 3 of 10 commits to see what changed: 1 changed code, 2 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

  6. 3 code weeks of maintenance or automation only — not counted as building

    Show the 3 weeks
    1. Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit hey-research-lab/hey-agent-contract

      Code activitySource linked

      1 active day in hey-research-lab/hey-agent-contract.

      Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

    2. Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit hey-research-lab/hey-cli

      Code activitySource linked

      1 active day in hey-research-lab/hey-cli.

      Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

    3. Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit hey-research-lab/hey-data

      Code activitySource linked

      1 active day in hey-research-lab/hey-data.

      Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

  7. Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit hey-research-lab/hey-agent-skills

    Code activitySource linked

    1 active day in hey-research-lab/hey-agent-skills.

    How HEY read this week

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

  8. Code changes, week of 2026-10-12 – 2026-10-18 · 4 commits hey-research-lab/hey-virtuals-plugin

    Code activitySource linked

    1 active day in hey-research-lab/hey-virtuals-plugin.

    How HEY read this week

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

Earlier ships (14)
  1. Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit hey-research-lab/hey-goat-plugin

    Code activitySource linked

    1 active day in hey-research-lab/hey-goat-plugin.

    How HEY read this week

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

  2. Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit hey-research-lab/plugin-hey-research

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in hey-research-lab/plugin-hey-research.

    How HEY read this week

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

  3. Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit hey-research-lab/hey-agentkit

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in hey-research-lab/hey-agentkit.

    How HEY read this week

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

  4. Code changes, week of 2026-10-05 – 2026-10-11 · 28 commits hey-research-lab/hey-research-open

    Code activitySource linked

    7 active days in hey-research-lab/hey-research-open.

    How HEY read this week

    This week HEY looked inside 3 of 28 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

  5. Code changes, week of 2026-10-05 – 2026-10-11 · 3 commits hey-research-lab/rhchain-registry

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in hey-research-lab/rhchain-registry.

    How HEY read this week

    This week HEY looked inside 3 commits to see what changed: 1 changed code, 2 documentation or maintenance only.

  6. Code changes, week of 2026-10-05 – 2026-10-11 · 4 commits hey-research-lab/hey-telegram-bot

    Code activitySource linked

    1 active day in hey-research-lab/hey-telegram-bot.

    How HEY read this week

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

  7. Code changes, week of 2026-10-05 – 2026-10-11 · 3 commits hey-research-lab/hey-ship-action

    Code activitySource linked

    1 active day in hey-research-lab/hey-ship-action.

    How HEY read this week

    This week HEY looked inside 2 of 3 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

  8. Code changes, week of 2026-10-05 – 2026-10-11 · 3 commits hey-research-lab/hey-research-receipts

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in hey-research-lab/hey-research-receipts.

    How HEY read this week

    This week HEY looked inside 3 commits to see what changed: 1 changed code, 2 documentation or maintenance only.

  9. Code changes, week of 2026-10-05 – 2026-10-11 · 2 commits hey-research-lab/hey-project-manifest

    Code activitySource linked

    1 active day in hey-research-lab/hey-project-manifest.

    How HEY read this week

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

  10. Code changes, week of 2026-10-05 – 2026-10-11 · 4 commits hey-research-lab/hey-embed

    Code activitySource linked

    1 active day in hey-research-lab/hey-embed.

    How HEY read this week

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

  11. Code changes, week of 2026-10-05 – 2026-10-11 · 3 commits hey-research-lab/hey-data

    Code activitySource linked

    1 active day in hey-research-lab/hey-data.

    How HEY read this week

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

  12. Code changes, week of 2026-10-05 – 2026-10-11 · 4 commits hey-research-lab/hey-cli

    Code activitySource linked

    1 active day in hey-research-lab/hey-cli.

    How HEY read this week

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

  13. Code changes, week of 2026-10-05 – 2026-10-11 · 2 commits hey-research-lab/hey-agent-contract

    Code activitySource linked

    1 active day in hey-research-lab/hey-agent-contract.

    How HEY read this week

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

  14. Code changes, week of 2026-10-05 – 2026-10-11 · 3 commits hey-research-lab/chainprint

    Code activitySource linked

    1 active day in hey-research-lab/chainprint.

    How HEY read this week

    This week HEY looked inside 2 of 3 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

Build through the drawdown

Down 77.9% from the HEY-tracked high, with 15 verified updates since.

Code changes, week of 2026-10-19 – 2026-10-25 — 2h agoDeployed a new contract: ShipEscrow — 2d agoCode changes, week of 2026-10-19 – 2026-10-25 — 5d agoCode changes, week of 2026-10-19 – 2026-10-25 — 5d agoCode changes, week of 2026-10-12 – 2026-10-18 — 7d agoCode changes, week of 2026-10-12 – 2026-10-18 — 8d agoCode changes, week of 2026-10-12 – 2026-10-18 — 8d agoCode changes, week of 2026-10-12 – 2026-10-18 — 8d agoCode changes, week of 2026-10-12 – 2026-10-18 — 12d agoCode changes, week of 2026-10-12 – 2026-10-18 — 13d agoCode changes, week of 2026-10-12 – 2026-10-18 — 13d agoCode changes, week of 2026-10-12 – 2026-10-18 — 13d agoCode changes, week of 2026-10-12 – 2026-10-18 — 13d agoCode changes, week of 2026-10-12 – 2026-10-18 — 13d agoCode changes, week of 2026-10-05 – 2026-10-11 — 14d agoCode changes, week of 2026-10-05 – 2026-10-11 — 16d agoCode changes, week of 2026-10-05 – 2026-10-11 — 16d agoCode changes, week of 2026-10-05 – 2026-10-11 — 16d agoCode changes, week of 2026-10-05 – 2026-10-11 — 16d agoCode changes, week of 2026-10-05 – 2026-10-11 — 16d agoCode changes, week of 2026-10-05 – 2026-10-11 — 16d agoCode changes, week of 2026-10-05 – 2026-10-11 — 16d agoCode changes, week of 2026-10-05 – 2026-10-11 — 16d agoCode changes, week of 2026-10-05 – 2026-10-11 — 16d agoCode changes, week of 2026-10-05 – 2026-10-11 — 16d ago$421K
Fully diluted valuation over time. Each marker is a meaningful ship.

A factual observation about past activity and market context. It is not a prediction, and not investment advice.

What changed

70 changes on HEY’s record for Hey Research Lab: 10 releases · 1 verification change · 1 market check · 11 official source changes · 47 other changes in 4 more kinds.

All 70 changes for Hey Research Lab →

The full change record holds 45 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 17 of the 19 research questions that apply.

17 of 19 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 3m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 16d ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 13h ago.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesMeasuredRead 8d ago.

Code and packages

  • Repository detailsMeasuredRead 23h ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Contracts

  • Contract creationMeasuredRead 16h ago.
  • Contract activityMeasuredRead yesterday.
  • Verified sourceMeasuredRead 3d ago.
  • Contract interfaceMeasuredRead 3d ago.

Market

  • Current marketMeasuredRead 22m ago.
  • Market historyMeasuredRead yesterday.
  • Supply distributionMeasuredRead yesterday.
  • LocksMeasuredRead 29m 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

29 more sources (docs)

Security context: bug bounty page on the project’s site. An audit shows an audit took place; it is not a guarantee of safety.

Contract
0xb33e…b6100xb33eb16782776b4d738c0fd643577cb0284db610