Skip to content

NUTZ

$NUTZ

StockFi · Utility

Contract 0x5a8e6bb390b51978b0cea029a070cfcdd495138e

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

Is this your project? Claim it →

🐿️ The squirrel that pays you. Hold $NUTZ. Every hour the squirrel drops tokenized stocks (SPY, NVDA, MU, SPCX) and USDG cash straight into your wallet. No staking. No claiming. No team cut.

What HEY knows

Development

Last shipped 9 days agoActive: 4 counted ships in 30 days; latest ship 9 days ago. Evidence Source

Build Momentum 45How it is measured

Latest: v0.6.0

Token market · context

Active market

Token check

Project names this contract
FollowCreate alertTerminal preview
Get updates

Get updates

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

No account? Email me NUTZ’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
Discovery Gap not measured — 24h volume under $1,000. What the Discovery Gap is
More detail
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
Fact3 contracts on record for code changes, 2 with published source code; no implementation or interface change recorded.
Not yet known
Unknown4 gaps: API description (not enough yet), Official site changes (not enough yet), Market history (not enough yet), Supply distribution (not enough yet). HEY has not read its website’s published files yet.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule: 4 counted ships in the last 30 days, the newest 2026-10-22.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv0.6.0Code changes, week of 2026-10-19 – 2026-10-25 · 1 commitv0.5.0+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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.
Source12 registered sources, 1 of them context only.ReadRecordsv0.6.0Code changes, week of 2026-10-19 – 2026-10-25 · 1 commitv0.5.0+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 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.
Source4 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.
Discovery Gap: Not measured — 24h volume under $1,000.
Not measured — market too thin: the tracked token's market reads “Active market” but traded $10.95 in the 24 hours of its reading, under the $1,000 a measured market needs. A Discovery Gap is measured only on an active market that is more than a launch curve and trades at least $1,000 a day: a thin market's attention percentile sits near the floor, so its gap would measure the thinness, not the building.
SourceThe score row: the Build Momentum percentile and the market-attention percentile, both taken over the projects with a market reading.ReadWhat HEY derivedNot measured — market too thin.Not concludedIt compares building with market attention; it is not a prediction and not a reason to trade.
Research coverage: HEY can answer 16 of the 20 research questions that apply.
16 of 20 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 6d ago.

Building

  • Building activityMeasuredRead 3h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 9d ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 2h ago.
  • 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.

Code and packages

  • Repository detailsMeasuredRead 2h ago.
  • Published packagesMeasuredRead 52m ago.
  • Package advisoriesMeasuredRead 2h ago.

Contracts

  • Contract creationMeasuredRead 2h ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 1h ago.
  • Contract interfaceMeasuredRead 1h ago.

Market

  • Current marketMeasuredRead 1h ago.
  • Market historyNot enough yetNo daily market history recorded yet.
  • Supply distributionNot enough yetHEY has not mapped this token’s supply yet.
  • LocksMeasuredRead 4h ago.
  • Market checksMeasured

Not applicable here: 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

v0.6.0 nutzwtf/nutz-verify

GitHub releaseSource-backed

Why it matters: First release after 14 quiet days.

Built from f4a4e0c01e2d6380cef9359c7d5b9c7a57581a11 by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and… Show all

Built from f4a4e0c01e2d6380cef9359c7d5b9c7a57581a11 by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and produced identical checksums; a release is not published otherwise. Check a download before running it: sha256sum -c SHA256SUMS --ignore-missing Reproduce the checksums from source: git checkout v0.6.0 scripts/build-release.sh diff dist/SHA256SUMS <(curl -sL…

Record ship:741d47e7… · 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: 7 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 · 1 commit nutzwtf/nutz-verify

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in nutzwtf/nutz-verify.

    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-19 – 2026-10-25 · 2 commits nutzwtf/nutz-contracts

    Code activitySource-backed

    2 active days in nutzwtf/nutz-contracts.

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

  3. v0.5.0 nutzwtf/nutz-verify

    GitHub releaseSource-backed

    Built from d50de067b1019aa05637bfc41bb4b8f9b48b6f1b by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and… Show all

    Built from d50de067b1019aa05637bfc41bb4b8f9b48b6f1b by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and produced identical checksums; a release is not published otherwise. Check a download before running it: sha256sum -c SHA256SUMS --ignore-missing Reproduce the checksums from source: git checkout v0.5.0 scripts/build-release.sh diff dist/SHA256SUMS <(curl -sL…

  4. v0.4.0 nutzwtf/nutz-verify

    GitHub releaseSource-backed

    Built from 05926763d9b816301ff8bbc8bda52ae35030ef29 by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and… Show all

    Built from 05926763d9b816301ff8bbc8bda52ae35030ef29 by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and produced identical checksums; a release is not published otherwise. Check a download before running it: sha256sum -c SHA256SUMS --ignore-missing Reproduce the checksums from source: git checkout v0.4.0 scripts/build-release.sh diff dist/SHA256SUMS <(curl -sL…

  5. v0.3.0 nutzwtf/nutz-verify

    GitHub releaseSource-backed

    Built from 5f55cc1069fe44b0af5ea95422adaaa4b38dcf56 by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and… Show all

    Built from 5f55cc1069fe44b0af5ea95422adaaa4b38dcf56 by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and produced identical checksums; a release is not published otherwise. Check a download before running it: sha256sum -c SHA256SUMS --ignore-missing Reproduce the checksums from source: git checkout v0.3.0 scripts/build-release.sh diff dist/SHA256SUMS <(curl -sL…

  6. v0.2.0 nutzwtf/nutz-verify

    GitHub releaseSource-backed

    Built from d7d7856abf903bd50bc06cf20cb5fb5aa3e307c6 by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and… Show all

    Built from d7d7856abf903bd50bc06cf20cb5fb5aa3e307c6 by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and produced identical checksums; a release is not published otherwise. Check a download before running it: sha256sum -c SHA256SUMS --ignore-missing Reproduce the checksums from source: git checkout v0.2.0 scripts/build-release.sh diff dist/SHA256SUMS <(curl -sL…

  7. v0.1.0 nutzwtf/nutz-verify

    GitHub releaseSource-backed

    Built from 3e90e4ee95e79dd636bce6e0142fb1b3ee28a492 by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and… Show all

    Built from 3e90e4ee95e79dd636bce6e0142fb1b3ee28a492 by scripts/build-release.sh with go1.26.8: CGO_ENABLED=0 go build -trimpath -buildvcs=false, cross-compiled to linux and darwin on amd64 and arm64. Two machines (ubuntu-latest and macos-latest) built this tag independently and produced identical checksums; a release is not published otherwise. Check a download before running it: sha256sum -c SHA256SUMS --ignore-missing Reproduce the checksums from source: git checkout v0.1.0 scripts/build-release.sh diff dist/SHA256SUMS <(curl -sL…

Other changes on HEY’s record

9 changes on HEY’s record for NUTZ: 6 releases · 1 new project on HEY · 2 weeks of code pushed.

All 9 changes for NUTZ →

The full change record holds 13 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 0x5a8E6Bb390b51978B0Cea029A070cfCDd495138E on Robinhood Chain

0x5a8e…138e0x5a8e6bb390b51978b0cea029a070cfcdd495138e

Project names this contract.

Market context

Active market · FDV (fully diluted) $49.4K · current liquidity $19.5K · reading 1 h old (DEX Screener).

Token

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

Market

24h volume
$11
Trades 24h
1 buys · 2 sells
Price 24h
up 0.6 percent over 24 hours

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

Market history, trading and checks →

Questions HEY can answer about NUTZ — as of 31 Oct

Show the answers
Is NUTZ still being built?
DerivedActive: 4 counted ships in 30 days; latest ship 9 days ago. Evidence
What did NUTZ ship last?
Factv0.6.0 — GitHub release, 9 days ago. Evidence
Is 0x5a8E6Bb390b51978B0Cea029A070cfCDd495138E NUTZ’s own contract?
FactProject names this contract: The project’s own site names this contract. Details
What does HEY not know about NUTZ?
Unknown4 gaps: API description (not enough yet), Official site changes (not enough yet), Market history (not enough yet), +1 more. HEY has not read its website’s published files yet.

Sources

12 places HEY reads for NUTZ