Skip to content

Hey Research Lab

$HEY

Infrastructure

Contract 0xb33eb16782776b4d738c0fd643577cb0284db610

HEY holds 130 other Robinhood Chain tokens with the ticker $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.

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

What HEY knows

Development

Shipping consistentlyShipping: 6 counted ships in 30 days; latest ship yesterday. Evidence Source

Build Momentum 74How it is measured

Latest: Code changes this week (since Mon 2 Nov) · 17 commits

Token market · context

Active market$314K fully diluted valuation

Token check

Project names this contract
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

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.

Sign in to follow Hey Research Lab

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 ranks ahead, and the market already notices it, among comparable projects: its building is ahead of 99.3% of them, its market attention ahead of 90.6% (a gap of 8.7). What the Discovery Gap is

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

More detail
Product usage
Fact2 of 2 watched contracts active · 1 call to the contracts' own functions in 7 days; the other 13,364 of 13,365 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 published source code; no implementation or interface change recorded.
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.
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: 6 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.ReadRecordsCode changes this week (since Mon 2 Nov) · 17 commitsCode changes, week of 2026-10-26 – 2026-11-01 · 50 commitsship:bffd7034-1889-4b9f-8e0c-03b04031715f+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 counted building from the project's own sources.
Source63 registered sources, 16 of them context only.ReadRecordsCode changes this week (since Mon 2 Nov) · 17 commitsCode changes, week of 2026-10-26 – 2026-11-01 · 50 commitsship:bffd7034-1889-4b9f-8e0c-03b04031715f+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.
Project names this contract.
Project names this contract: 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 derivedProject names this contract: 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.
Research coverage: HEY can answer 17 of the 19 research questions that apply.
17 of 19 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 60d ago.

Building

  • Building activityMeasuredRead just now.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 30d ago.
  • TimelineMeasured

Official site

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

Code and packages

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

Contracts

  • Contract creationMeasuredRead 21h ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 3d ago.
  • Contract interfaceMeasuredRead 3d ago.

Market

  • Current marketMeasuredRead 1m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead today.
  • LocksMeasuredRead 3h 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.

Market figures are context only and never change activity status. Methodology

Latest ship

Checked

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

Code activitySource-backed

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:5627c6ce… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

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-07; HEY first knew on 2026-11-02.
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.

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: 3 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) · 13 commits hey-research-lab/security

    Code activitySource-backed

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

    How HEY read this week

    This week HEY looked inside 2 of 13 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.

  2. Code changes this week (since Mon 2 Nov) · 19 commits hey-research-lab/hey-research-lab

    Code activitySource-backed

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

    How HEY read this week

    This week HEY looked inside 1 of 11 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 8 automated commits (bot accounts or a repeating scripted message) not counted.

  3. Code changes this week (since Mon 2 Nov) · 4 commits hey-research-lab/hey-data

    Code activitySource-backed

    3 active days in hey-research-lab/hey-data.

    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.

  4. Code changes this week (since Mon 2 Nov) · 4 commits hey-research-lab/proof-of-ship-near

    Code activitySource-backed

    1 active day in hey-research-lab/proof-of-ship-near.

    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.

  5. Code changes this week (since Mon 2 Nov) · 2 commits hey-research-lab/hey-ship-action

    Code activitySource-backed

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

    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.

  6. Code changes this week (since Mon 2 Nov) · 1 commit hey-research-lab/hey-agent-skills

    Code activitySource-backed

    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.

  7. Code changes this week (since Mon 2 Nov) · 1 commit hey-research-lab/hey-agent-contract

    Code activitySource-backed

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

    How HEY read this week

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

  8. Code changes this week (since Mon 2 Nov) · 2 commits hey-research-lab/hey-telegram-bot

    Code activitySource-backed

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

    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.

Earlier ships (16)
  1. Code changes this week (since Mon 2 Nov) · 1 commit hey-research-lab/hey-virtuals-plugin

    Code activitySource-backed

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

    How HEY read this week

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

  2. Code changes this week (since Mon 2 Nov) · 1 commit hey-research-lab/hey-embed

    Code activitySource-backed

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

    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 2 Nov) · 2 commits hey-research-lab/plugin-hey-research

    Code activitySource-backed

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

    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. Code changes this week (since Mon 2 Nov) · 1 commit hey-research-lab/hey-goat-plugin

    Code activitySource-backed

    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.

  5. Code changes this week (since Mon 2 Nov) · 2 commits hey-research-lab/hey-agentkit

    Code activitySource-backed

    2 active days in hey-research-lab/hey-agentkit.

    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.

  6. Code changes this week (since Mon 2 Nov) · 2 commits hey-research-lab/hey-check

    Code activitySource-backed

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

    How HEY read this week

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

  7. Code changes this week (since Mon 2 Nov) · 1 commit hey-research-lab/hey-cli

    Code activitySource-backed

    What changed, in the repository’s own words:

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

    How HEY read this week

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

  8. Code changes this week (since Mon 2 Nov) · 3 commits hey-research-lab/hey-research-receipts

    Code activitySource-backed

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

    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.

  9. Code changes this week (since Mon 2 Nov) · 3 commits hey-research-lab/hey-project-manifest

    Code activitySource-backed

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

    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.

  10. Code changes this week (since Mon 2 Nov) · 3 commits hey-research-lab/chainprint

    Code activitySource-backed

    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.

  11. Code changes this week (since Mon 2 Nov) · 3 commits hey-research-lab/rhchain-registry

    Code activitySource-backed

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

    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.

  12. Code changes, week of 2026-10-26 – 2026-11-01 · 50 commits hey-research-lab/hey-research-open

    Code activitySource-backed

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

    How HEY read this week

    This week HEY looked inside 3 of 50 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.

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

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in hey-research-lab/hey-agent-contract.

    How HEY read this week

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

  14. Code changes, week of 2026-10-26 – 2026-11-01 · 2 commits hey-research-lab/hey-telegram-bot

    Code activitySource-backed

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

    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.

  15. Code changes, week of 2026-10-26 – 2026-11-01 · 10 commits hey-research-lab/hey-research-lab

    Code activitySource-backed

    3 active days in hey-research-lab/hey-research-lab.

    How HEY read this week

    This week HEY looked inside 2 of 10 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. 9 automated commits (bot accounts or a repeating scripted message) not counted.

  16. Code changes, week of 2026-10-26 – 2026-11-01 · 1 commit hey-research-lab/rhchain-registry

    Code activitySource-backed

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

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

Other changes on HEY’s record

110 changes on HEY’s record for Hey Research Lab: 10 releases · 1 new Verified Builder or owner proof · 15 official source changes · 1 contract change · 83 other changes in 3 more kinds.

All 110 changes for Hey Research Lab →

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

The token’s market, checks, locks and stamps below are context only: none of it changes activity status or Build Momentum.

Contract 0xB33eb16782776b4D738c0Fd643577cb0284Db610 on Robinhood Chain

0xb33e…b6100xb33eb16782776b4d738c0fd643577cb0284db610

Project names this contract: The owner proved control of the contract with an on-chain signature.

Market context

Active market · FDV (fully diluted) $314K · current liquidity $50K · reading under an hour old (DEX Screener).

Token

Launch stage
Trading in a DEX pool
Pair age
60d ago

Market

24h volume
$27K
Trades 24h
92 buys · 113 sells
Price 24h
down 28.1 percent over 24 hours· 6hdown 9.3 percent over 6 hours· 1hup 0.7 percent over 1 hour

The tracked token has liquidity and traded in the last 24 hours.

Market history, trading and checks →

Market integrity

Liquidity is 14% below the level it held two days running ($59.7K, 2026-11-06).

Market
Active market
Last day with trading
2026-11-07

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-11-08 06:57 UTC · How HEY checks this

Locks

Token supply locked
6.18%
Next unlock
2027-03-22 · 3.64% of supply
Last unlock
2027-09-09
Pair locked
Not applicable

Locked by HoodLock, read from the locker contract HEY watches. No locked pair holds this token; most pools on this chain have no pair token to lock. Locked supply says what cannot move today, not that the price will do anything.

Sources

63 places HEY reads for Hey Research Lab
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.