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

# Verify ownership (prove control)

> Why you sign a message, what it says, and how to finish a pending wallet.

To put a wallet on a [statement](https://help.bitcoincontrolcenter.com/statements/statements-and-hoseki-verified.md), you prove you control it. You do this by signing a short message with your wallet.

> [!NOTE]
>
> Signing a message **cannot move funds**. It is not a transaction. Nothing is broadcast to the Bitcoin network.

## Why verify

| | Pending wallet | Verified wallet |
| - | - | - |
| Balance tracked | Yes | Yes |
| Shown on Home and Portfolio | Yes | Yes |
| Can go on a statement | No | Yes |

Only want to track a wallet? You can leave it pending.

## What you sign

The message looks like this:

```text theme={null}
I, the owner, affirm sole control of this account. No other third-party claims/access permitted. Ownership revocable solely by me. ID=…
```

The `ID` is unique to your account. You sign with the wallet's **first receive address** (path ending `/0/0`).

## How to sign

You sign right after adding a wallet. To finish later, open the **pending** account and select **Continue**.

![Pending account page titled Continue Verification? with Abandon and Continue buttons](https://mintcdn.com/hoseki-corp/UfUbkRUza9CJFqpH/images/accounts-pending-continue.png?fit=max\&auto=format\&n=UfUbkRUza9CJFqpH\&q=85\&s=935b7bd8d54ea9427613db416df92921)

A pending account. Select Continue to sign.

**Ledger and Trezor**

1. Select **Prove Control**.
2. Check the message and address on your device. Approve it.

![Hardware wallet signing prompt for proof of control](https://mintcdn.com/hoseki-corp/XCQqCRepRDP5H4K0/images/statements-signing.png?fit=max\&auto=format\&n=XCQqCRepRDP5H4K0\&q=85\&s=3afa100933de050e790116f81b1591fc)

Sign on your device.

**COLDCARD (MicroSD)**

1. Select **Download** to save `hoseki-ownership-claim.txt`. Copy it to your MicroSD card. Do not edit it.
2. On the COLDCARD, go to **Advanced/Tools** → **File Management** → **Sign Text File**. Pick the file. Press Enter.
3. Upload the new `hoseki-ownership-claim-signed.txt`. Select **Prove Control**.

**COLDCARD Q and Keystone**

1. Scan the QR code on screen with your device.
2. Confirm and sign on the device.
3. Select **Ready to Scan**. Hold the signed QR up to your webcam.

**xpub or descriptor**

1. Copy the **Address** and **Message**.
2. Sign it in your wallet software (Sparrow, Electrum, Bitcoin Core, or similar).
3. Paste the signature. Select **Verify**.

![Manual signing screen with Address, Message, and Signature fields](https://mintcdn.com/hoseki-corp/UfUbkRUza9CJFqpH/images/accounts-xpub-signing.png?fit=max\&auto=format\&n=UfUbkRUza9CJFqpH\&q=85\&s=6b1426e7c847f82bfad4fa432e4153aa)

Sign with any wallet tool and paste the result.

When it works, you see **Claim Verified!** Choose **Generate Statement**, **Connect Another Account**, or **Back to Home**.

## Good to know

* **Verification does not expire.** You sign once per wallet.
* **The message says "the owner".** It does not include your name. Your name on statements comes from [Settings](https://help.bitcoincontrolcenter.com/settings/app-settings.md).
* **Multisig** needs a signature from enough keys to meet your quorum. See [Multisig](https://help.bitcoincontrolcenter.com/accounts/multisig.md).
* **Stuck waiting for the device?** After 20 seconds, a link appears to reset the step.

## If signing fails

| Message | Fix |
| - | - |
| **Invalid signature** | Sign the exact message shown, with the exact address shown. Don't add spaces or line breaks. |
| **Signing address does not match the account key** | You signed with a different address or wallet. Use the address shown. |
| **File not downloaded or copied** | Download or copy the message file before you select **Next**. |
| **The signing process did not complete successfully** (COLDCARD) | Upload the file ending `-signed.txt`, not the original. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.