Yachtify
Yachtify Protocol offers a fractional private yacht ownership model that provides investors with a unique opportunity to be a part of a recession-proof maritime industry with multiple streams of income. By doing so, we're opening up the exclusive aviation market of the rich and powerful to cryptocurrency users. With our native token, $YCHT, investors can purchase fractional NFTs that represent a physical yacht. These yachts are insured and stored in high-security ports around the world, and existing yacht owners can list a minimum of 25% of their private yachts for fractional sale. Members can also trade yacht hour smart NFTs that decrease as the hours are used.
Owner privileges
Comments
Ownership Privileges
- Set charity address
- Set/Change the number of tokens to sell in order to add liquidity to any arbitrary value
- Enable/Disable swap and liquify
- Include/Exclude wallets from fees
- Set max transaction limit to any arbitrary value including zero and lock user funds
- Withdraw tokens and ETH from the contract but not the native ones
Note - This Audit report consists of a security analysis of the Yachtify smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. We recommend everyone to do their own research. Please beware that the liquidity of the contract is credited to the owner wallet which is controllable by the owner, in an extreme scenario, the owner will be able to drain liquidity. Moreover, we only audited one token contract for the Yachtify team, other contracts associated with the project are not audited by our team.
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
90
State variables
public
15
Total lines
of code
729
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
Liquidity will be transferred to an EOA
L683
Every time the swap and liquify function is called in the contract, the liquidity will be credited to the "owner" address which is not recommended because in this case, the liquidity receiver address is controllable by the owner.
low Issues
Pending
#1 Issue
Missing Events Arithmetic (events-maths)
L512-515
L525-528
L627-635
L637-645
Emit an event for critical parameter changes.
Pending
#2 Issue
Missing Zero Address Validation (missing-zero-check)
L500
Check that the address is not zero.
Pending
#3 Issue
State variables shadowing (shadowing-state)
L444
Remove the state variable shadowing.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L140-146
L167-178
L161-166
L153-155
L157-159
Remove unused functions.
Pending
#2 Issue
Function initializing state variables (function-init-state)
L411
L416
Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.
Pending
#3 Issue
Unused return values (unused-return)
L672-687
Ensure that all the return values of the function calls are used.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L98-101
L107-111
L126-128
L129-131
L132-134
L469-471
L475-478
L479-481
L482-485
L486-490
L491-494
L495-498
L507-510
L516-518
L520-522
L627-635
L637-645
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.