Donut Swap
Welcome to DonutSwap, a cutting-edge AMM and Yield Farming platform, redefining DeFi. Built on Ethereum with cross-chain capabilities, DonutSwap propels your assets across blockchain borders, maximizing earning potential. With diverse liquidity pools and advanced yield farming, our platform is a potent blend of security, flexibility, and profit. Dive into the future of decentralized finance with us, taste the sweet success of financial freedom, and unlock a new era of prosperity. The sweet side of DeFi starts here.
Owner privileges
Comments
Ownership Privileges
- The owner can claim the stuck tokens.
- The owner can whitelist addresses from fees.
- The owner can update the buy and sell fees of not more than 10%.
- The owner can set the wallet-to-wallet transfer fees to not more than 10%.
- The owner can change the marketing wallet address.
- The owner can enable trading only once.
- The owner can enable/disable swapping.
- The owner can set the minimum swap amount of not less than 0.0001% of the total supply.
- The contract balance will be sent to the marketing wallet address(0xc209CCADBacA5A67B4f60C2832Ba19C37Dd63c2d) automatically after the swapping is completed.
Note - This Audit report consists of a security analysis of the Donut Swap smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the Donut Swap team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.
Audit Scope
This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.
We will verify the following claims:- Correct implementation of Token standard
- Deployer cannot mint any new tokens
- Deployer cannot burn or lock user funds
- Deployer cannot pause the contract
- Overall checkup (Smart Contract Security)
- Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
- Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.
Functions
public
93
State variables
public
12
Total lines
of code
839
Capabilities
Hover on items
Audit Details
Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.
Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.
low Issues
Pending
#1 Issue
Unchecked tokens transfer (unchecked-transfer)
L650-659
Use `SafeERC20`, or ensure that the transfer/transferFrom return value is checked.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L341-353
L254-256
L258-264
L266-272
L274-283
L298-300
L302-309
L285-287
L289-296
L243-245
L329-339
L311-327
L361-364
L515-530
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L387-390
L392-396
L414-416
L418-420
L434-437
L439-441
L443-446
L448-464
L466-469
L471-479
L668-670
Use the `external` attribute for functions never called from the contract.
Diagrams
Disclaimer
SolidProof.io reports are not, nor should be considered, an âendorsementâ or âdisapprovalâ of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any âproductâ or âassetâ created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etcâ...)
SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.
SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProofâs position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.