← Back to the ecosystem

Bittensor

Bittensor.com is the official hub for the Bittensor SDK, CLI, documentation, and curated third-party wallets and explorers, giving developers and users one reliable, always-current reference point.

Bittensor homepage

Official portal bringing together the SDK, the CLI, the technical documentation, and verified third-party resources for anyone already using Bittensor day to day.

What is it for?

Before a single portal existed, anyone operating on Bittensor had to rely on scattered GitHub repositories, outdated documentation, and informal lists of wallets or explorers shared on Discord or Twitter.

This scenario increased the risk of installing the wrong SDK version, following outdated guides, or ending up on a third-party tool with no security guarantees.

The migration from SDK v9/v10 to v11 made this problem even more obvious, with users mixing old and new instructions without knowing which to follow.

Bittensor.com solves this problem by centralizing everything under a single, officially authoritative domain.

Instead of searching across multiple sources, users know that the documentation, the Python package, the CLI, and the wallet and explorer lists shown there always reflect the current state of the chain.

How does it work?

The site is organized into six main sections, accessible directly from the main navigation: About, Whitepaper, Docs, Discord, Wallet, and Explore.

The Docs section is the technical core of the site.

It includes a quick-start guide, a dedicated SDK page, a section specifically for automated agents, CLI reference, and a detailed version migration guide.

Reference pages, such as Transactions, Queries, Errors, and Hyperparameters, are generated automatically from the SDK’s own code, which guarantees they never fall out of sync with the chain.

Beyond human-readable content, the site also provides the same content in structured formats, through files such as /llms.txt, /llms-full.txt and JSON catalogs listing all available transactions and queries, allowing AI agents to consult the documentation without relying on scraping.

The Wallet section presents a curated list of compatible wallets, split between everyday options, such as browser extensions and mobile apps, and cold storage options, such as hardware devices and offline signing.

The Explore section follows the same approach for blockchain explorers and learning resources, always making clear that these are third-party tools, not audited or controlled by the Bittensor team.

Features

  • Unified installation of the Python SDK and the btcli CLI through a single command, with support for Python 3.10 through 3.14.
  • Reference documentation generated directly from the source code, covering transactions, queries, error codes, and network hyperparameters.
  • A curated wallets page, with options for everyday use and for cold storage, each with clear indication of supported platforms.
  • A curated explorers and learning resources page, always distinguishing between official content and third-party content.
  • SDK version migration guide and releases page, useful for anyone maintaining their own integrations with the chain.

Role in the ecosystem

Bittensor.com functions as the ecosystem’s neutral reference point, without competing commercially with any of the tools it recommends.

Rather than building its own explorer, wallet, or dashboard, the site directs traffic to solutions already maintained by independent teams, keeping for itself only the role of keeping the SDK, the CLI, and the documentation always aligned with the current state of the chain.

This role reduces ecosystem fragmentation and gives any new project or tool a clear path to gaining visibility among those already active on the network.

How to get started?

  1. Go to the Docs section and follow the quick-start guide to install the bittensor package and the btcli CLI.
  2. Choose a wallet on the Wallet page, depending on whether you prefer a browser extension, a mobile app, or a cold storage solution.
  3. Connect the wallet to the network and confirm you’re using the latest SDK version, especially if you’re coming from an integration prior to v11.
  4. Check the Explore page to choose a blockchain explorer or an additional learning resource, depending on your needs.
  5. Bookmark the releases page to keep track of future updates to the CLI and the SDK.

Follow Bittensor Discord X