User Guide - Getting Started

Getting Started Guide

• The software comes with a default limit of 2 active sessions. If you need additional sessions for your workflow, they can be purchased separately. This allows you to scale your operations based on your needs.

• To properly close the session, use the key combination Ctrl + C

• After pressing Ctrl + C, you will see a successful exit log message

• If the session is closed improperly, it will automatically deactivate within 2 minutes

Operation System Support

• Windows and Linux platforms are supported by the software

• For stable operation of a large number of accounts, it is recommended to use a Linux server

Available Modules

Login to accounts

• This module is required for automatic account creation or logging into an account

• The software automatically links the wallet and verifies the email

• After login, the session is saved to the database for future use

Farm

• A specialized module designed for continuous and uninterrupted node farming

• Automatically sends ping requests and performs health checks, mirroring the functionality of the official extension

• Utilizes a combined approach of multiprocessing and async I/O tasks for optimal network performance

• Performance is controlled by cpu_thread_count setting instead of regular threads

• Can efficiently process large numbers of nodes (tested with 10k nodes in ~5 minutes with proper server capacity)

• Requires adequate server bandwidth (1-5 Gbps recommended) for handling large node counts (>5000)

• Some request errors are expected when processing large numbers of nodes

Note: The farming module uses CPU logical processors for task processing. To determine the optimal cpu_thread_count setting:

1. Check your CPU's specifications:

   • Find the total number of logical processors (threads) your CPU has

   • For example: Ryzen 5 3600x has 6 cores and 12 logical processors

2. Calculate the safe setting:

   • Subtract 1 from your total logical processors

   • This reserves one processor for system operations

   • Example: 12 logical processors - 1 = 11 maximum safe setting

3. Set your cpu_thread_count:

   • Choose a number between 1 and your maximum safe setting

   • Example: If you have 12 logical processors, set between 1-11

   • Higher numbers will process more nodes simultaneously, but require more system resources

Export stats

• Module exports detailed account statistics into a single consolidated report: accounts_stats.csv

• The report includes comprehensive account information in the following structure:

  • Email - Account email address

  • Password - Email password

  • Wallet Address - Connected wallet address

  • Unique Identification Code - Account's unique identifier

  • Nickname - Account username

  • Referral URL - Personal referral link

  • Total Referrals - Number of successful referrals

  • Node Total Running Time - Cumulative runtime of node

• If data export fails for an account, the report marks all fields except Email and Password as "Failed"

• Results are automatically saved in the ./results/stats/ directory

Proxy Specifications

The software has an automatic proxy change system. For example, you can load 10,000 proxies for 100 accounts and if one of the proxies stops working, the software will automatically take another one.

Supported Proxy Types

The software supports the following proxy types:

• SOCKS5

• HTTP

Attentation: Login accounts module support only HTTP format.

Recommended Proxy Types for Farming

For optimal farming performance, recommend using:

1. ISP Proxies (Highest Priority)

2. Residential Proxies (Second Best Option)

The cleaner the IP addresses, the lower the chance of being banned by project in future.

Proxy Quality Assessment

You can check the quality of your proxies at scamalytics.com/ip

Quality Score Interpretation:

• 0: Ideal score (Best for farming)

• 100: Worst score

Configuration File Formats

proxies.txt

1. Navigate to the file proxies.txt (config > data)

2. Add proxies in one of the following formats:

http://user:pass@ip:port
http://ip:port:user:pass
http://ip:port@user:pass
socks5://user:pass@ip:port
socks5://ip:port:user:pass
socks5://ip:port@user:pass

login_accounts.txt

1. Navigate to the file login_accounts.txt (config > data)

2. Add accounts in the following format:

email:email_password:pk_or_mnemonic

Note:

• Your email accounts must have IMAP access enabled

• pk_or_mnemonic mean EVM wallet private key or mnemonic

• For some email providers, you'll need to use an app-specific password instead of your regular account password:

  • Gmail - Requires an app password (2FA must be enabled)

  • Yahoo - Requires an app password (2FA must be enabled)

  • iCloud - Requires an app-specific password

  • Outlook - May require an app password if 2FA is enabled

• How to check if IMAP is enabled:

  • Gmail: Settings > See all settings > Forwarding and POP/IMAP > Enable IMAP

  • Yahoo: Settings > More Settings > Security > Allow apps that use less secure sign in

  • Other providers: Check your email provider's settings for IMAP configuration

farm_accounts.txt

1. Navigate to the file farm_accounts.txt (config > data)

2. Add accounts in the following format:

email

export_stats_accounts.txt

1. Navigate to the file export_stats_accounts.txt (config > data)

2. Add accounts in the following format:

email

referral_code.txt

1. Navigate to the file referrals_codes.txt (config > data)

2. Add codes in the following format (URL or code):

https://www.app.multiple.cc/#/signup?inviteCode=jKoHN4qC
jKoHN4qC

Settings.yaml Configuration

Main Settings

• LICENSE_KEY: ""

  • The license key you received after purchase

Threading and Database Settings

• threads: 10

  • Controls the number of concurrent operations

  • Higher values increase processing speed but require more system resources

• cpu_thread_count: 2

  • Controls CPU threads for farm module (0 = maximum available threads)

• shuffle_accounts: true

  • When enabled, processes accounts in random order

  • Helps distribute load and avoid pattern detection

• database_url: "sqlite://./database.sqlite3"

  • Database connection string (postgres/sqlite)

  • Uses SQLite as the default database system

  • Format for postgres: postgres://user:pass@host/db_name

Retry and Error Handling

• error_delay: 1

  • Waiting time in seconds before retrying a failed operation

• max_login_attempts: 3

  • Maximum number of login attempts per account

• max_stats_attempts: 3

  • Maximum attempts to retrieve statistics

• max_proxy_change_attempts: 2

  • Maximum attempts to switch to a different proxy

IMAP Settings

• use_proxy_for_imap: true

  • Controls proxy usage for IMAP connections

• skip_logged_accounts: true

  • When enabled, skips processing of already logged accounts

Single IMAP Configuration

• use_single_imap:

  • enable: false

  • imap_server: "imap.gmx.net"

Mail Redirect Configuration

• redirect_settings:

  • enable: false

  • email: ""

  • password: ""

  • imap_server: "imap.gmail.com"

Startup Settings

• delay_before_start:

  • min: 0, max: 0

  • Random delay range (in seconds) before starting operations

IMAP Server Configuration

Supported email providers and their IMAP servers:

• Global Email Services:

  • gmail.com: imap.gmail.com (SSL required)

  • yahoo.com: imap.mail.yahoo.com (SSL required)

  • icloud.com: imap.mail.me.com (2FA may be required)

• CIS Region Services:

  • mail.ru: imap.mail.ru

  • rambler.ru: imap.rambler.ru

• European Email Services:

  • gmx.com: imap.gmx.com

  • gmx.net: imap.gmx.net

  • gmx.de: imap.gmx.net

• Polish Email Services:

  • onet.pl: imap.poczta.onet.pl

  • onet.com.pl: imap.poczta.onet.pl

  • op.pl: imap.poczta.onet.pl

Note: You can add additional email providers and their IMAP servers by following the format:

imap_settings:
  domain.com: imap.domain.com