Zynk Protocol
Zynk Protocol is a DeFi Company that integrates futuristic blockchain technology to provide a comprehensive ecosystem. Our goal is to build innovative and disruptive DeFi utilities such as Bridges, Wallets, NFTs, Dapps, and Swaps, among others. We aspire to revolutionize the industry and become the go-to platform for all DeFi needs.
Owner privileges
Comments
Ownership Privileges:
- Update liquidity providing state
- Update liquidity threshold
- Enable trading but cannot disable it
- Update tax but can only set it to a pre-defined value with a maximum of 5 %
- Update deadline but it must be less than 5 blocks
- Update dev and marketing wallet
- Include/Exclude wallets from the fee
- Withdraw ETH and other tokens from the contract but not the native ones
We recommend investors/users 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
49
State variables
public
12
Total lines
of code
770
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
Missing Events Arithmetic (events-maths)
L700-703
L733-737
Emit an event for critical parameter changes.
Pending
#2 Issue
Modifiers that can return the default value (incorrect-modifier)
L480-486
All the paths in a modifier must execute `_` or revert.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L23-26
Remove unused functions.
Pending
#2 Issue
Unused return values (unused-return)
L681-694
Ensure that all the return values of the function calls are used.
Pending
#3 Issue
Uninitialized local variables (uninitialized-local)
L580
L577
L578
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L463
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L104-106
L112-114
L136-138
L161-169
L174-182
L191-199
L214-229
L243-254
L270-283
L394-396
L398-404
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.