Palm AI
The $PALM token was created on the Ethereum network. It supports the development of the bot, helps keep it the most updated LLM on Telegram and provides a liquid asset to trade.
Owner privileges
Comments
Ownership Privileges
- The owner can start the reward distribution only once.
- The owner can stop the rewards distribution.
- Any arbitrary wallet can update the reward variables in the contract.
- The owner can update multiple reward pools in the contract.
- The owner can withdraw reards from the contract.
- The owner can update the reward per block value in the contract to any arbitrary value excluding zero.
- The owner can update any arbitrary value in the lock period, if the value is set to a excessive number then user will not be able to receive any rewards for a long period of time.
Note - This Audit report consists of a security analysis of the Palm AI Staking 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 Palm AI team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.
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
9
Total lines
of code
914
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)
L901-905
L907-909
Emit an event for critical parameter changes.
Pending
#2 Issue
Floating pragma solidity version.
L674
Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.
Pending
#3 Issue
Missing threshold
L901-905
L907-909
The owner can set any arbitrary value in the locking period, which can lock the user funds from withdrawing the rewards from the contract. It is recommended that there must be a certain threshold where the value cannot be set to an excessive number. Also, in the update reward per block owner can set any number excluding zero, which is not recommended as there must be a certain threshold if the value is set to 1 then the rewards received by the user will be very low.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L328-330
L357-363
L413-415
L423-430
L388-390
L398-405
L303-308
L462-472
L20-22
L531-544
L555-566
L546-553
L568-582
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L81-83
L89-92
L745-747
L749-755
L823-852
L855-878
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.