AFFITRUM

Affitrum proposes to use AI algorithm and Web3 technologies to transform the digital advertising industry. By utilizing blockchain, smart contracts, and decentralized Ad networks. Affitrum can introduce transparency, eliminate intermediaries, enhance privacy, and ensure fair compensation for all participants. The project aims to empower advertisers, publishers, and users, creating a sustainable and efficient ecosystem.

Owner privileges
Comments
Ownership/Authority Privileges
- Launch Contract
- Withdraw tokens and ETH from the contract but not the native ones
- Set Fee receiver addresses
- Set liquidity treasury and distributor address
- Include/Exclude accounts from Fees
- Enable/Disable auto buyback, record buy, and add liquidity
- Add/Remove pair
- The buy/sell fees is fixed at 9%
Note - This Audit report consists of a security analysis of the AFFITRUM Token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the AFFITRUM team, other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.
Moreover, The actual code of the interfaces used in the contract IJackpot, readDistributor and IAffilBonusPool were not a part of the audit scope and we cannot comment on its security. On the other hand, the distributor address can be used to lock tokens as we don't know the actual code and it can be used to return type(unit256).max
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
95
State variables
public
35
Total lines
of code
2099
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)
L1785
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L2051-2053
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L2025
L2027
L2028
L2041
L2046
Check that the address is not zero.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L700-702
L729-735
L785-787
L795-802
L760-762
L770-777
L675-680
L834-844
L159-161
L447-463
L1213-1215
L1229-1231
L1377-1379
L1267-1269
L1415-1417
L1246-1248
L1394-1396
L1253-1255
L1401-1403
L1239-1241
L1387-1389
L1353-1363
L1279-1289
L1427-1437
L905-918
L929-940
L920-927
L942-956
L889-896
Remove unused functions.
Pending
#2 Issue
Unused return values (unused-return)
L1803-1808
Ensure that all the return values of the function calls are used.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L1741
L1749
L1738
L1746
L1743
L1751
L1734
L1740
L1748
L1739
L1747
L1742
L1750
L1744
L1752
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L224-226
L232-234
L1810-1812
L1814-1816
L298-302
L1818-1822
L343-347
L363-372
L1036-1038
L1044-1047
L1964-1966
L2006-2010
L2079-2082
L2084-2087
L2089-2091
L2093-2096
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.