└── README.md


/README.md:
--------------------------------------------------------------------------------
  1 | # 🎉 Grass bot is Ready! 🎉
  2 | We’ve released two versions of software for farming Grass:
  3 | 
  4 | 1) 🔥 FREE version works only with accounts registered through it.
  5 |   * **Download free version in our Telegram bot:** https://t.me/FAMERS0FT
  6 | 
  7 | 2) 💎 PAID version supports any accounts — register using your own referral code!
  8 |   * **DM us for the paid version in Telegram:** https://t.me/FAMERS0FT
  9 | 
 10 | - 📩 Contacts: https://t.me/FAMERS0FT
 11 | 
 12 | - - -
 13 | 
 14 | **🚀 What can our software do?**
 15 | 
 16 | * ✅ Account registration
 17 | * ✅ Email verification
 18 | * ✅ Wallet approval
 19 | * ✅ Farming in X1, X1.25, and X2 modes
 20 | 
 21 | 
 22 | **💪 Why our GRASS bot is better than alternatives?**
 23 | 
 24 | * 1️⃣ Traffic efficiency — consumes much less data compared to competitors.
 25 | * 2️⃣ Speed — works significantly faster than other solutions.
 26 | * 3️⃣ Smart proxy manager — instantly switches proxies if a connection drops.
 27 | * 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!
 28 | 
 29 | 
 30 | **🛠 What else can we offer?**
 31 | 
 32 | * Unlimited residential proxies (price negotiable, depends on server count).
 33 | * Traffic-based proxies — just $1.5 per GB
 34 | * Another our softwares:
 35 |    * [Grass](https://github.com/CryptoDepin/grass-bot)
 36 |    * [Dawn](https://github.com/CryptoDepin/dawn-validator-bot)
 37 |    * [LayerEdge](https://github.com/CryptoDepin/layeredge-bot)
 38 |    * [Gradient](https://github.com/CryptoDepin/gradient-network-bot)
 39 |    * [NodeGo](https://github.com/CryptoDepin/nodego-bot)
 40 |    * [Bless](https://github.com/CryptoDepin/bless-network-bot)
 41 |    * [DeSpeed](https://github.com/CryptoDepin/despeed-bot)
 42 |    * [NodePay](https://github.com/CryptoDepin/nodepay-bot)
 43 |    * [Monadscore](https://github.com/CryptoDepin/monadscore-bot)
 44 | 
 45 | Invite your friends and colleagues to join! 🚀
 46 | 
 47 | # How to use? Documentation
 48 | ### Installation
 49 | **Software will autimatically install in: C:\Program Files (x86)\GrassBot_free_v1.5**
 50 | 
 51 | **You cannot change the location directory of the software**
 52 | 
 53 | ### Setting Up CAPTCHA Key
 54 | * In the `Data` folder, open the `config.ini` file.
 55 | * Specify the CAPTCHA-solving service `api key` for 2captcha.com
 56 | 
 57 | ### Adding Email Accounts
 58 | * In the `Data` folder, use the `emails.txt` file.
 59 | * Add email accounts in the format: `email:password`.
 60 | * Ensure the email accounts support `IMAP`; otherwise, verification will fail.
 61 | 
 62 | ### Setting IMAPS
 63 | * In the `Data` folder, open the `imaps.txt` file.
 64 | * 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.
 65 | 
 66 | ### Adding Proxies
 67 | * In the `Data` folder, use the `proxy.txt` file.
 68 | * Add proxies in the format: `ip:port` or `login:password@ip:port`.
 69 | 
 70 | ### Account Registration
 71 | * Successful registrations will be saved in the `reg_goods.txt` file.
 72 | * Emails that failed to register will be listed in the `reg_bads.txt` file.
 73 | 
 74 | ### Preparing Accounts for Farming
 75 | * Move successfully registered accounts from `reg_goods.txt` to the `accs.txt` file in the `Data` folder.
 76 | * Ensure `proxy.txt` contains proxies in the required format.
 77 | * Start the farming process.
 78 | 
 79 | ### Email Verification
 80 | * Place accounts to be verified in the `accs.txt` file in the `Data` folder.
 81 | * Use the `proxy.txt` file for proxies in the specified format.
 82 | * Successfully verified accounts will be saved in `approveEmail_goods.txt`.
 83 | * Failed verifications will be logged in `approveEmail_bads.txt`. These accounts can be reattempted, as some might pass on subsequent tries.
 84 | 
 85 | ### Wallet Binding
 86 | * Add accounts needing wallet binding to the `accs.txt` file in the `Data` folder.
 87 | * Use `proxy.txt` for proxy configurations.
 88 | * Successfully bound wallets will be logged in `addWallet_goods.txt`, with additional wallet details appended in the format:` |wallet|seed phrase|wallet_private_key`.
 89 | * Failed bindings will be logged in `addWallet_bads.txt`. Retry binding for failed accounts.
 90 | 
 91 | ### Wallet Email Verification
 92 | * Add accounts for email verification of wallets to the `accs.txt` file in the `Data` folder.
 93 | * Use the `proxy.txt` file for proxies.
 94 | * Successfully verified accounts will be saved in `approveWalletEmail_goods.txt`.
 95 | * Failed verifications will be logged in `approveWalletEmail_bads.txt`. Retry failed accounts if needed.
 96 | 
 97 | ### Collecting Reward Tiers
 98 | * This mode collects rewards based on specific point or referral thresholds. Frequent use is unnecessary.
 99 | * Add accounts for reward collection to the `accs.txt` file in the `Data` folder.
100 | * Use `proxy.txt` for proxies.
101 | 
102 | # 🔗 Contacts
103 | * 📩 https://t.me/FAMERS0FT
104 | 


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