> For the complete documentation index, see [llms.txt](https://nfd-gg.gitbook.io/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nfd-gg.gitbook.io/main/eng-combine-software/modules/operation-and-launching-of-modules/zora-module/wallet-manager.md).

# Wallet Manager

### Adding wallets to the module:

* First, you need to set up accounts in [**Account Manager**](https://docs.nfd.gg/main/eng-combine-software/account-manager), link wallets to them, and optionally, add proxies;
* Click **Add More Wallets**;
* Select the wallets to be added to the module. Please note that if you purchased a plan for 50 accounts, you can only replace 3 wallets after adding these 50 accounts to the Wallet Manager. Therefore, add wallets carefully;
* Click **Add to Zora**, and the selected wallets will be added to the module.

<figure><img src="/files/DVxh3ydcTi1h9QTiI8bw" alt=""><figcaption><p>Adding wallets to the module.</p></figcaption></figure>

***

### **UI Touch:**

**UI Touch** is a standard interaction with any website through its interface. Any website consists of two components: the front end (interface) and the back end, which contains the site's logic and processes all interactions.

In web3 protocols, pressing a certain button triggers a contract call. That is, pressing the button in the interface triggers the contract call, and then your Metamask opens for you to sign the transaction.

How any software works: it bypasses the interface and directly accesses the contract behind the button, sending all necessary information for the transaction directly to the contract.

The interface of web3 protocol websites serves one purpose - to simplify blockchain interactions for ordinary users, but working directly with contracts is not prohibited. This can even be done manually through Etherscan.

However, sooner or later, projects will start fighting against Sybil activity. One way could be placing appropriate analytics on their websites to collect information about the IP address and browser fingerprint from which the button was pressed to trigger the contract and make the transaction.

The **UI Touch** function in Combine allows you to interact with official bridges or any other protocols without leaving Combine. It is important to understand that for your interaction to be considered legitimate, you need to open the site through **UI Touch** and perform the transaction manually through this window.

* Click on the **UI** icon.
* In the **User Agent** field, you can see your fingerprint. The fingerprint is automatically selected from a list of over 10,000 of the most common fingerprints worldwide. The initially generated fingerprint is fixed to the wallet until you click the **Generate New** button.
* In the **Custom User Agent** field, you can insert your user agent from an anti-detect browser or generate it from any other source.
* In the **Choose Target Project** field, select the required protocol and click **Launch**.
* Immediately after this, a browser window will open where you need to connect your wallet and complete the transaction.

<figure><img src="/files/RnzXoiu8A6dP5Mt3nVnx" alt=""><figcaption><p>UI-Touch function.</p></figcaption></figure>

***

### Status and Actions section:

In the **Status** section, you can see the status of a specific wallet during the last session and the date when this wallet was last launched:

* If the date is highlighted in green, the wallet ran without errors.
* If the date is highlighted in red, the wallet encountered an error or was paused.

<figure><img src="/files/zQJVQWilvaSmohHNUjUv" alt=""><figcaption><p>Section Status.</p></figcaption></figure>

* In the Actions section, clicking on the first icon will open a page with statistics for the specific wallet on the DeBank website;
* Clicking on the second icon will open an explorer where you can view transactions for the specific wallet;
* Clicking on the trash icon will remove the selected wallet from the module. Adding new wallets is available within the limit specified in the line "Remaining attempts to change the wallet." Removed wallets can be returned to the module without restrictions.

<figure><img src="/files/MODennSjIuiPPFYgEfTw" alt=""><figcaption><p>Actions section.</p></figcaption></figure>
