Skip to content

RUSHR

$RUSHR

AI Agents · Utility

Contract 0xa8ceeeb747fcf136947c35c5de6187ee90d6bfed

HEY holds 14 other Robinhood Chain tokens with the ticker $RUSHR. This page is only the contract above. See them

The open social trading for humans and AI agents, on Robinhood Chain

What HEY knows

Development

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

Build Momentum 34How it is measured

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

Token market · context

Active market$83K fully diluted valuation

Token check

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

Get updates

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

No account? Email me RUSHR’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 94.5% of them, its market attention ahead of 86.7% (a gap of 7.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
Fact1 of 1 watched contract active · 186 calls to the contracts' own functions over the 3 of 7 days HEY holds; the other 12,249 of 12,435 calls were ERC-20 token transfers and approvals, which trading alone produces; the rest unknown, not zero.

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

Contracts
Fact2 contracts on record for code changes, 1 with published source code; no implementation or interface change recorded.
Not yet known
Unknown2 gaps: Published packages (not enough yet), API description (no source). 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: 2 counted ships in the last 30 days, the newest 2026-11-16.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 16 Nov) · 18 commitsCode changes, week of 2026-11-09 – 2026-11-15 · 248 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 counted building from the project's own sources.
Source8 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 16 Nov) · 18 commitsCode changes, week of 2026-11-09 – 2026-11-15 · 248 commitssource:dfb45276-fd0b-42c1-9635-e72b2aa08c48+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.
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.
Source9 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 22h ago.

Building

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

Official site

  • Official docsMeasuredRead 41m ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 9h ago.

Code and packages

  • Repository detailsMeasuredRead 9h 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 21h ago.
  • Contract interfaceMeasuredRead 21h ago.

Market

  • Current marketMeasuredRead 4m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead today.
  • LocksMeasuredRead 1h 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 16 Nov) · 18 commits

Code activitySource-backed

1 active day in rushr-dev/platform.

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

Record ship:c5bc3442… · 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-16; HEY first knew on 2026-11-16.
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

2 meaningful, source-backed ships in the 2 weeks since HEY began reading this project’s sources; earlier weeks are not yet read, not zero.

2-week shipping streak

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-11-09 – 2026-11-15 · 248 commits

    Code activitySource-backed

    5 active days in rushr-dev/platform.

    How HEY read this week

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

Other changes on HEY’s record

8 changes on HEY’s record for RUSHR: 3 new Verified Builders or owner proofs · 1 token check change · 1 new project on HEY · 2 weeks of code pushed · 1 other change in 1 more kind.

All 8 changes for RUSHR →

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

0xa8ce…bfed0xa8ceeeb747fcf136947c35c5de6187ee90d6bfed

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

Market context

Active market · FDV (fully diluted) $83.1K · current liquidity $25.3K · reading under an hour old (DEX Screener) · sources disagree: GeckoTerminal priced it 6.1× lower within a day.

Token

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

Market

Liquidity
$25K
24h volume
$144K
Trades 24h
1,377 buys · 1,149 sells
Price 24h
up 144 percent over 24 hours· 6hdown 12.8 percent over 6 hours· 1hup 3.6 percent over 1 hour

The tracked token has liquidity, and trading volume was read for it within a day of its newest market reading — in that reading, or in HEY’s record of on-chain trades.

Read from DEX Screener, 4m ago.

Market history, trading and checks →

Market integrity

Two market sources describe different markets for this token; HEY is holding it for review.

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

HEY has not seen this token hold a market of $5K or more for 3 days, so there is no level to measure a fall against.

Two market sources describe different markets for this token; HEY is holding it for review rather than choosing one.

  1. Every event, with its figures, on the market page →

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-16 12:50 UTC · How HEY checks this

Sources

8 places HEY reads for RUSHR