Is Trends Based Tokens still being built?

Active: 1 meaningful event in 30 days; latest ship 17 days ago.

What does HEY not know about Trends Based Tokens?

3 gaps: Official docs (no source), API description (not tied to the project yet), Official site changes (not tied to the project yet). HEY read its website and found no link to docs.

Trends Based Tokens

$TREND

AI Agents

Token unverified: HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership. Token market

Contract 0x2fc967b0da46c21b1f1a66b624ed296ea85d3b07

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

HEY verified shipping evidence from the project’s own public sources; ownership of this page is not claimed yet.

Is this your project? Claim and verify →

TREND Based Tokens is the agentic economics model in social Platforms like memes styles based tokens at X, Farcaster, Clawkai. It will be more than a memes based token, it was planned for integrating with llm-credits protocol system. If you want more trends based data, HODL

Building: Last shipped 17 days agoActive: 1 meaningful event in 30 days; latest ship 17 days ago. Evidence Source
Build Momentum 20How it is measured
Latest ship: Code changes, week of 2026-09-28 – 2026-10-04 · 18 commits · 17d ago · Code activity
Why it matters: First week of code changes after 41 quiet days.
Latest change: Derived9 days ago: HEY reclassified the project — activity status moved from Shipping to Active. Evidence

FollowCreate alert Terminal previewView latest ship

Follow puts Trends Based Tokens on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me Trends Based Tokens’s changes

Or read its RSS feed.

Product usage: FactNo calls to its 1 watched contract in 7 days.
Counted from the chain. Usage says the contracts are used, not that anyone is building.
Contracts: Fact1 contract on record for code changes, 1 with verified source; no implementation or interface change recorded.
Token market · context: Trading inactiveToken unverified
Not yet known: Unknown3 gaps: Official docs (no source), API description (not tied to the project yet), Official site changes (not tied to the project yet). HEY read its website and found no link to docs.
HEY can answer 16 of the 19 research questions that apply · Research coverage

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: 1 meaningful event in the last 30 days, the newest 2026-10-02.; SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.Read6h agoRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 18 commits Code changes, week of 2026-08-17 – 2026-08-23 · 5 commitsWhat 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 verified building evidence from the project's own sources.; Source8 registered sources, 2 of them context only.Read1mo agoRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 18 commits Code changes, week of 2026-08-17 – 2026-08-23 · 5 commits source:49cb4839-6e6b-48df-a0bc-74ed705b0db0+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.
Token unverified.: Token unverified: HEY found the token through a launch record or a market listing, and nothing the project published names it.; SourceThe project's own published sources and HEY's check of the contract.What HEY derivedToken unverified: HEY knows it from a launchpad record, and the site that record named does not name it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Trading inactive.: Trading inactive: the only pool is the launch pool holding the token’s own supply, and nothing traded in it in the last day.; Source6 readings from HEY's own market tables.Read4h agoWhat HEY derivedHEY’s market rule reads this token’s market as “Trading inactive”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.; Market figures are context only and never change activity status. Methodology

LinksWebsite (context only)GitHubX account @Ton_Proj_Auth not found, checked 2026-10-18.DEX Screener RHTools Sources

Latest ship

Checked 1h ago

Code changes, week of 2026-09-28 – 2026-10-04 · 18 commitshakuramasam/thirdeye-ai

17d ago

Code activitySource linked

What changed, in the repository’s own words:

2 active days in hakuramasam/thirdeye-ai.

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:c1c95066… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

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: 3 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about Trends Based Tokens — as of 2026-10-19

Is Trends Based Tokens still being built?: DerivedActive: 1 meaningful event in 30 days; latest ship 17 days ago. Evidence
What did Trends Based Tokens ship last?: FactCode changes, week of 2026-09-28 – 2026-10-04 · 18 commits — Code activity, 17 days ago. Evidence
Is 0x2fc967B0dA46c21B1f1A66b624ed296EA85d3b07 Trends Based Tokens’s own contract?: UnknownToken unverified: HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership. Details
What does HEY not know about Trends Based Tokens?: Unknown3 gaps: Official docs (no source), API description (not tied to the project yet), Official site changes (not tied to the project yet). HEY read its website and found no link to docs. Details

Build timeline

Code changes, week of 2026-08-17 – 2026-08-23 · 5 commitshakuramasam/orebot-network-contracts
1mo ago
Code activitySource linked
What changed, in the repository’s own words:
2 active days in hakuramasam/orebot-network-contracts.
This week HEY looked inside 1 of 5 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.
View evidence

Around the latest ship

Observed after, over 7 days: calls 0/day (before: 0/day) · volume $0/day (before: $0/day) · liquidity $20.5K (before: $20.5K).

Code changes, week of 2026-09-28 – 2026-10-04 · 18 commitsCode activityin the week of 28 Sep (week precision)

Observed before (21–27 Sep) and Observed after (5–11 Oct): Code changes, week of 2026-09-28 – 2026-10-04 · 18 commits
Measure	Observed before21–27 Sep	Observed after5–11 Oct
Volume per day	$0/day	$0/day
Liquidity	$20.5K	$20.5Kunchanged against the days beforevs beforeagainst before
Calls per day	0/day	0/day
Active contracts (busiest day)	0	0
Distinct caller addresses (busiest day)	0	0

Not shown: Price and valuation: the market is not live

Observed around the same time — HEY does not claim this event caused it.

Market context and product usage, placed by time. Seven days either side; the day in progress is never compared. Open evidence As data

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about Trends Based Tokens? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

4 changes on HEY’s record for Trends Based Tokens: 1 verification change · 1 market check · 2 weeks of code pushed.

Verification10d ago
Research standing moved from Published to Verified builder
See the change
Code pushed17d ago · recorded by HEY 10d ago
Code changes, week of 2026-09-28 – 2026-10-04 · 18 commits
See the change Source ↗
Market check1mo ago · recorded by HEY 25d ago
No trade recorded since 2026-09-10, on HEY's daily readings of the market since then.
See the change
Code pushed1mo ago · recorded by HEY 1mo ago
Code changes, week of 2026-08-17 – 2026-08-23 · 5 commits
See the change Source ↗

Trends Based Tokens on What changed →

The full change record holds 7 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 16 of the 19 research questions that apply.

16 of 19 applicable dimensions measuredShow each dimension

Identity

IdentityMeasuredRead 1mo ago.

Building

Building activityMeasuredRead 1h ago.
RepositoriesMeasured
ReleasesMeasured
TimelineMeasured

Official site

Official docsNo sourceHEY read its website and found no link to docs.
API descriptionNot tied to the project yetIts website is not yet confirmed as the project’s own.
Official site changesNot tied to the project yetIts website is not yet confirmed as the project’s own.

Code and packages

Repository detailsMeasuredRead 3d ago.
Published packagesMeasuredRead 3d ago.

Contracts

Contract creationMeasuredRead 21h ago.
Contract activityMeasuredRead yesterday.
Verified sourceMeasuredRead 3d ago.
Contract interfaceMeasuredRead 3d ago.

Market

Current marketMeasuredRead 4h ago.
Market historyMeasuredRead yesterday.
Supply distributionMeasuredRead 1mo ago.
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.

Sources

Website
https://orebot-network.lovable.app/Context onlyContext only because HEY reached this site through a launch record or a listing and nothing yet ties it to this token; it counts once the site names the token’s contract, a GitHub claim names one of the project’s repositories, or a moderator confirms one of them.
Website
https://thirdeye-ai-alpha.vercel.appContext onlyContext only because HEY reached this site through a launch record or a listing and nothing yet ties it to this token; it counts once the site names the token’s contract, a GitHub claim names one of the project’s repositories, or a moderator confirms one of them.
Repository
https://github.com/hakuramasam/orebot-network-contractsOfficial
Repository
https://github.com/hakuramasam/thirdeye-aiOfficial
GitHub org
https://github.com/hakuramasamOfficial
X
https://x.com/Ton_Proj_AuthX account @Ton_Proj_Auth not found, checked 2026-10-18.From a launch or market listing
Farcaster
https://farcaster.xyz/haku85From a launch or market listing
Telegram
https://t.me/orebot_networkFrom a launch or market listing

Contract

0x2fc9…3b07

Build Momentum

Last shipped 17 days ago · Build Momentum 20

SHIPPING: 4
CONSISTENCY: 17
SIGNIFICANCE: 11
EVIDENCE: 70 — strongest component
SOURCES: 33

How steadily, how recently and how verifiably this project ships, from 0 to 100 — this project on its own, never price. How it is measured

Under the Radar

Not measured — no live market

The tracked token has no live market, so it has no market-attention percentile.

Shipping weeks / last 12

Builder Radar

#500 on today’s Builder Radar▼ 72 over 7 days

The board that ranks builders against each other on verified development, on-chain use and research standing. Price never counts.

The three parts

Development: 20
On-chain use: Not measured yet
Research standing: 100
Overall: 28

Methodology

Public code activity

29/ 100

A reading of the public repositories over 60 days — active days, releases, contributors and how recent — kept apart from Build Momentum.

Days with recorded activity: 4 / 60
Contributors: 4
GitHub releases: 0
Last code update: 17d ago

Observed development days. Commit volume is capped and never ranked.

Merged pull requests not measured; the remaining dimensions are reweighted rather than counted as zero.

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

Contract 0x2fc967B0dA46c21B1f1A66b624ed296EA85d3b07 on Robinhood Chain

0x2fc9…3b07

Market context

Trading inactive: HEY holds a valuation and does not publish it while the market is not live.

Token

Launch stage: Trading in a DEX pool
Pair age: 2mo ago

Market

Valuation: No active market
Liquidity: Not a market reading
24h volume: $0
Trades 24h: 0 buys · 0 sells
Price 24h: unchanged over 24 hours· 6hunchanged over 6 hours· 1hunchanged over 1 hour

The pool reports its liquidity as the token’s own supply at its last price, and recorded no trades in the last 24 hours. HEY does not read that reserve as liquidity.

HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership.

Read from GeckoTerminal, 4h ago.

Market history, trading and checks →

Market integrity

Liquidity holds its level; no trade recorded since 2026-09-10.

Market: Trading inactive
Last day with trading: 2026-09-10

2026-09-10No trade recorded since 2026-09-10, on HEY's daily readings of the market since then.

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-10-19 00:56 UTC · How HEY checks this

Is this your project?

Claim the profile to post what you ship and keep this page accurate.

Claiming verifies ownership; by itself it changes no status, score or order.

Claim this project

Builders: show this status. Your HEY badge — Show it on your site or README; it changes no status, score or order.

For the builders: share this research profile — a post, the README badge, an embed and the evidence links.

Something wrong here? Report an error on this page

How HEY researches your project

Your HEY research profile is liveFor the team behind Trends Based Tokens: share it, badge it, embed it.

HEY verified Trends Based Tokens as a builder: an official source with a meaningful ship, and evidence on Robinhood Chain. This page updates itself as you ship.

Open the full share pack

Share verified builder status

Post on X Share card image

Trends Based Tokens ($TREND) — Active · Verified Builder · latest ship 2 Oct: Code changes, week of 2026-09-28 – 2026-10-04 · 18 commits · via Clanker · on HEY Research Lab
https://heyresearch.xyz/project/trends-based-tokens

Add HEY badge to GitHub

Paste into your README. It shows your activity status and last ship, and links here.

[![Trends Based Tokens on HEY Research Lab](https://heyresearch.xyz/api/badge/trends-based-tokens)](https://heyresearch.xyz/project/trends-based-tokens?utm_source=badge&utm_medium=readme)

Add HEY intelligence to your site

A live builder widget, the same facts as this page. Choose a variant and theme.

<script src="https://heyresearch.xyz/embed/hey-project.js" async></script>
<hey-project project="trends-based-tokens" variant="builder" theme="auto">
  <a href="https://heyresearch.xyz/project/trends-based-tokens">Trends Based Tokens on HEY Research Lab</a>
</hey-project>

Canonical page: https://heyresearch.xyz/project/trends-based-tokens
API: https://heyresearch.xyz/api/projects/trends-based-tokens/snapshot
Partner card (by contract): https://heyresearch.xyz/api/v1/scan?chain=4663&token=0x2fc967b0da46c21b1f1a66b624ed296ea85d3b07
Changes feed: https://heyresearch.xyz/api/changes?project=trends-based-tokens
Research receipts: An agent citing this project names it as { "subjectType": "project", "subject": { "chainId": 4663, "projectSlug": "trends-based-tokens" } }. How receipts work

Everything here is public. HEY never contacts builders about it.

Embeddable badgeMethodology

Builder activity

Questions HEY can answer about Trends Based Tokens — as of 2026-10-19

Build timeline

Code changes, week of 2026-08-17 – 2026-08-23 · 5 commitshakuramasam/orebot-network-contracts

Around the latest ship

Research notes

What changed

Research coverage

Identity

Building

Official site

Code and packages

Contracts

Market

Sources

Around the latest ship