kovart / forta-attack-simulation Goto Github PK

View Code? Open in Web Editor NEW

48.0 48.0 6.0 403 KB

🦠🔬 Forta bot that detects deployment of smart contracts containing exploits

License: Other

JavaScript 0.61% Shell 1.13% Dockerfile 0.51% TypeScript 91.31% Solidity 6.44%

agent attack blockchain bot ethereum exploit forta prevention simulation

forta-attack-simulation's People

Contributors

Stargazers

Watchers

Forkers

jeffchen006 guoshijiang 0xtaf kayaba-attribution jsvisa dianxiang-sun

forta-attack-simulation's Issues

High drop rate in May for the attack-simulation-bot-targeted

Kovart, going over the performance of this bot in May it has high drop rates in the BSC and ETH chain. It would be great if you could take a look at it and consider sharding as an option. Thank you!

Attack simulation bot didnt trigger on Euler attack

Did trigger locally, but not on the network due to queue being too large.
Pls implement sharding.

Add a prioritized contract processing queue

In order to reduce the detection time of potentially malicious contracts, it is proposed to create a prioritized processing queue, which will be based on alerts associated with the address of the deployer as well as its on-chain reputation.

It is worth considering implementations of the handleAlert() function, which will raise the processing priority in real time.