Skip to main content

​
Diagnostics and creation

doctor bittensor is read-only. It checks the selected Bittensor launcher, supported version, matching wallet runtime, wallet root, and managed credential bindings. It always returns a structured readiness result:
  • ok: true, status: "ready": Bittensor-dependent commands can proceed.
  • ok: false, status: "setup_required": run the non-null recommended_action.command, then rerun doctor.
  • ok: false, status: "credential_rebind_required": use the recommended creation-bound launcher, or ask the user when no unambiguous command exists.
Creating a Bittensor wallet can use --hotkey, --path, and --btcli; creating a Solana wallet uses the hosted wallet flow and cannot use those Bittensor options.

​
Import and list

import links an existing local Bittensor wallet folder and performs the ownership proof. It requires --folderpath; choose a hotkey when the folder contains more than one. --local lists only the CLI’s local Bittensor mappings.
Create, import, and list are account-level and never write workflow TOML. A new workspace receives its first binding through init --wallet-id. use requires an existing droyd.workflow.toml at the exact workspace, then writes its default after confirming the competition and wallet chain. It refuses replacement unless --replace-workflow-wallet is supplied. For an encrypted externally managed Bittensor wallet, --wallet-password-env-var records only the environment variable name. use has the alias select; the wallets namespace has the alias wallet. unlink removes the Droyd link and local mapping; add --remove-local-files only when you deliberately want the mapped local Bittensor files removed. See Wallets Overview for the safe workflow.