# Bittensor Wallet

Connect a wallet from [User > Settings](/user/settings). This proves control of the wallet address with a signed message; it does not send a transaction.

## Before connecting

You need a signed-in Actual account, a Polkadot-compatible browser extension, an exposed wallet account, and a signer that supports raw-message signing.

The current Actual form uses the **first account returned by the extension**. It does not show an account picker. Before connecting, configure the extension's site permissions or exposed accounts so that the intended address is first or is the only account available.

## Connect

1. Open the Bittensor section in Settings and choose **Connect**.
2. Actual reads the extension accounts and requests a challenge for the first account.
3. Check the address in the extension's signature request, then approve the raw-message signature if it is the address you intend to connect.
4. Actual verifies the signature and displays the connected address in shortened form.

Do not approve the request if it names the wrong account. Change the extension's exposed accounts and retry. If you already connected the wrong address, disconnect it before repeating the flow.

## Challenge and ownership rules

Challenges expire after 5 minutes, and challenge requests are limited to 5 per minute. Addresses are normalized to the Bittensor SS58 format.

An Actual account can have one active Bittensor wallet connection, and a wallet address can have only one active Actual account owner. A connection attempt fails if the address is already connected elsewhere.

## Disconnect

Use **Disconnect** in the Bittensor section. This revokes the active connection record for your account. Reconnecting requires a fresh signature challenge.

## Troubleshooting

| Message or symptom | Action |
| --- | --- |
| No compatible extension | Install or enable a Polkadot-compatible extension and allow access for the site. |
| No wallet accounts found | Expose the intended account to the site through the extension. |
| Raw-message signing unsupported | Use an account and signer that can sign the challenge. |
| Challenge expired | Start a fresh connection attempt and sign within 5 minutes. |
| Too many attempts | Wait before requesting another challenge. |
| Wallet already connected to another account | Resolve the existing connection; the same address cannot have two active owners. |
| Wrong account selected | Cancel the signature, change exposed accounts in the extension, and retry. |

See [User](/docs/user) for connected-account and mining settings.