Skip to content

Rothera Network

$ROTHERA

Agentic Finance

Contract 0xbcd104d018e94a4f1bb199340aacf365479124f0

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

Is this your project? Claim it →

Compute from the quiet hours. A marketplace that pools idle GPUs into one compute network for apps and AI agents.

What HEY knows

Development

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

Build Momentum 38How it is measured

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

Token market · context

Launch pool only

Token check

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

Get updates

Follow puts Rothera Network 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 Rothera Network

No account? Email me Rothera Network’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
Discovery Gap not measured — market too thin. 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
UnknownHEY has not read this project’s contracts for implementation or interface changes yet.
Not yet known
Unknown8 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet), Contract creation (not enough yet), Published source code (not enough yet), Contract interface (not enough yet), Market history (not enough yet), Supply distribution (not enough yet). 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: 2 counted ships in the last 30 days, the newest 2026-11-17.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 16 Nov) · 6 commitsv0.1.0 · Initial public documentationWhat 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 16 Nov) · 6 commitsv0.1.0 · Initial public documentationsource:376ae676-e244-4a60-aa09-7b589847e890+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.
Launch pool only.
Launch pool only: the only pool is the launch pool holding the token’s own supply, and it traded in the last day.
Source5 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Launch pool only”.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 — market too thin.
Not measured — market too thin: the tracked token's market reads “Launch pool only”. 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 11 of the 19 research questions that apply.
11 of 19 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 2h ago.

Building

  • Building activityMeasuredRead 1h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 14h ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • 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 1h ago.
  • Published packagesMeasuredRead 1h ago.

Contracts

  • Contract creationNot enough yetHEY has not read the contract’s creation yet.
  • Contract activityMeasuredRead today.
  • Published source codeNot enough yetHEY has not read the contract’s published source yet.
  • Contract interfaceNot enough yetHEY has not read the contract’s published source yet.

Market

  • Current marketMeasuredRead 17m ago.
  • Market historyNot enough yetNo daily market history recorded yet.
  • Supply distributionNot enough yetHEY has not mapped this token’s supply yet.
  • LocksMeasuredRead 2h 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) · 6 commits

Code activitySource-backed

Why it matters: The first week of code changes HEY has recorded for this project.

1 active day in rotheranetwork-collab/rothera-network.

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

Record ship:6450b408… · 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-17; HEY first knew on 2026-11-18.
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 1 week since HEY began reading this project’s sources; earlier weeks are not yet read, not zero.

1-week shipping streak

Build timeline

  1. v0.1.0 · Initial public documentation

    GitHub releaseSource-backed

    First public release of the Rothera Network repository: README, architecture, builder API (v1 preview), node operator guide, verification, tokenomics, FAQ, examples (curl, Python, TypeScript, node config, MCP) and community files. > Rothera is in Phase 0 (design). Nodes, API… Show all

    First public release of the Rothera Network repository: README, architecture, builder API (v1 preview), node operator guide, verification, tokenomics, FAQ, examples (curl, Python, TypeScript, node config, MCP) and community files. > Rothera is in Phase 0 (design). Nodes, API, contracts and token are not live. All figures are drafts.

Other changes on HEY’s record

4 changes on HEY’s record for Rothera Network: 1 release · 1 new Verified Builder or owner proof · 1 new project on HEY · 1 week of code pushed.

All 4 changes for Rothera Network →

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 0xbcd104D018e94A4f1bb199340aAcf365479124f0 on Robinhood Chain

0xbcd1…24f00xbcd104d018e94a4f1bb199340aacf365479124f0

Project names this contract.

Market context

Launch pool only · FDV (fully diluted) $3.7K · liquidity $3.7K (launch pool inventory, not a market) · reading under an hour old (GeckoTerminal).

Token

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

Market

24h volume
$29K
Trades 24h
358 buys · 227 sells
Price 24h
up 15.6 percent over 24 hours· 6hdown 3.5 percent over 6 hours· 1hunchanged over 1 hour

The pool still holds the token’s own supply, so its reported liquidity is not a depth figure; trades in the last 24 hours are what make this a market.

Market history, trading and checks →

Sources

3 places HEY reads for Rothera Network