> ## Documentation Index
> Fetch the complete documentation index at: https://docs.droyd.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Bittensor wallet

> Create or link a locally held Bittensor wallet and prove ownership safely.

Bittensor wallets remain under your local custody. Droyd receives public
addresses and a short-lived ownership proof, never a mnemonic, keyfile,
password, or private key.

## Create a new wallet

Check local readiness first:

```bash theme={null}
droyd doctor bittensor --json
```

Doctor does not change your machine. If it returns `ok: false`, run its
non-null `recommended_action.command`, then rerun doctor. A fresh installation
normally recommends:

```bash theme={null}
droyd setup bittensor --managed --json
droyd doctor bittensor --json
```

Continue only after doctor returns `ok: true` and `status: "ready"`, then create
the wallet:

```bash theme={null}
droyd wallets create --chain bittensor --name mining-cold --hotkey default --json
```

Managed setup uses `uv` for the download. It does not replace or interfere with
another `btcli` already installed on your machine. If you intentionally want to
use an existing compatible installation, run
`droyd setup bittensor --btcli /absolute/path/to/btcli --json` instead.

Creation opens a local browser backup page. Save the coldkey and hotkey recovery
phrases plus the generated password somewhere secure, then confirm the page.
Do not share or paste any of that material into Droyd, an agent prompt, or a
workspace file.

## Link an existing wallet

Import the local wallet folder and select the hotkey when it has more than one:

```bash theme={null}
droyd wallets import --chain bittensor --folderpath ~/.bittensor/wallets/mining-cold --hotkey default --json
```

Droyd asks the selected hotkey to sign an ownership challenge locally. Complete
competition registration only when the competition's requirements call for it;
registration cost and eligibility are competition-specific.

Creating or importing a wallet does not write workspace TOML. Bind the approved
wallet when initializing its competition workspace with `droyd init --competition <competition-slug> --wallet-id <wallet-id> --json`. Run from the
intended parent or pass `--parent <directory>`, and use the successful
canonical `workspace_path`.