Doge Affiliate
Doge Affiniate is a token born inspired by the strength of solidarity from the community of famous cryptocurrencies in the world such as doge, shiba, Doge Affiliate with technological superiority that will help you make money directly from trading. introduce and engage more Doge Affiliate token holders. The first meme token to market affiliate links to the community.
Owner privileges
Comments
Ownership/Authorized Privileges:
The contract has 4 modifiers - isAdmin, onlyOwner, isLottery, and isAffiliateSM. Moreover, the owner address is able to call all the functions with these modifiers along with the other addresses associated with them.
The other addresses will still be able to make changes in the contract even after the ownership is renounced.
isAdmin(marketing wallet) Privileges:
- Enable Trading but cannot disable it.
- Enable/Disable the state of the lottery
- Update tokens per ticket and swap tokens at the amount, but it must be less than 1% of the total supply.
- Update Affiliate and Lottery SM address
- Include/Exclude accounts from Fees and Reward
isAffiliateSM (marketing or affiliateSM addresses) privileges:
- Set Referral wallet
isLottery (marketing or lotterySM addresses') privileges:
- Increase and Decrease Lottery ticket number for an account.
onlyOwner Privileges:
- Update marketing wallet, Reserve wallet, and Lottery wallet.
- Withdraw tokens from the contract balance but not the native ones
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
50
State variables
public
17
Total lines
of code
795
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
Local variables shadowing (shadowing-local)
L267
L596
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Access Control (events-access)
L752-755
L757-760
L762-765
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Events Arithmetic (events-maths)
L371-374
L777-780
Emit an event for critical parameter changes.
Pending
#4 Issue
Missing Zero Address Validation (missing-zero-check)
L227
Check that the address is not zero.
Pending
#5 Issue
Floating Pragma
-
The current pragma Solidity directive is â^0.8.17". Contracts should be deployed with the same compiler version and flags that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions
Pending
#6 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)
L31-34
Remove unused functions.
Pending
#2 Issue
Function initializing state variables (function-init-state)
L147
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.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L146
L152
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L55-57
L59-62
L245-247
L249-251
L253-255
L258-260
L267-269
L271-274
L276-288
L290-293
L295-304
L306-309
L311-313
L315-328
L347-349
L357-361
L363-369
L399-401
L403-405
L407-409
L789-792
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.