@@ -7,17 +7,16 @@ Follow our guidelines and best practices to write secure smart contracts.
77** Table of contents:**
88
99- [ Development guidelines] ( ./development-guidelines )
10- - [ Secure development workflow] ( ./development-guidelines/workflow.md )
1110 - [ High-level best practices] ( ./development-guidelines/guidelines.md )
11+ - [ Incident Response Recommendations] ( ./development-guidelines/incident_response.md )
12+ - [ Secure development workflow] ( ./development-guidelines/workflow.md )
1213 - [ Token integration checklist] ( ./development-guidelines/token_integration.md )
14+ - [ Learn EVM] ( ./learn_evm ) : EVM technical knowledge
15+ - [ EIPs - forks] ( ./learn_evm/eips_forks.md ) : summarize the EIPs included in each fork
1316- [ Program analysis] ( ./program-analysis ) : How to use automated tools to secure contracts
14- - [ Slither] ( ./program-analysis/slither ) : a static analyzer avaialable through a CLI and scriptable interface.
1517 - [ Echidna] ( ./program-analysis/echidna ) : a fuzzer that will check your contract's properties.
18+ - [ Slither] ( ./program-analysis/slither ) : a static analyzer avaialable through a CLI and scriptable interface.
1619 - [ Manticore] ( ./program-analysis/manticore ) : a symbolic execution engine that can prove the correctness properties.
17- - [ Learn EVM] ( ./learn_evm ) : EVM technical knowledge
18- - [ EIPs - forks] ( ./learn_evm/eips_forks.md ) : summarize the EIPs included in each fork
19-
20- For each tool, this training material will provide:
21-
22- - a theoretical introduction, a walkthrough of its API, and a set of exercises.
23- - exercises expected to require ~ two hours to practically learn its operation.
20+ - For each tool, this training material will provide:
21+ - a theoretical introduction, a walkthrough of its API, and a set of exercises.
22+ - exercises expected to require ~ two hours to practically learn its operation.
0 commit comments