TO Pays
Welcome to TO pays, a revolutionary platform that pays it's community back to spend on cool products donate to charity or convert into USD. Our project, established in 2023, is driven by a team of experienced professionals who are committed to building a trusted and rewarding platform. Our vision is to create a happy community where everyone can be useful to everyone. We believe in incentivising our users by paying them back, as we consider it to be extremely valuable. We are committed to continuously updating our platform with the best features to provide an exciting shopping experience.
Owner privileges
Comments
Ownership Privileges
- Deployer can enable/disable following state variables
- _isExcludedMaxTransactionAmount[updAds]
- swapEnabled
- _isExcludedFromFees[account]
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
98
State variables
public
26
Total lines
of code
1284
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
Reentrancy vulnerabilities
L1087
Apply the [`check-effects-interactions pattern`](http://solidity.readthedocs.io/en/v0.4.21/security-considerations.html#re-entrancy).or nonReentrant modifier from OpenZeppelin
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L950
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L1012-1017
L1019-1022
L1033-1039
L1041-1047
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L1066
L1071
Check that the address is not zero.
Pending
#4 Issue
Contract doesnât import npm packages from source (like OpenZeppelin etc.)
-
We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L14-17
L402-410
L579-581
L595-598
L703-706
L694-698
L674-680
L662-669
L685-689
L709-712
L716-720
Remove unused functions.
Pending
#2 Issue
Unused state variables (unused-state)
L657
Remove unused state variables.
Pending
#3 Issue
Unused return values (unused-return)
L1216-1229
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)
L209-211
L217-219
L234-236
L260-263
L268-270
L279-282
L297-305
L319-322
L338-341
L637-640
L1054-1058
L1077-1079
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.