-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
New Feature - Was it really a honeypot? #18
Comments
This sadly isn't entirely true and valid to fully rely on it. |
WOW, i'm shocked to hear this. This is news to me and I wonder if I have been a victim of this as well. Do you know if EVERY coin of theirs is a "honeypot" or do they like to mix it up to add to the confusion? |
Also is there a way to "screen" for whitelist functions? |
They change it during the trade, which makes it difficult to be completely sure. |
Yes, i think it would be good if WH could somehow screen for whitelist functions. But i don't know how hard that would be to implement. |
It would be really helpful if the bot could keep track of the coins that were initially labeled as honeypots BUT where the tracked wallet was still able to sell them later on. This would indicate that the coin wasn't a honeypot after all.
This feature would be useful for tweaking strategies. For example, if the tracked wallet is profitable at buying and selling coins that were initially detected to be "honeypots," then the user could decide to disable the honeypot protection mechanism. Disabling the honeypot protection in this case would be desirable because they are overall making profits.
Specifically, I’m thinking WH could display a message indicating that coin originally labeled as a "honeypot" has been successfully sold.
It would be even nicer if the TX log could display a message that the tracked wallet sold a honeypot coin and for how much profit.
(I know the TX wallet is pretty much only for coins that the user bought, but for analysis purposes, I think this would be a great feature).
The text was updated successfully, but these errors were encountered: