> For the complete documentation index, see [llms.txt](https://alphabot-docs.gitbook.io/alphabot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alphabot-docs.gitbook.io/alphabot/for-individuals/account-settings/signed-wallets.md).

# Signed Wallets

A user can connect multiple wallets to a single user account in Alphabot. Any of the signed wallets can be connected to log in as that user, and all of the wallets will be checked for NFT holdings when registering for raffles with NFT requirements. A user will need to sign with these wallets to link them to their account. 

When a user links a wallet that is already associated with an Alphabot account, any pending **raffle entries** on that account will be deleted, and any existing **wins** on that account will be transferred to the main account being linked.

<figure><img src="/files/ri2IxUz16GzRCkaI10Il" alt=""><figcaption></figcaption></figure>

## Cold Wallet Delegation

Alphabot supports **WALLET DELEGATION** via <https://warm.xyz/> OR <https://delegate.cash/>.

Vault wallets you have delegated to your hot wallets can now be added to your profile's signed wallets by clicking the shield icon next to the correct wallet address in your [**Profile's Signed Wallets**](https://www.alphabot.app/#profile-signed)&#x20;

This cold wallets will then be checked just like any other signed wallet when you are completing NFT requirements.

<figure><img src="/files/uxyN17idk54g5mnKIozk" alt=""><figcaption><p> Note: this will only work for wallets delegated for all contracts and types, and that do not expire.</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://alphabot-docs.gitbook.io/alphabot/for-individuals/account-settings/signed-wallets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.