Add common security risks lesson #21
Merged
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
nuke-web3
approved these changes
Nov 12, 2023
There was a problem hiding this comment.
This is SO FREAKIN' GREAT! The content is vast, and you did a great job using the slides system here 🤩
Thanks a ton for this great content! cc @Asamartino this is a good place to look at for an example for new contributors the the book coming in IMHO.
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.
This lesson focuses on identifying and fixing common security risks in Polkadot SDK projects witht the aim to provide clear guidance on implementing more robust access control, better cryptographic practices, and overall secure design to improve the safety and integrity of your work.