Subsmate
Additionally, Subsmate Profile NFTs contain a subscribe module. This module contains the logic that allows different accounts to be issued subscribe NFTs to record their relationship to the main profile on-chain.
Owner privileges
Comments
Ownership Privileges
- Change sale status at any time, which means that the owner can start or cancel the sale at any point in time
- Withdraw USDC from the contract
- Change lockTime, finishTime, and startTime of the sale at any point in time which may result in the locking of the user's funds because if the lockTime is changeable then users won't be able to claim their tokens. Note that these values can also be set to zero which will result in funds available to claim right after deposits.
- Set the max allocation amount to any arbitrary value including zero and stop users from buying tokens
- Add a new vesting round with any arbitrary value of '_claimPercent'
- The owner can withdraw sale tokens from the presale contract.
Note - The owner can basically buy the tokens for "free" from the presale contract because it is possible for the owner to withdraw the USDC sent while buying tokens. Moreover, keep in mind that the owner controls every aspect of the presale contract.
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
25
State variables
public
16
Total lines
of code
1178
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)
L1099-1101
L1103-1109
L1111-1117
L1119-1125
Emit an event for critical parameter changes.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L233-245
L87-89
L97-103
L116-122
L130-139
L172-174
L182-189
L147-149
L157-164
L38-44
L62-67
L221-231
L197-213
L838-840
L501-511
L442-455
L466-477
L457-464
L479-493
L418-424
L426-433
L706-715
L666-668
L732-741
L622-624
L683-692
L537-543
L579-584
L591-596
L562-572
L550-555
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L904-906
L912-915
L1055-1057
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.