User Guide - Getting Started
Last updated
Last updated
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
Note: if you plan to use the software on Linux, you will need to use the Postgres DB. See the installation guide:
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
Linux supports 1024 file descriptors by default, while Windows supports only 512. On Linux, this value can be increased, but on Windows, it cannot be modified
This module is designed for automatic registration and verification of accounts
If an account is registered but not verified - the software will automatically detect this and complete verification
After registration, the session is saved to the database (refresh, access tokens) and instead of future logins for any actions, the software will simply refresh the access token. This is done because the access token is only valid for 60 minutes
This module is designed for logging into your existing accounts, which must be fully registered and verified. If not, the software will notify you and export the accounts to a separate file so you can process them through the "Register & Verify accounts" module
After login, the session is saved to the database (refresh, access tokens) and instead of future logins for any actions, the software will simply refresh the access token. This is done because the access token is only valid for 60 minutes
A specialized module designed for continuous and uninterrupted node farming
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
Requires adequate server bandwidth (1-5 Gbps recommended) for handling large node counts (>5000)
Farming fully emulates the extension's operation. It communicates 24/7 with the websocket (MQTT broker) and sends all types of messages: shield, task, pingreq, key, latency and others
Windows has a limit of 512 nodes, Linux has 1024 (but this limit can be increased with a command). For stable farming, it's advisable not to exceed these limits
If you decide to farm more than 1024 nodes on a Linux server - calculate cpu_thread_count so that there are no more than 1000 nodes per logical processor. But keep in mind that with more than 1000 nodes, farming will be unstable and you will receive less uptime and points
1 process is always allocated for checking node status. This means if you set 2 cpu_thread_count, 3 will be used: 2 for farming nodes and 1 for verification. Take this into account!!!!!
Note: The farming module uses CPU logical processors for task processing. To determine the optimal cpu_thread_count setting:
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
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
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
A tool for expanding your node network through additional node generation
There are no limits, you can generate as many nodes as you consider necessary. But keep in mind that, for example, 100 nodes would already look a bit suspicious, and it's unlikely that an average user could farm that many
The software automatically monitors this limit and gracefully terminates the process when reached, providing clear feedback through logs
You can configure generation parameters using nodes_config in settings.yaml
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
UID - accounts local ID
Referral code - Personal referral code
Total referrals - Total number of referrals
Total Points - Total number of points
Daily Points - Number of points per day (from 00.00 UTC to 00.00 UTC)
Total Nodes - Total number of nodes
Active Nodes - Number of active nodes
Discord Connected
Twitter Connected
Discord Username
Twitter Username
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
Efficient module for automatic Discord account linking to your Gradient account
Requires only the Discord authorization token for quick setup
Efficient module for automatic Twitter account linking to your Gradient account
Requires only the Twitter authorization token for quick setup
This module is designed for quickly clearing all active accounts proxies. This can be useful if you want to completely replace all old proxies and use a new pool.
Each account has a unique proxy and will continue using it until an error.
This module is designed for quickly clearing all active nodes proxies. This can be useful if you want to completely replace all old proxies and use a new pool.
Each node has a unique proxy and will continue using it until an error.
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.
The software supports the following proxy types:
SOCKS5
HTTP
Attentation: Login accounts module support only HTTP format.
For optimal farming performance, recommend using:
ISP Proxies (Highest Priority)
Residential Proxies (Second Best Option)
The cleaner the IP addresses, the lower the chance of being banned by project in future.
You can check the quality of your proxies at scamalytics.com/ip
Quality Score Interpretation:
0: Ideal score (Best for farming)
100: Worst score
Navigate to the file proxies.txt (config > data)
Add proxies in one of the following formats:
Navigate to the file register_accounts.txt (config > data)
Add accounts in the following format:
Navigate to the file login_accounts.txt (config > data)
Add accounts in the following format:
Navigate to the file generate_nodes_accounts.txt (config > data)
Add accounts in the following format:
Navigate to the file connect_twitter_accounts.txt (config > data)
Add accounts in the following format:
Navigate to the file twitter_tokens.txt (config > data)
Add accounts in the following format:
Navigate to the file connect_discord_accounts.txt (config > data)
Add accounts in the following format:
Navigate to the file discord_tokens.txt (config > data)
Add accounts in the following format:
Navigate to the file export_stats_accounts.txt (config > data)
Add accounts in the following format:
Navigate to the file referrals_codes.txt (config > data)
Add codes in the following format (URL or code):
This section contains your license key which authenticates your installation and enables all features of the software.
threads: Controls the number of concurrent operations. Higher values increase processing speed but require more system resources. Currently set to 20 (high throughput).
cpu_thread_count: CPU thread allocation for FARM mode. Value of 0 uses maximum available threads. Note that 1 process is always allocated for node verification.
shuffle_accounts: When enabled (true), processes accounts in random order. This helps distribute load and avoid pattern detection.
database_url: Database connection string. Currently using SQLite as the default database system. For PostgreSQL, use format: postgres://user:pass@host/db_name
error_delay: Waiting time in seconds before retrying a failed operation (currently 1 second)
max_register_attempts: Maximum number of registration attempts per account
max_login_attempts: Maximum number of login attempts per account
max_stats_attempts: Maximum attempts to retrieve statistics
max_generate_attempts: Maximum attempts for node generation
max_proxy_change_attempts: Maximum attempts to switch to a different proxy
max_twitter_connect_attempts: Maximum attempts to connect Twitter account
max_discord_connect_attempts: Maximum attempts to connect Discord account
use_proxy_for_imap: Controls proxy usage for IMAP connections
skip_logged_accounts: When enabled (true), skips processing of already logged accounts
This section allows you to use a single IMAP server for all email operations. When disabled (false), the system will use the appropriate server for each email provider based on the IMAP settings section.
max_active_nodes: Maximum number of simultaneously active nodes (10)
max_generate_nodes: Maximum number of nodes that can be in generating state (15)
delay_between_generation: Random delay range (in seconds) between node generations
min: 2, max: 3
delay_between_verification: Random delay range (in minutes) between verification operations for nodes
min: 50, max: 70
generate_count: Range for number of nodes to generate per account
min: 1, max: 2
This section contains settings for captcha solving services. You can use 2captcha, anticaptcha, or capsolver. Currently configured to use capsolver.
enable: Master switch for email redirection functionality (disabled)
email: Primary email address for redirection
password: Authentication credentials for redirect email
imap_server: IMAP server address for redirect email (configured for ukr.net)
delay_before_start: Random delay range (in seconds) before starting operations
min: 5, max: 10
This section maps email domains to their corresponding IMAP servers. The system will automatically use the appropriate IMAP server based on the email domain unless a single IMAP server is specified.
You can add any other email providers and their corresponding IMAP servers to the imap_settings section following the same format: domain.com: imap.domain.com
For optimal performance, adjust the thread count based on your system's capabilities
For higher security, consider enabling proxy usage for IMAP connections
