CURVE Network
Curve network is a Layer-1 network with lightning-fast, Secure & scalable blockchain economy. Curve Network Token. CURVE is the native utility token of Curve network blockchain. CURVE will be used to pay transaction fees or any services directly related to the on-chain activity.
Owner privileges
Comments
Ownership Privileges
- Enable/Disable trading
- Include/Exclude wallets from reward, blacklist, and fee
- Set buy/sell fees to any arbitrary value including 100% or more
- Update marketing and team wallet address
- Update the cooldown period, and 'swap tokens at amount' to any arbitrary value
- Update max transaction limit, and max wallet limit to any arbitrary value including zero and lock user funds
- Update router and pair address
- Withdraw any type of tokens from the contract balance.
Note - The liquidity of the contract will be transferred to the owner wallet until the contract is renounced.
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
52
State variables
public
13
Total lines
of code
683
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.
medium Issues
Pending
#1 Issue
Fees can be 100% or more
L348
L353
The owner is able to set fees up to 100% or more which may result in loss of user funds
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L249
L462
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L628-631
L633-635
L656-659
L661-663
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L205-206
L619
L623
L665
Check that the address is not zero.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L35-38
Remove unused functions.
Pending
#2 Issue
Unused return values (unused-return)
L573-586
Ensure that all the return values of the function calls are used.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L142
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L59-61
L63-66
L229-231
L232-234
L240-242
L249-251
L253-256
L258-266
L268-271
L273-279
L281-285
L287-289
L291-300
L336-338
L340-342
L344-346
L348-351
L353-356
L677-679
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.