[Feature Request] Database of historical tokens for risk assessment

[CryptoCarlos21]

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

[electronixxx]

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]

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.