Skip to main content

TaoHash

TaoHash — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

TaoHash — an Infra project on the Bittensor network (subnet 14), subnet token (symbol: TAOHASH / ALPHA).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: Bittensor subnet 14 about the production/pooling of PoW hashrate (BTC mining) and verifiable distribution of rewards.
  • Who it’s for: miners (contribute hashrate/shares), validators (verify the contribution and calculate weights), holders of the ALPHA/subnet token.
  • Why onchain/token: the subnet’s onchain mechanics distribute emissions/weights; the ALPHA/subnet token acts as “ownership” and an element of incentives (see Evidence).

How it works (very briefly)

  1. The user does: interacts with the project’s product/subnet.
  2. The system does: miners contribute BTC hashrate, the pool records shares/difficulty, validators evaluate the contribution by share value and set weights.
  3. The user gets: BTC rewards (per the protocol) and/or ALPHA/subnet token rewards (depending on participation).
  4. Where the blockchain is: Bittensor subnet 14 (subnet emissions/weights/parameters).
  5. Token role (if any): the ALPHA/subnet token is tied to ownership/incentives (including the described distribution of rewards and claimable pool fees).

Quick links: AI thesis fit

Project passport

Field Value
Project name TaoHash
Also known as (aliases) TAOHASH
Logo (logo) ../assets/495_taohash_logo.png
Token symbol (ticker) TAOHASH
Category Infra
Primary chain (chain) Bittensor
Type Appchain
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) active
Token (standard) —
Token contract —
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) PoW mining hashrate pool + incentives
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary ai_score 0 / onchain_score 2 / token_score 1 / evidence_score 0
Last verified 2026-02-11

General project overview

TAOHash (subnet 14) is a subnet in the Bittensor ecosystem focused on the production/aggregation of BTC mining hashrate (PoW) and verifiable distribution of rewards. Validators evaluate miners’ contribution (shares/difficulty → share value) and on this basis set weights that affect emissions and the distribution of the ALPHA/subnet token.

Features/modules

  • Mining pool: miners connect as to a regular mining pool and submit shares.
  • Contribution evaluation: validators compute share value and set weights.
  • Two types of incentives: direct BTC payouts and ALPHA/subnet token rewards (per the subnet description).

Typical scenarios

  • Scenario 1: a miner connects equipment/hashrate → receives BTC rewards and (for subnet participants) ALPHA rewards.
  • Scenario 2: a validator verifies shares and calculates share value → sets weights that affect emissions.

Getting started (wallet/network)

  • What you need: a wallet/account (if required by the product) and access to the Bittensor ecosystem.
  • Network/chain: Bittensor.
  • Fees: — (depend on operations/infrastructure).

Architecture/tech (non‑AI)

  • Components: subnet mining pool, miners (share submissions), validators (weights), share value accounting infrastructure.
  • Participant roles: miners, validators, holders of the ALPHA/subnet token.
  • Where logic runs: share accounting/evaluation — offchain at the validators/pool; weights/emissions and incentives — via Bittensor.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: the ALPHA/subnet token reflects ownership/incentives (including the reward mechanics and (per the description) claimable pool fees).
  • Protocol necessity drivers: described in the subnet’s Tier‑1 documentation and repository (see Evidence).
  • Who pays fees: —.
  • Where fees go: —.
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: —.

Project status and timeline

  • Current status: active.
  • Key releases/milestones: —.
  • Roadmap: see links_* (as navigation).

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: subnet statistics/state are available via taostats (see links_* / Evidence).

AI component of the project

  • What is real AI here? Per Tier‑1 sources, TAOHash is described as a PoW/mining subnet; an AI component is not claimed as the core of the protocol.
  • What is truly onchain? The onchain state of the subnet on the Bittensor network (subnet id 14; see Evidence).
  • Why is a token needed? The ALPHA/subnet token is used as ownership/an incentive (including the reward mechanics and (per the description) claimable pool fees) — see Evidence.
  • Red flags (based on the information found): mixing the “AI” label with infrastructure PoW mechanics without Tier‑1 confirmation of an AI component.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality no Tier‑1 data 0
Onchain necessity medium 2
Token necessity medium 1
Evidence Tier‑1 present 0
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): Per Tier‑1 sources, the project is described as a PoW/mining subnet; AI intentions are not claimed as a separate block.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without Tier‑1 statements about AI intentions we set 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): An AI component as the core of the protocol is not described in TAOHash’s Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a specific Tier‑1 description of the AI feature we set 0.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): AI demos/examples are not applicable (the AI feature is not established).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a Tier‑1 demo/guide we do not raise the flag.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): AI quality metrics are not applicable (the AI feature is not established).
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): A tech description of the AI architecture is not applicable (the AI feature is not established).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a tech description/architecture per Tier‑1 we set 0.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Bittensor
  • Addresses/identifiers: subnet id 14
  • Evidence: Tier‑1 — https://learnbittensor.org/subnets/14
  • Why sufficient / why not (one line): The Tier‑1 source records subnet id 14 and the identity of the subnet.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: the subnet’s incentive mechanics: weights from validators by share value, emissions/ALPHA rewards.
  • Evidence: Tier‑1 — https://raw.githubusercontent.com/latent-to/taohash/main/README.md ; https://learnbittensor.org/subnets/14
  • Why sufficient / why not (one line): Tier‑1 describes how validation/weights and rewards are structured at the subnet level.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established (no Tier‑1 justification of criticality).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a Tier‑1 argument “why without onchain the rationale breaks down” we set 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The subnet uses the ALPHA/subnet token as part of the reward/ownership mechanics.
  • Evidence: Tier‑1 — https://raw.githubusercontent.com/latent-to/taohash/main/README.md ; https://learnbittensor.org/subnets/14
  • Why sufficient / why not (one line): Tier‑1 sources describe ALPHA rewards and ownership/claimable fees.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): No Tier‑1 confirmation that the token is used to pay for the service was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without tech docs/terms of use per Tier‑1 we set 0.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): Miners/participants receive ALPHA rewards (an additional incentive on top of BTC), and holders are described as owners of the pool/a share of fees.
  • Evidence: Tier‑1 — https://raw.githubusercontent.com/latent-to/taohash/main/README.md ; https://learnbittensor.org/subnets/14
  • Why sufficient / why not (one line): Tier‑1 sources describe the reward mechanics via ALPHA.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): No Tier‑1 confirmation of governance via the token was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a described governance process per Tier‑1 we set 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): Tier‑1 does not provide a strict analysis of the replaceability of the ALPHA/subnet token with alternatives.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Tier‑1 materials on the utility/mechanics are needed to assess replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://raw.githubusercontent.com/latent-to/taohash/main/README.md The purpose of the subnet (PoW hashrate), incentive design, reward mechanics (BTC + ALPHA).
Tier‑1 https://learnbittensor.org/subnets/14 The identity and parameters of subnet 14, a description of the ALPHA/ownership mechanics and reward logic.
Tier‑1 — No Tier‑1 source for claim “AI component/AI demo/AI metrics as the core of the protocol” was found.
Tier‑2 https://taostats.io/subnets/14/chart Dashboard of the subnet’s state/statistics (context).
Tier‑2 https://www.coingecko.com/en/coins/taohash Token profile (for reference; navigation).

No comments to display

Back to top