Skip to content
HEY Research Lab
Menu

HOODX

Is this your project? Claim it →

Community index factory on Robinhood Chain — not Robinhood Markets. Build an index, share it, earn a cut. $696X is Gen-0.

What HEY knows

Development

Shipped this weekShipping: 4 counted ships in 30 days; latest ship 2 days ago. Evidence Source

Build Momentum 46How it is measured

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

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

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

No account? Email me HOODX’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
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: 4 counted ships in the last 30 days, the newest 2026-11-02.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 2 Nov) · 2 commitsCode changes, week of 2026-10-19 – 2026-10-25 · 9 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 3 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 counted building from the project's own sources.
Source3 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 2 Nov) · 2 commitsCode changes, week of 2026-10-19 – 2026-10-25 · 9 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 3 commits+4 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.
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 4d ago.

Code and packages

  • Repository detailsMeasuredRead 12m ago.
  • Published packagesMeasuredRead 12m 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)X (opens in a new tab)Sources

Latest ship

Checked

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

Code activitySource-backed

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

What changed, in the repository’s own words:

1 active day in thepaypay420/hoodx.

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.

Record ship:dae5e17d… · 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-02; 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.

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: 4 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-10-19 – 2026-10-25 · 9 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in thepaypay420/hoodx.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-10-19 – 2026-10-25 · 9 commits (opens in a new tab)

  2. Code changes, week of 2026-10-12 – 2026-10-18 · 3 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in thepaypay420/hoodx.

    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.

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 3 commits (opens in a new tab)

  3. Code changes, week of 2026-10-05 – 2026-10-11 · 16 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in thepaypay420/hoodx.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 16 commits (opens in a new tab)

  4. Code changes, week of 2026-09-28 – 2026-10-04 · 93 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    7 active days in thepaypay420/hoodx.

    How HEY read this week

    This week HEY looked inside 4 of 93 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 93 commits (opens in a new tab)

  5. Code changes, week of 2026-09-21 – 2026-09-27 · at least 95 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    at least 7 active days in thepaypay420/hoodx since 2026-09-21; the count stops at the newest 100 commits listed.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · at least 95 commits (opens in a new tab)

  6. Code changes, week of 2026-09-14 – 2026-09-20 · at least 98 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    at least 5 active days in thepaypay420/hoodx since 2026-09-16; the count stops at the newest 100 commits listed.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 98 commits (opens in a new tab)

  7. Deployed a new contract: 0xe9c3…ea04

    New contractSource-backed

    The account that launched HOODX’s token deployed 0xe9c3…ea04 on 2026-06-10. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0xe9c3…ea04 (opens in a new tab)

  8. Deployed a new contract: 0xebbe…ef9e

    New contractSource-backed

    The account that launched HOODX’s token deployed 0xebbe…ef9e on 2026-06-10. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0xebbe…ef9e (opens in a new tab)
Earlier ships (11)

  1. Deployed a new contract: 0x5778…b70a

    New contractSource-backed

    The account that launched HOODX’s token deployed 0x5778…b70a on 2026-06-05. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0x5778…b70a (opens in a new tab)

  2. 2 contracts deployed by the project’s deployer between 10:48:13 and 10:48:14 UTC on 5 Jun

    New contract

    Show all 2 contracts

    1. Deployed a new contract: VaultV2AllocatorProxy

      New contractSource-backed

      The account that launched HOODX’s token deployed VaultV2AllocatorProxy at 0xd7d7…7e81 on 2026-06-05. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: VaultV2AllocatorProxy (opens in a new tab)

    2. Deployed a new contract: VaultV2Allocator

      New contractSource-backed

      The account that launched HOODX’s token deployed VaultV2Allocator at 0x398a…f517 on 2026-06-05. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: VaultV2Allocator (opens in a new tab)

  3. Deployed a new contract: FundingMorphoFactory

    New contractSource-backed

    The account that launched HOODX’s token deployed FundingMorphoFactory at 0xbb0c…ef91 on 2026-06-05. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: FundingMorphoFactory (opens in a new tab)

  4. Deployed a new contract: FlashLoanMorpho

    New contractSource-backed

    The account that launched HOODX’s token deployed FlashLoanMorpho at 0xde0a…78e4 on 2026-06-05. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: FlashLoanMorpho (opens in a new tab)

  5. Deployed a new contract: BoxAdapterFactory

    New contractSource-backed

    The account that launched HOODX’s token deployed BoxAdapterFactory at 0x83ba…7aa8 on 2026-06-05. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: BoxAdapterFactory (opens in a new tab)

  6. Deployed a new contract: BoxFactory

    New contractSource-backed

    The account that launched HOODX’s token deployed BoxFactory at 0x1848…39cc on 2026-06-05. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: BoxFactory (opens in a new tab)

  7. Deployed a new contract: MetaOracleDeviationTimelockFactory

    New contractSource-backed

    The account that launched HOODX’s token deployed MetaOracleDeviationTimelockFactory at 0xb9a0…184b on 2026-06-04. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: MetaOracleDeviationTimelockFactory (opens in a new tab)

  8. Deployed a new contract: MorphoMarketFactory

    New contractSource-backed

    The account that launched HOODX’s token deployed MorphoMarketFactory at 0x7371…e67f on 2026-06-04. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: MorphoMarketFactory (opens in a new tab)

  9. Deployed a new contract: MorphoReader

    New contractSource-backed

    The account that launched HOODX’s token deployed MorphoReader at 0x4ca5…02f4 on 2026-06-04. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: MorphoReader (opens in a new tab)

  10. Deployed a new contract: VaultV2Supervisor

    New contractSource-backed

    The account that launched HOODX’s token deployed VaultV2Supervisor at 0x261a…f2b1 on 2026-06-04. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: VaultV2Supervisor (opens in a new tab)

Other changes on HEY’s record

23 changes on HEY’s record for HOODX: 1 new Verified Builder or owner proof · 1 token check change · 1 market check · 13 contract changes · 7 other changes in 1 more kind.

  • Market check

    The project is building while its token trades with little liquidity. Token market status: low liquidity. This describes the token market, not whether development has stopped.

    See the change for Market check

  • Token check

    Token check: now “Not named by the project” (was “Project names this contract”)

    See the change for Token check

All 23 changes for HOODX →

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

Sources

3 places HEY reads for HOODX