└── README.md


/README.md:
--------------------------------------------------------------------------------
  1 | # 🎉 NodeGo bot is Ready! 🎉
  2 | We’ve released software for farming NodeGo:
  3 | 
  4 | * 🔥 AVAILABLE ONLY paid version
  5 | * 💎 PAID version supports any accounts — register using your own referral code!
  6 | * **📩 DM us for the paid version in Telegram**: https://t.me/FAMERS0FT
  7 | 
  8 | - 📩 Contacts: https://t.me/FAMERS0FT
  9 | 
 10 | - - -
 11 | 
 12 | **🚀 What can our software do?**
 13 | 
 14 | * ✅ Account registration
 15 | * ✅ Email verification
 16 | * ✅ Authorization (for old accounts)
 17 | * ✅ Farming
 18 | * ✅ Linking Twitter
 19 | * ✅ Linking Discord
 20 | 
 21 | **💪 Why our NodeGo bot is better than alternatives?**
 22 | 
 23 | * 1️⃣ Traffic efficiency — consumes much less data compared to competitors.
 24 | * 2️⃣ Speed — works significantly faster than other solutions.
 25 | * 3️⃣ Smart proxy manager — instantly switches proxies if a connection drops.
 26 | * 4️⃣ Optimized performance — no need for 3–5–10 servers. You only need 1–2 servers for full functionality. For Windows, the optimal thread count is 15K, with some servers capable of handling even more!
 27 | 
 28 | **🛠 What else can we offer?**
 29 | 
 30 | * Unlimited residential proxies (price negotiable, depends on server count).
 31 | * Traffic-based proxies — just $1.5 per GB 
 32 | * Another our softwares:
 33 |    * [Grass](https://github.com/CryptoDepin/grass-bot)
 34 |    * [Dawn](https://github.com/CryptoDepin/dawn-validator-bot)
 35 |    * [LayerEdge](https://github.com/CryptoDepin/layeredge-bot)
 36 |    * [Gradient](https://github.com/CryptoDepin/gradient-network-bot)
 37 |    * [NodeGo](https://github.com/CryptoDepin/nodego-bot)
 38 |    * [Bless](https://github.com/CryptoDepin/bless-network-bot)
 39 |    * [DeSpeed](https://github.com/CryptoDepin/despeed-bot)
 40 |    * [NodePay](https://github.com/CryptoDepin/nodepay-bot)
 41 |    * [Monadscore](https://github.com/CryptoDepin/monadscore-bot)
 42 | 
 43 | Invite your friends and colleagues to join! 🚀
 44 | 
 45 | # How to use? Documentation
 46 | ### Installation
 47 | **Software will automatically install in: C:\Program Files (x86)\NodeGo_private_v1.0**
 48 | 
 49 | **You cannot change the location directory of the software**
 50 | 
 51 | ### Setting Up CAPTCHA Key
 52 | * In the `Data` folder, open the `config.ini` file.
 53 | * Specify the CAPTCHA-solving service `api key` for 2captcha.com
 54 | 
 55 | ### Adding Email Accounts
 56 | * In the `Data` folder, open the `emails.txt` file.
 57 | * Add email accounts in this format: `mail:pass`. 
 58 | * If you have email accounts with email forwarding function, add them in this format: `fakemail:mail:pass`.
 59 | * Ensure the email accounts support `IMAP`; otherwise, verification will fail.
 60 | 
 61 | ### Setting IMAPS
 62 | * In the `Data` folder, open the `imaps.txt` file.
 63 | * Add the IMAP of the emails you use in this format: `email domain|imap`. For example: `desedumail.com|imap.firstmail.ltd`, where `desedumail.com` is an email domain, and `imap.firstmail.ltd` - its IMAP.
 64 | 
 65 | ### Adding Proxies
 66 | * In the `Data` folder, open the `proxy.txt` file.
 67 | * Add proxies in this format: `login:password@ip:port`, one per line.
 68 | 
 69 | ### Adding Referral Codes
 70 | * In the `Data` folder, open `referalCodes.txt` file.
 71 | * Add referral codes, one per line.
 72 | 
 73 | ### Linking Twitter accounts
 74 | * In the `Data` folder, open the `twitter.txt` file.
 75 | * Add Twitter auth_token, one per line. Each token corresponds to one Twitter account.
 76 | * Accounts with errors during the linking process will be logged in `twitter_bads.txt`.
 77 | * **In 99% of cases, errors occur due to invalid Twitter tokens.**
 78 | 
 79 | ### Linking Discord accounts
 80 | * In the `Data` folder, open the `discord.txt` file.
 81 | * Add Discord tokens, one per line. Each token corresponds to one Discord account.
 82 | * Accounts with errors during the linking process will be logged in `discord_bads.txt`.
 83 | *  **In 99% of cases, errors occur due to invalid Discord tokens.**
 84 |   
 85 | ### Account Registration
 86 | * Use option **Registration** to register new accounts.
 87 | * Failed registrations will be saved in the `reg_bads.txt` file.
 88 | 
 89 | ### Email Verification
 90 | * Use option **Email Verification** to verify the emails of new accounts.
 91 | 
 92 | ### Old Accounts Authorization
 93 | * In the `Data` folder, add your old accounts to the `accs_auth.txt` file in this format: `login:pass|mail:pass`.
 94 | * Use option **Authorization** to authorize your old accounts.
 95 | 
 96 | ### Farming
 97 | * Ensure `proxy.txt` contains proxies in the required format.
 98 | * Start the farming process.
 99 | 
100 | ### Collecting statistics
101 | * The **Collect statistics** module collects and analyzes account activity data, saving it in the `statistics_goods.txt` file.
102 | 
103 | ### Saving accounts to file
104 | * The **Save accounts to file** module saves all existing accounts in the `accounts.txt` file.
105 | 
106 | ### Removing unverified accounts
107 | * The **Remove unverified accounts** module deletes accounts with failed verification.
108 | 
109 | # 🔗 Contacts
110 | * 📩 https://t.me/FAMERS0FT
111 | 


--------------------------------------------------------------------------------