Skip to content

Bittensor

$tao

AI · Utility

Not named by the project: 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 0xf3081494b87e8d5fb7960f066e931d1d0e6e3d67

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

Is this your project? Claim it →

Bittensor is an open-source protocol that powers a decentralized, blockchain-based machine learning network. Machine learning models train collaboratively and are rewarded in TAO according to the informational value they offer the collective. TAO also grants external access, allowing users to extract information from the network while tuning its activities to their needs. Ultimately, BitTensors vision is to create a pure market for artificial intelligence, an incentivized arena in which consumers and producers of this valuable commodity can interact in a trustless, open and transparent context. Bittensor enables: -A novel, optimized strategy for the development and distribution of artificial intelligence technology by leveraging the possibilities of a distributed ledger. Specifically, its facilitation of open access/ownership, decentralized governance, and the ability to harness globally-distributed resources of computing power and innovation within an incentivized framework. -An open-source repository of machine intelligence, accessible to anyone, anywhere, thus creating the conditions for open and permission-less innovation on a global internet scale. -Distribution of rewards and network ownership to users in direct proportion to the value they have added.

Read more

What HEY knows

Building
Not measuredBuilder source held, not countedHEY holds a repository, changelog or feed only as context — nothing yet ties it to the project — so no count here is a measured zero. Details
FollowCreate alertTerminal preview
Get updates

Get updates

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

No account? Email me Bittensor’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.

Share
Known so far
Deployed
26 Aug, read from the chain
Launched via
Pons
Token market
Launch pool onlyNot named by the project
Product usage
1 of 1 watched contract active · 32 calls to the contracts' own functions in 7 days; the other 55,052 of 55,084 calls were ERC-20 token transfers and approvals, which trading alone produces.
Latest read
HEY last read this project’s records 18m ago.

What HEY can’t confirm yet

  • Building activity, Releases — No repository, changelog or feed to read.
  • Repositories — Repositories listed, none counted yet: each is held as context, and the page says why under it.
  • Official docs — HEY found a docs link on its website and holds it until the website is tied to the project.
  • Official site changes — Its website is not yet 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
Not measured — builder source held, not counted.
HEY holds no repository, changelog or feed it can read building from, so it cannot say whether anyone is building.
SourceHEY holds no repository, changelog or feed it can read for this project.ReadWhat HEY derivedHEY’s activity rule reads the counted events as “Not measured — builder source held, not counted”.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".
Not named by the project.
Not named by the project: HEY has not confirmed that the project stands behind this contract — HEY knows it from a launchpad record, and the site that record named does not name it.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedNot named by the project: 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.
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.
Source9 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 cannot answer whether anyone is building this yet (building activity: no source); it can answer 11 of the 16 research questions that apply.
11 of 16 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 49d ago.

Building

  • Building activityNo sourceNo repository, changelog or feed to read.
  • RepositoriesNot tied to the project yetRepositories listed, none counted yet: each is held as context, and the page says why under it.
  • ReleasesNo sourceNo repository, changelog or feed to read.
  • TimelineMeasured

Official site

  • Official docsNot tied to the project yetHEY found a docs link on its website and holds it until the website is tied to the project.
  • Official site changesNot tied to the project yetIts website is not yet confirmed as the project’s own.

Contracts

  • Contract creationMeasuredRead 22h ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 10h ago.
  • Contract interfaceMeasuredRead 10h ago.

Market

  • Current marketMeasuredRead 18m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead 2d ago.
  • LocksMeasuredRead 1h ago.
  • Market checksMeasured

Not applicable here: API description, Repository details, Published packages, 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

Launch record

The token’s deployment, read from the chain. HEY records it as provenance, never as building.

  1. Verified contract source published: BurnMintERC20

    Contract source verifiedSource-backed

    BurnMintERC20 at 0xf308…3d67 has verified source on Robinhood Chain Blockscout (compiler 0.8.27+commit.40a35a09).

Other changes on HEY’s record

10 changes on HEY’s record for Bittensor: 1 new Verified Builder or owner proof · 9 market moves.

All 10 changes for Bittensor →

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

0xf308…3d670xf3081494b87e8d5fb7960f066e931d1d0e6e3d67

Not named by the project.

Market context

Launch pool only · FDV (fully diluted) $1.2M · liquidity $840K (launch pool inventory, not a market) · reading under an hour old (DEX Screener).

Token

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

Market

24h volume
$90K
Trades 24h
273 buys · 178 sells
Price 24h
up 1.2 percent over 24 hours· 6hup 0.3 percent over 6 hours

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 →

Market integrity

Liquidity is 20% below the level it held two days running ($1.0M, 2026-10-14).

Market
Launch pool only
Last day with trading
2026-10-30

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-31 18:58 UTC · How HEY checks this

Sources

8 places HEY reads for Bittensor
  • Website
    https://bittensor.com/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://forevermoney.aiContext onlyThe same reason as the row above that explains it.
  • Docs
    https://www.bittensor.com/docsContext onlyThe same reason as the row above that explains it.
  • Repository
    https://github.com/RaoFoundation/bittensorContext onlyContext only because a launch record or a listing declared this repository and nothing yet ties it to this token; it counts once the repository names the token’s contract, HEY’s code search finds a Robinhood Chain marker in one of the project’s own repositories, a GitHub claim names it, the project’s site names the token’s contract, or a moderator confirms it.
  • X
    https://x.com/forevermoney_aiFrom a launch or market listing
  • X
    https://x.com/opentensor@opentensor links back to bittensor.com — checked 2026-10-31.From a launch or market listing
  • Telegram
    https://t.me/taobittensorFrom a launch or market listing
  • Discord
    https://discord.gg/bittensorFrom a launch or market listing

Every repository above is held as context, for the reason written under it: nothing read from them counts as this project’s building or sets its activity status.