THOR (SN112): What Holding It Means

THOR is the token associated with Bittensor Subnet 112 (SN112), a project developing open robotics infrastructure. Its first planned use case is a marketplace for commissioning robotics training data, beginning with expert video annotation. A buyer sets the task and acceptance criteria; qualified contributors create annotations, while THOR coordinates verification and delivery.

The initial pilot is designed for professional annotation firms. Permissionless annotation is planned after beta, so you should not assume that the marketplace is already open to everyone. The project’s longer-term direction is to connect data, models and hardware for robotics research and deployment, but that does not establish what the SN112 token can currently be used for.

If you are considering holding THOR, separate the project’s goals from the token’s confirmed role. The token is linked to SN112, but THOR has not published a specific holder utility in the information described here. Do not assume that owning it grants marketplace access, voting rights, revenue, or a claim on the project.

THOR is an AI- and robotics-related token tied to Bittensor Subnet 112, not the RUNE token used by THORChain. Similar names can lead to costly mistakes, so check the exact symbol, subnet and receiving network before you acquire or transfer anything.

For the token itself, the project has not published a specific use such as paying marketplace fees, staking, governance, or sharing revenue. The robotics data marketplace is the project’s stated product direction; it should not be treated as proof that the token is required to use that marketplace. Confirm any token function against current official project materials before relying on it.

This distinction matters if you are buying THOR for a particular purpose. A project can build useful software without giving its token a defined role, and a proposed future use is not the same as a live feature. Avoid sending funds based only on a ticker search or a claim that the token automatically provides access to robotics services.

SN112 identifies THOR with a Bittensor subnet. The token facts do not identify separate issued chains, so do not assume THOR is an Ethereum, Solana or THORChain asset. Its network and transfer format should be confirmed from an official THOR or Bittensor source before you deposit or withdraw it.

Use only a wallet that explicitly supports the correct Bittensor network and the SN112 token. A wallet that can display another asset named THOR may not support this one. Before sending a meaningful amount, verify the receiving address and network, check that the wallet can display and transfer the token, and consider a small test transfer if the network supports one.

If an exchange or wallet lists “THOR,” compare the subnet identifier and network details rather than relying on the name alone. Never send it to an address for another chain just because the address looks familiar. Transfers to an incompatible network may be difficult or impossible to recover.

THOR’s reported circulating and total supply are both about 2.86 million SN112, with a stated maximum supply of 21 million. These figures are based on data dated November 8, 2026, and token supply can change. The maximum is not the same as the amount currently circulating.

A maximum supply figure alone does not tell you when or how additional tokens may be issued, distributed, or unlocked. THOR has not published an issuance schedule in the project details described here, so check current token information before making assumptions about future supply. Also confirm that a wallet or market listing refers to Bittensor SN112 rather than another token with a similar name.

If you track the token’s value, remember that market prices and liquidity can move quickly. A quoted price is not a guaranteed sale price, and a market value estimate does not mean you can sell your full balance at that level.

Store THOR only in a wallet that supports its exact network and subnet token. Keep your recovery phrase offline, never share it with anyone, and avoid entering it into websites or forms that claim to verify, unlock, or migrate your tokens. If you use a hardware wallet, first confirm that it supports the relevant Bittensor asset and transaction type; hardware storage cannot protect you from signing a malicious transaction.

The main risks include uncertainty about the token’s current utility, the project’s early-stage marketplace plans, and the possibility that the product may not reach its intended adoption. Token prices and trading liquidity can also change sharply. Network, wallet and address errors can lead to permanent loss, while fake tokens and impersonation attempts can exploit the THOR name.

Before transferring, verify the network, token and destination through trusted project channels. Do not rely on unsolicited messages or promises of guaranteed returns, and keep only the amount you can afford to lose exposed to these risks.