You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As already anticipated Tsar, in my opinion If you want to focus your tools for advance users, you should separate the buy/copy tools from selling/trading tools.
For buying sniper and wallet hunters are perfect.
The problem is that I have many instances running for WH and sometimes also for Snippers. When some buy tx happens it is quite big mess to find information between all those files without wasting time.
As active user I would really appreciate if you could create a separate tool for selling and/or trading purposes
This tool would monitor token holdings of several wallets (refresh like every 5-10 sec)
We could skip holding values <$10
Option to skip some contracts manually.
In this way, we can monitor all open positions in ONE PLACE.
Furthermore, if some basic information of the token could be shown would be nice. MC, BUY/SELL FEE, TOTAL SUPPLY, AVG, AVG BUY PRICE, DELTA % FROM AVG ENTRY PRICE, HOLDINGS WORTH $$ (all this information monitored and refreshed every 5 seconds minimizing queris to our nodes)
Now the opperations to do.
Stablish up to two limit sells (like currently WH does)
Trailing stop (under development)
Option for autosell if it detects change fee method ID with >30% to <10% sell fee.
Protection mechanism
All best antirug in place
Minimum $ value to sell
Max sell fee
In the future if you are thinking to put these services behind a nice UI, I think it will be easier having them separated. 1 tab for snipping, 1 tab for wh, 1 tab for open position handling with respective config parameters.
I know these are BIG words and huge development. At least would be good to have some open discussion in the community and hopefully it helps to stablish the best roadmap for your project.
The text was updated successfully, but these errors were encountered:
For multiple instances of current bots, you can use WinSSHTerm, so you can see many windows at once.
You can also track your wallet with EtherDrops on Telegram to see actively entered/exit positions.
As for WalletHunter, the buy/sell with autosell can already be defined.
For the UI part, it sounds nice, but i would personally advise against, as it would put much time into a how the tools are looking, and would limit development time on bot bugfixes and features.
As already anticipated Tsar, in my opinion If you want to focus your tools for advance users, you should separate the buy/copy tools from selling/trading tools.
For buying sniper and wallet hunters are perfect.
The problem is that I have many instances running for WH and sometimes also for Snippers. When some buy tx happens it is quite big mess to find information between all those files without wasting time.
As active user I would really appreciate if you could create a separate tool for selling and/or trading purposes
This tool would monitor token holdings of several wallets (refresh like every 5-10 sec)
We could skip holding values <$10
Option to skip some contracts manually.
In this way, we can monitor all open positions in ONE PLACE.
Furthermore, if some basic information of the token could be shown would be nice. MC, BUY/SELL FEE, TOTAL SUPPLY, AVG, AVG BUY PRICE, DELTA % FROM AVG ENTRY PRICE, HOLDINGS WORTH $$ (all this information monitored and refreshed every 5 seconds minimizing queris to our nodes)
Now the opperations to do.
Stablish up to two limit sells (like currently WH does)
Trailing stop (under development)
Option for autosell if it detects change fee method ID with >30% to <10% sell fee.
Protection mechanism
All best antirug in place
Minimum $ value to sell
Max sell fee
In the future if you are thinking to put these services behind a nice UI, I think it will be easier having them separated. 1 tab for snipping, 1 tab for wh, 1 tab for open position handling with respective config parameters.
I know these are BIG words and huge development. At least would be good to have some open discussion in the community and hopefully it helps to stablish the best roadmap for your project.
The text was updated successfully, but these errors were encountered: