Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Database of historical tokens for risk assessment #7

Open
ghost opened this issue Sep 2, 2021 · 2 comments
Open

Comments

@ghost
Copy link

ghost commented Sep 2, 2021

This request is to:

  • Add a database or log file that stores every contract that was not bought due to a fail in the audit. whether it is a rugcheck, honeypot fail etc
  • Each time the bot finds a new contract, it compares data against the log file as part of it's audit

Rules

  • Previous contract with same name was rugcheck/honeypot failed?
  • Previous contract owner is the owner of this new found contract?
  • X Y Z (whatever else we deem as good data to check on each contract)

This means the bot is learning from historical data to help with risk assessment of new contracts

@ghost ghost changed the title [New Feature Request] Database of historical tokens for risk assessment [Feature Request] Database of historical tokens for risk assessment Sep 2, 2021
@electronixxx
Copy link

I'd suggest doing this by hashing some functions of the smart contract, and saving these hashes into a local database. Then on each new token, the audit feature will check the hash of the current contract and check if its present. This is O(1) computations complexity since it uses hashes.

@JayArrowz
Copy link
Owner

JayArrowz commented Sep 23, 2021

Added to sniper improvements, this is indeed a really good change. We can even store rug contracts and pattern match for existing ones. Will most likely use entity framework so the choice of DB is the users.
I'll have basic config for a inmemory db.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants