Open ghost opened 3 years ago
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.
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.
This request is to:
Rules
This means the bot is learning from historical data to help with risk assessment of new contracts