Skip to content

Commit 7f0924c

Browse files
authored
Update README.md
1 parent 3381152 commit 7f0924c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,10 @@ Follow our guidelines and best practices to write secure smart contracts.
77
**Table of contents:**
88

99
- [Development guidelines](./development-guidelines)
10-
- [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)
13-
- [Token integration checklist](./development-guidelines/token_integration.md)
10+
- [High-level best practices](./development-guidelines/guidelines.md): High-level best-practices for all smart contracts
11+
- [Incident Response Recommendations](./development-guidelines/incident_response.md): Guidelines on how to formulate an incident response plan
12+
- [Secure development workflow](./development-guidelines/workflow.md): A rough, high-level process to follow while you write code
13+
- [Token integration checklist](./development-guidelines/token_integration.md): What to check when interacting with arbitrary token
1414
- [Learn EVM](./learn_evm): EVM technical knowledge
1515
- [EIPs - forks](./learn_evm/eips_forks.md): summarize the EIPs included in each fork
1616
- [Program analysis](./program-analysis): How to use automated tools to secure contracts

0 commit comments

Comments
 (0)