Proxies
Proxies can be used for performing operations with RPCs or for modules which require interaction with external APIs, such as Magic Eden Launchpad. Proxies must be stored in the following format:
ip:port:username:passwordMinter Suite will detect the .txt files present on your bot's folder and prompt you to select a file from them to use as proxy source. This allows you to load several proxy files onto your folder, and being able to pick which file you want to run.
Therefore, a proxy, or several proxies can be loaded onto the same file, for example proxies.txt , such as:
minterbot.art:1234:mev:david
minterbot.art:1234:ms:mommy
etc.
Providers
Some suggestions for popular proxy providers are: Oxylabs, BrightData, SmartProxy.
DYOR when purchasing from proxy providers, most of them are just reselling proxies from the larger providers, so you will just be paying an expensive markup fee on top. This is not the case for the providers suggested, in fact, they are mostly used as source for other proxy provider resellers, so when possible try to go to the source 😉.
BirdProxies is another provider which while it is slightly more expensive, it gives good results.
Static/Sticky vs Rotating
The most optimal way to use proxies is by re-using HTTP client connections.
Rotating
When running rotating proxies, a new HTTP client connection has to be established every time before sending an HTTP request. If you want to run rotating proxies, you MUST only enter ONE proxy, the rotating proxy. Else, Minter Suite will think you are running static proxies and therefore the intended behaviour of "rotating" proxies will not be used.
Static/Sticky
Static/Sticky proxies are more straight forward, one unique IP is established per proxy and it's HTTP client connection is constantly reused. Minter Suite will make a pool for the proxies with the connection established and use them effectively.
However, this has an overhead attached to it, as the connections remain open, this means you can easily reach your machine's threshold limit for open connections, which on Windows can be pretty low (5000 - 65534). This can produce the infamous error: `wsarecv: An existing connection was forcibly closed by the remote host . On Linux machines, the open connection limits are higher so it's more efficient when running larger proxy list files.
Our Recommendations
When running static/sticky proxies, don't run huge proxy list files of > 10,000 proxies as it will be counter-productive. Connection pools will not be re-used efficiently and you could easily reach your device's limit and start causing errors.
Rotating proxies aren't as bandwidth optimal as static/sticky proxies, but their usage is still more effective to reduce API bans, as new IP connections are constantly being assigned. Therefore we recommend to run at least one instance with a rotating proxy to obtain better results.
Last updated