User Guide - Getting Started
Last updated
Last updated
This module is designed for automatic registration and verification of accounts
After registration, the session is saved to the database for future use
If the account is not verified, you can run the module again and the software will automatically verify it
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 accounts" or "Verify accounts" module
After login, the session is saved to the database for future use
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 accounts (tested with 10k 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:
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
Module exports detailed account statistics into a single consolidated report: accounts_stats.csv
If you set true for the value convert_csv_to_excel in the config, the csv file will be automatically converted to excel
The report includes comprehensive account information in the following structure:
Account Password
User ID
Referral Code
Referral Count
Stork Signed Prices Count
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
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.
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)
If you set true for the gen_random_pass_for_accounts value in the config, the software will generate a random password for accounts; if you set false, the software will use the email password
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 export_stats_accounts.txt (config > data)
Add accounts in the following format:
Navigate to the file farm_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 (only code):
threads: Controls concurrent account operations. Registration and login modules enforce a max of 5.
database_url: Use SQLite or PostgreSQL (e.g. postgres://user:password@host/dbname).
shuffle_accounts: Shuffles account processing order to avoid detection patterns.
gen_random_pass_for_accounts: Automatically generates strong passwords for new accounts.
convert_csv_to_excel: Converts stats from .csv to .xlsx after farming.
delay_before_start: Random delay before task start. Default delay range is 30–60s for some modules, so only max is customizable.
error_delay: Wait time before retrying after an error.
max_*_attempts: Limits retry count for each action.
enabled: Turns on IMAP-based email fetching (used for verification codes).
imap_server: Custom IMAP server (e.g. imap.gmx.net).
use_proxy: Enables proxy for mail fetching.
ℹ️ Format for email login in login_accounts.txt or register_accounts.txt:
Only main mail is used for fetching login/verification codes.
use_proxy_for_imap: Enables proxy for IMAP access.
use_single_imap: If enable is true, all accounts will use this IMAP server.
servers: Mapping of common domains to their IMAP endpoints (auto-resolution).
