PYROWORLDnet Info
Welcome to Pyro Token Universe, a groundbreaking blockchain project inspired by the legendary hero Johnny Storm, the Human Torch.PyroToken(PYC) combines innovation, scarcity, and rewards to create a dynamic ecosystem that empowers holders and fuels long-term growth.
Team and KYC Verification
The team has securely submitted their personal information to SolidProof.io for verification.
In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.
TrustNet Score
The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.
Real-Time Threat Detection
Real-time threat detection, powered by Cyvers.io,
is currently not
activated
for this project.
This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks.
For more information, click here.
Security Assessments
Summary and Final Words
No crucial issues found
The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.
Contract owner cannot mint
It is not possible to mint new tokens.
Contract owner cannot blacklist addresses.
It is not possible to lock user funds by blacklisting addresses.
Contract owner cannot set high fees
The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.
Contract cannot be locked
Owner cannot lock any user funds.
Token cannot be burned
There is no burning within the contract without any allowances
Ownership is not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
Contract is not upgradeable
The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.
Scope of Work
This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.
The auditing process consists of the following systematic steps:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.
A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.
Final Words
The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.
Ownership Privileges
- The token owner can update the minimum token swap amount.
- The owner can update the redistribution, weekly rewards, liquidity, marketing fees, and burn rate in the contract.
- The owner can toggle swapping.
- The owner can update the holding transaction limit to not less than 1% of the total supply.
- The owner can update the burn, marketing, nova burn, presale, and liquidity wallet.
- The owner can update the router and pair address.
- The owner can exclude wallets from limits.
- The owner can exclude wallets from fees.
- The owner can enable trading only once.
- The owner can withdraw stuck tokens.
The nova burn will be happened randomly in the contract which can only be happen twice a year which will burn tokens from the nova burn wallet.
Note - This Audit report consists of a security analysis of the Pyrocoin 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 Pyroworld team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 2 findings
Acknowledged
#1 medium Issue
Transfer of tokens without enabling trade.
The trading needs to be enabled by the owner in order for regular users to transfer tokens. On the contrary, the owner can authorize addresses manually and those addresses will be able to trade tokens. This functionality can be exploited in the following way, For example, there is a presale and the wallets used for the presale can be authorized by the owner. All the tokens obtained can be consolidated into a final wallet address and facilitate trading and selling of the acquired tokens, the last wallet address can be authorized.
Resolved
#2 medium Issue
Liquidity is added to externally owned address.
The contract's liquidity is automatically added to the '_liqWallet' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.
low Issues | 7 findings
Resolved
#1 low Issue
Floating pragma solidity version
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.
Resolved
#2 low Issue
Remove safemath library
The compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.
Resolved
#3 low Issue
Missing Visibility
It is recommended to add 'public,' 'private,' or 'internal' visibility during the declaration or initialization of a state variable or a mapping in the contract.
Resolved
#4 low Issue
Unused modifier
It is recommended that the unused code be removed from the contract.
Resolved
#5 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Resolved
#6 low Issue
Missing threshold for minimum swap amount.
The contract allows the owner to arbitrarily update the minimum swap threshold value. This is not recommended, as it lacks predefined minimum and maximum limits. Such limits are essential to prevent unnecessary or excessively frequent swapping, ensuring optimal functionality and avoiding inefficiencies.
Resolved
#7 low Issue
Missing zero or dead address check.
It is recommended to check that the address cannot be zero or dead address.
informational Issues | 2 findings
Resolved
#1 informational Issue
Function that are not used (Dead code).
Remove unsed code
Acknowledged
#2 informational Issue
Missing events arithmetic
It is recommended to emit all the critical parameter changes.