Spyd3r W3b

Screenshots

Problem Statement

Spyd3r W3b is a DevSecOps Tool aimed towards blockchain implementations.Dapp development and maintainence, Smart contract security and alerting, Platform performance and analytics and finally organisation management are the Pillar concepts of Spyd3r W3b. The lack of Advanced development and maintainence facilities for Onchain deployments and their coordination with auxilary offchain implementation which drive an entire Dapp and the organisation behind it led us to the creation of Spyd3r W3b. Builders can maintain ,Take organisational decisions, Streamline processes, Automate upgrades and versioning,Monitor and regulate onchain activities all through Spyd3r W3b. The Key responsibilty Spyd3r W3b will be taking is Enabling businesses of various spectrum to enter the Web3 world. Spyd3r W3b is also to heavily influence the Inflow of userbase to blockchain as it will have versions of the tools enabling both Builders and Users.

Solution

Current MVP version is built to monitor reentrancy attack and Transaction-Ordering Dependence (TOD) Attack.All the events emitted are also stored in mongoDB There are 3 microservices in this project:Listener_MS - This microservice listens to the following eventsa. Stake --stakes ether from userb. Unstake --unstakes ether from contractMemPool_MS - this microservice monitors the mempool for following interaction patterns to PAUSE THE CONTRACT using Lit Keys for keyless signing for the usera. Same function being called consecutively by same address within 20 blocksb. Gas sent for the transaction is less than requiredc. Stake and unstake are called within 20 blocks of each otherd. consecutive ether transfer from contract within 20 blocksMailing_MS - This microservice sends an email to the owner of smartcontract upon event emit of stake or unstake.Kafka Docker setup - a single channel called stakeClient is used to communicate between Listener_MS and Mailer_MS.