Skip to content
HEY Research Lab
Menu

RuneHood

$RUNE

Contract 0x437d083c57bb31573aa383f9602ec5a86519b9d4

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

Is this your project? Claim it →

Every token launched here is a real Bitcoin Rune: etched on Bitcoin, fixed 1B supply, backed 1:1. Robinhood Pad

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 26 Oct) · 3 commits

Token market · context

Active market$4K fully diluted valuation

Same ticker, different contract: 2 other published projects use the ticker $RUNE. This page: its site runehood.fun names 0x437d…b9d4. RuneCurve: its site runecurve.tech names 0x469d…d8ab; SetRune: its site setrune.dev names 0x94f4…0854. HEY does not say which is the real one — only what each project’s own sources name.

Token check

Project names this contract
FollowCreate alertTerminal preview
Get updates

Get updates

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

No account? Email me RuneHood’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
Attention
Building ranks ahead of market attention among comparable projects: its building is ahead of 94.1% of them, its market attention ahead of 50% (a gap of 44.1). What the Discovery Gap is

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

Product usage
UnknownThe project has a contract, but HEY does not count its calls yet: a token joins the watch once it takes calls in a thirty-day window, and any contract the project’s own sources name is watched. Unknown, not zero.
Contracts
Fact1 contract on record for code changes, 1 with verified source; no implementation or interface change recorded.
Not yet known
Unknown4 gaps: Official docs (not tied to the project yet), API description (not enough yet), Official site changes (not enough yet), Supply distribution (not enough yet). HEY found a docs link on its website and holds it until the website is tied to the project.
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-10-29.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 26 Oct) · 3 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 verified building evidence from the project's own sources.
Source5 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 26 Oct) · 3 commitssource:8f65d041-0030-4bdf-83ae-3f5ae5994d27source:c3e63e43-1219-4de5-8c15-a77ee217c28e+2 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 project’s own site names it.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.
Source6 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 13 of the 17 research questions that apply.
13 of 17 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 10h ago.

Building

  • Building activityMeasuredRead 35m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNot tied to the project yetHEY found a docs link on its website and holds it until the website is tied to the project.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Contracts

  • Contract creationMeasuredRead 9h ago.
  • Contract activityMeasuredRead yesterday.
  • Verified sourceMeasuredRead 8h ago.
  • Contract interfaceMeasuredRead 8h ago.

Market

  • Current marketMeasuredRead 4m ago.
  • Market historyMeasuredRead today.
  • Supply distributionNot enough yetHEY has not mapped this token’s supply yet.
  • LocksMeasuredRead 2h ago.
  • Market checksMeasured

Not applicable here: Repository details, Published packages, 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
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)X (opens in a new tab)DEX Screener (opens in a new tab)RHTools (opens in a new tab)Sources

Latest ship

Checked

Code changes this week (since Mon 26 Oct) · 3 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:

2 active days in runehood/runehood-contracts.

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.

Record ship:fea0015c… · 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-10-29; HEY first knew on 2026-10-29.
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)

Shared change · Published

RuneHood was published on HEY with its sources recorded.

Builder status: Shipping.

Observed by HEY on 2026-10-29Source: HEY’s research record

Evidence receipt

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

4 changes on HEY’s record for RuneHood: 1 verification change · 1 token verification change · 1 new project on HEY · 1 week of code pushed.

All 4 changes for RuneHood →

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

Contract 0x437d083c57BB31573Aa383f9602ec5a86519b9d4 on Robinhood Chain

0x437d…b9d40x437d083c57bb31573aa383f9602ec5a86519b9d4

Project names this contract: The project’s own site names this contract.

Market context

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

Token

Launch stage
Trading in a DEX pool
Pair age
11h ago

Market

24h volume
$33K
Trades 24h
287 buys · 221 sells
Price 24h
down 92.0 percent over 24 hours· 6hdown 0.6 percent over 6 hours· 1hup 0.4 percent over 1 hour

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

Market history, trading and checks →

Questions HEY can answer about RuneHood — as of 29 Oct

Show the answers
Is RuneHood still being built?
DerivedShipping: 1 counted ship in 30 days; latest ship today. Evidence
What did RuneHood ship last?
FactCode changes this week (since Mon 26 Oct) · 3 commits — Code activity, today. Evidence
Is 0x437d083c57BB31573Aa383f9602ec5a86519b9d4 RuneHood’s own contract?
FactProject names this contract: The project’s own site names this contract. Details
What does HEY not know about RuneHood?
Unknown4 gaps: Official docs (not tied to the project yet), API description (not enough yet), Official site changes (not enough yet), +1 more. HEY found a docs link on its website and holds it until the website is tied to the project.

Sources

5 places HEY reads for RuneHood