From f48459903502c5daaf29c7df03b921ca85619552 Mon Sep 17 00:00:00 2001 From: Liron Achdut Date: Sun, 2 Oct 2022 16:44:00 +0300 Subject: [PATCH] remove recommendation to use safemath not needed since solidity 0.8 --- development-guidelines/token_integration.md | 1 - 1 file changed, 1 deletion(-) diff --git a/development-guidelines/token_integration.md b/development-guidelines/token_integration.md index 5939307d..0e035c55 100644 --- a/development-guidelines/token_integration.md +++ b/development-guidelines/token_integration.md @@ -27,7 +27,6 @@ To follow this checklist, use the below output from Slither for the token: ## Contract composition - [ ] **The contract avoids unneeded complexity.** The token should be a simple contract; a token with complex code requires a higher standard of review. Use Slither’s [`human-summary` printer](https://github.com/crytic/slither/wiki/Printer-documentation#human-summary) to identify complex code. -- [ ] **The contract uses `SafeMath`.** Contracts that do not use `SafeMath` require a higher standard of review. Inspect the contract by hand for `SafeMath` usage. - [ ] **The contract has only a few non–token-related functions.** Non-token-related functions increase the likelihood of an issue in the contract. Use Slither’s [`contract-summary` printer](https://github.com/crytic/slither/wiki/Printer-documentation#contract-summary) to broadly review the code used in the contract. - [ ] **The token only has one address.** Tokens with multiple entry points for balance updates can break internal bookkeeping based on the address (e.g., `balances[token_address][msg.sender]` may not reflect the actual balance).