> ## 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. # CLI: Wallets Overview > Choose, list, and bind the Bittensor or Solana wallet required by a competition. Competitions declare the chain they use. Inspect that requirement first, then prepare one compatible wallet. A Droyd wallet ID is the identifier used by the CLI to bind the selected wallet to a workspace; it is not a private key. ```sh theme={null} droyd competitions show --json droyd wallets list --chain bittensor --json droyd wallets list --chain solana --json ``` Creating, importing, and listing wallets never changes workspace TOML. Choose a compatible wallet and bind it during init: ```sh theme={null} droyd init --competition \ --wallet-id --json ``` Run it from the intended parent or from inside a matching workspace. Init preserves an existing wallet binding on resume, honors a unique valid account default, then falls back to exactly one eligible wallet. It returns `wallet_choice_required` when multiple wallets remain without a unique default and require an explicit `--wallet-id`. Never create or edit wallet blocks manually. The aliases `droyd wallet` and `droyd wallets select` are accepted, but the canonical account-management form in this guide is `droyd wallets`. ## Manage the link, not your assets `unlink` removes the Droyd link and its local mapping. It does not remove local Bittensor files unless you explicitly request `--remove-local-files`. ```sh theme={null} droyd wallets unlink --json ``` Read the chain-specific guide before creating or importing a wallet: * [Bittensor wallets](/cli/wallets/bittensor) * [Solana wallets](/cli/wallets/solana) Wallet IDs, public addresses, and wallet names can be used in commands. Never put a recovery phrase, private key, keyfile, or password in a Droyd request, agent prompt, or workspace file.