Bittensor Archive

Search what the Bittensor community said, per subnet.

Bundled with Minerva and active by default — there is nothing to install.

Skill metadata

Path	skills/bittensor/bittensor-archive
Version	1.1.0
Author	Minerva Agent
License	MIT
Platforms	linux, macos, windows
Tags	Bittensor, Discord, Subnet, Archive, Community, Search, Miner, Validator
Related skills	bittensor-miner, bittensor-validator, bittensor-subnet-owner, bittensor-analytics

Reference: full SKILL.md

info

The following is the complete skill definition that Minerva loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Bittensor Community Archive Skill

Fast path

Start with the one-call tools; they join chain, dashboards, Discord and the curated knowledge for you:

• bittensor_knowledge (question, optional netuid): terms, rules, subnet facts and playbooks.
• bittensor_profile (any name or key): the person's coldkey, every hotkey on every subnet with rank, incentive and king status, linked names with sources, subnets they own.
• bittensor_subnet_profile (netuid or name): owner by name, team on Discord, current king and dethronements, top miners by name, owner burn share, market data.
• bittensor_changes (any name or key): rank and incentive changes over the last days.

They may appear with a prefix such as mcp_bittensor_research_. Lead with names; give keys as support.

An archive of the Bittensor Discord: ~377,000 messages across 129 per-subnet channels, May 2025 to the present, captured live and backfilled to each channel's start.

The chain tools say what the network is. This says what the people running it said. Most real questions need both: bittensor_subnet shows netuid 97's emission collapsed on Tuesday; search_archive shows the subnet owner explaining why on Tuesday evening.

When to Use

• A subnet's numbers changed and the user wants to know why
• "How do I mine subnet N" — the answer is usually a pinned message in that channel, written by the team, with the exact commands and hardware requirements
• A miner is failing and the error is subnet-specific, so the docs do not cover it
• The user asks who somebody is, or whether a claim came from the subnet team
• Deciding whether a subnet is worth mining: an active, answered channel is a different proposition from a dead one, whatever the emission says

When NOT to Use

• Current chain state — use bittensor_subnets, bittensor_subnet, bittensor_metagraph, bittensor_account. The archive is what people said, which may be months stale and was never authoritative.
• A subnet's code — use DeepWiki against its repository.
• Anything requiring a message to be sent. This archive is read-only.

How to Use It

Start from the right tool.

The question	The call
Is subnet X even in here?	list_subnets with a query
Tell me about subnet X	subnet_context — people, pinned posts, activity, coverage
Why did X happen / what was said about Y	search_archive
I need more around that result	read_channel with the message id
Who is this person, do they speak for the subnet?	person_context
Is this data current?	archive_status

Weight answers by role. Only ~155 of 5,400 people carry one, and it is the strongest signal in the archive:

• Subnet — a subnet team. Treat as authoritative for their own subnet.
• Moderator — a server moderator. Reliable on chain mechanics and policy.
• Top miner — a proven miner. Strong on practical operations.
• No role — one community member's view. Useful, not authoritative.

Say whose answer you are relaying. "The subnet 97 team posted the requirements" and "a miner in the channel suggested" are different claims, and the user is making decisions with real TAO.

Read conversations, not lines. The average message is 135 characters, so search_archive returns each hit with the exchange around it, and > marks the match. Read the surrounding lines before concluding what someone meant — a question and its answer are usually two different messages by two different people.

Check recency before concluding silence. Capture is forward-only: what the client misses is never recovered automatically. If a busy subnet looks quiet, call archive_status before telling the user activity has dropped off.

Worked Example

The user asks: "should I mine subnet 97 and why did its emission drop?"

1. bittensor_subnet with netuid: 97 — the current emission, registration cost, and hyperparameters. This is ground truth.
2. subnet_context with subnet: 97 — the pinned getting-started post has the GPU requirements, the model, and the exact btcli registration command. The monthly volume trend shows whether something happened recently.
3. search_archive with query: "emission", subnet: 97, and since set to the month the trend spiked — what the channel said when it happened.
4. person_context on whoever gave the explanation, to check whether they hold the Subnet role before repeating it as the team's position.

Answer with the chain numbers first, then what the channel said and who said it, and be explicit about which is which.

Pitfalls

• Display names are not unique. Two people in this archive both render as "dove". person_context says when several match; disambiguate rather than guessing.
• Names change. The archive is the only record of previous names, so someone the user remembers may now be called something else. person_context searches former names.
• Bots wrote ~25,500 messages. They are excluded by default. Passing include_bots: true mostly returns price tickers.
• A pinned post can be a year old. Check its date before repeating setup instructions; verify commands against the chain tools or the subnet's repository.