From 7da08419c4d6356379452670f76a2183584c89e5 Mon Sep 17 00:00:00 2001 From: Lebid Yuriy Date: Wed, 17 Aug 2022 16:14:44 +0200 Subject: [PATCH] Update guidelines.md https://github.com/crytic/slither/wiki/Detector-Documentation#recommendation-39 follow to `Dangerous strict equalities` recommendations. To avoid confusion in future I propose to use unique link ...#incorrect-versions-of-solidity --- development-guidelines/guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/development-guidelines/guidelines.md b/development-guidelines/guidelines.md index dbcac12a..f5270a25 100644 --- a/development-guidelines/guidelines.md +++ b/development-guidelines/guidelines.md @@ -82,7 +82,7 @@ The architecture of your codebase should make your code easy to review. Avoid ar ### Solidity - **Favor Solidity 0.5 or 0.6.** In our opinion, Solidity 0.5 and 0.6 are more secure and have better built-in practices than 0.4. Solidity 0.7 is too young to be used in production and needs time to mature. -- **Use a stable release to compile; use the latest release to check for warnings.** Check that your code has no reported issues with the latest compiler version. However, Solidity has a fast release cycle and has a history of compiler bugs, so we do not recommend the latest version for deployment (see Slither’s [solc version recommendation](https://github.com/crytic/slither/wiki/Detector-Documentation#recommendation-39)). +- **Use a stable release to compile; use the latest release to check for warnings.** Check that your code has no reported issues with the latest compiler version. However, Solidity has a fast release cycle and has a history of compiler bugs, so we do not recommend the latest version for deployment (see Slither’s [solc version recommendation](https://github.com/crytic/slither/wiki/Detector-Documentation#incorrect-versions-of-solidity)). - **Do not use inline assembly.** Assembly requires EVM expertise. Do not write EVM code if you have not _mastered_ the yellow paper. ## Deployment guidelines