Demo proposal, week 6: Blockchain monitoring, incident response with Open zeppelin defender #73
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
Names and KTH ID
Deadline
Category
Description
OpenZeppelin Defender is known for security monitoring and general automation. This demo will use several of the components from OpenZeppelin Defender to automate incident response for a smart contract.
The plan is to:
Relevance
Security is a very important aspect of smart contracts, and therefore we need tools for monitoring, analytics and response. This demo will show how one could safeguard contracts, which is crucial in developing blockchain applications.