Development of a bot for working with accounts and interacting with web services.

We are working with a specific website, we have a large database of accounts, and currently, there is a need to create a bot for automatic account verification. Interaction with gmail.com email for receiving verification emails, interaction with the Solflare cryptocurrency wallet for the Google Chrome browser, and the ability to work through a list of socks5/http(s) proxies.
In fact, we need two separate scripts for different stages of work conditionally called "preparation" and "main process"
  Please propose solutions to the tasks described below, also provide your price and the tools you will use to join the project.


Basic description of actions that are currently performed manually and need to be automated:

First stage/Script ("preparation") -  take the login:password from the account database in the file logins.txt --> log in to the website --> open the developer panel and change some data in the page code --> enter the address of one of several emails from the list in another file mails.txt --> save using the button on the website --> log out of the account --> repeat these actions for all accounts in the database --> save processed accounts in a new file wait.txt with a label in the format "login:password - wait".

At this stage, there may be issues such as:
- invalid account (incorrect login or password)
- error during saving the new email (in this case, the next one from the list in the file mails.txt  should be used; if the error appears again, take the next email and so on until all emails from the list have been tried; if after the last attempt the error appears again, mark such an account in the output file, for example, with the symbol " - ")
The bot must correctly handle these two issues and mark accounts that could not be processed in a new results file wait.txt


Second stage/Script ("main process")

The account database consists of accounts in the format login:password registered with an old email.
Our goal is to change the email, verify it, create a new wallet, connect the new wallet, verify it, and save the account with the new data in a separate text document output.txt, in the following format (four lines):
login:password
solflare
(seed phrase from the new wallet)
(address of this wallet)

Here is how the process currently done manually looks like:

1. Take the login password from the account from the file with the account database in the format login:password

2.  Log in to the website

3. Take the email from the list of emails in the file new_mails.txt (emails generated by the icloud service, all of them are redirected to the main gmail email from which the bot must open all emails)

3. Enter the new email and old password in the profile on the website (the process of requesting an email change)

4. Wait and follow the link in the email that arrives.

5. After verifying the email, create a new Solflare wallet and connect it to the profile on the website. (the ability to connect the wallet appears only after verifying the email)

6. Log out of the account and immediately log in again and connect the same wallet again, and click the wallet verification button (this procedure is necessary because there is a bug on the site, the email arrives only if you log in again)

7. Wait for the wallet verification email, follow the link in the email.

8. Check the profile (verified email ✅, verified wallet ✅)

9. Save the account in a new file output.txt in the following format (four lines):

login:password

solflare 

(seed phrase from the wallet)
(wallet address)
IMPORTANT: THE LOGIN MUST CONTAIN THE INITIAL VALUE FROM THE ACCOUNT DATABASE FILE, AND THE NEW VALUE - THE EMAIL ADDED TO IT, SEPARATED BY THE SYMBOL " / "

At this stage, there may be issues such as:

- login password may be invalid
- the email change button may not be active 

- the email may already be verified

- the wallet may already be linked

- the email may not be verified, but the wallet is already linked

- both the email and wallet may already be verified

- the email verification or wallet verification email may arrive with a delay (the email contains the account nickname, which may help with processing the emails)
Any of these issues will prevent the correct processing of the account and must be noted in the final file output.txt to understand at which stage the problem occurred.


If this brief is not sufficient, we will describe in more detail in the messenger from Durov:  panantren