> 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/zksync-module/wallet-manager.md).
# Wallet Manager
### Adding wallets to the module:
* First, you need to set up accounts in the [Account Manager](https://docs.nfd.gg/main/eng-combine-software/account-manager), link wallets to them, and, if desired, add proxies;
* Click on **Add More Wallets**;
* Select the wallets to be added to the module. Note that if you purchased a plan for 50 accounts, after adding these 50 accounts to the Wallet Manager, you can only replace 3 wallets. So add wallets carefully;
* Click on **Add to ZkSync**, and the selected wallets will be added to the module.
Adding wallets to the module.
***
### **UI Touch:**
**UI Touch** is a typical interaction with any website through its interface. Any website consists of two components: the front end (interface) and the back end, which contains all the site's logic and handles all interactions.
In web3 protocols, pressing a specific button triggers a contract call, i.e., pressing a button in the interface triggers a contract call, and your Metamask opens, allowing you to sign the transaction.
How any software works: it bypasses the interface, directly accessing the contract behind the button, sending all the necessary information for the transaction directly to the contract.
The interface of web3 protocol sites serves one purpose - to simplify blockchain interactions for regular users, but there is no prohibition against working directly with contracts. This can be done, and it is not necessary to do it through software - you can perform these interactions manually, even through Etherscan.
However, sooner or later, projects will start combating Sybil activity. One way to do this might be to place corresponding analytics on their sites, collecting information about the IP address and browser fingerprint from which the button triggering the contract was clicked and the transaction was executed.
The **UI Touch** function in Combine will allow you to interact with official bridges or any other protocol without leaving Combine. It is important to understand that for your interaction to be considered legitimate, you must 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 enter your User agent from an anti-detect browser or generated elsewhere;
* In the **Choose target project** field, select the desired protocol and click **Launch**;
* Immediately after this, a browser window will open, where you need to connect the wallet and complete the transaction.
UI-Touch function.
***
### Status and Actions section:
In the **Status** section, you can see the status of a specific wallet that it received during the last session and the date when this wallet was last launched:
* If the date is highlighted in **green**, the wallet worked without errors;
* If the date is highlighted in **red**, the wallet encountered an error or was paused.
Section Status.
* In the Actions section, clicking on the first icon will open a page with statistics for the specific wallet on the [DeBank](https://debank.com/) website;
* When you click on the second icon, an explorer will open where you can view transactions for the specific wallet;
* Clicking on the trash can icon will delete the selected wallet from the module. Adding new wallets is available within the limit specified in the **Remaining attempts to change** **the wallet line**. Deleted wallets can be added back to the module without restrictions.
Actions section.
---
# 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://nfd-gg.gitbook.io/main/eng-combine-software/modules/operation-and-launching-of-modules/zksync-module/wallet-manager.md?ask=&goal=
```
`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.