CryptoFy Coin Info
cryptofy coin is a decentrlized metaverse coin that bridge the gap between the virtual world and the real world by aiding seamless, secured and fast transaction. Its very economical and has fast processing power per seconds powered by the cryptofy smart chain (CSC). As we develop and grow, cryptofy coin plans to expand into additional industries, such as the energy agricultural, and oil and gas sectiors. Cryptofy coin is the game-changer
Overall Score
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.
TrustNet DataPulse
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 can blacklist addresses
It is possible to lock user funds by blacklisting addresses.
Contract owner can set high fees
Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
Token transfer can be locked
Owner can lock user funds with owner functions.
Token cannot be burned
There is no burn function within the contract.
Ownership is not renounced
Contract can be manipulated by owner functions.
Scope of Work
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 owner can set the market pair address.
- The owner can exclude wallets from transaction limits.
- The owner can exclude wallets from fees.
- The owner can set any arbitrary value in buy and sell tax where the amount can be more than 25% or to 100%.
- The owner can update the distribution settings of liquidity, marketing, and team share.
- The owner can set any arbitrary value in the max transaction amount, which can lock the transfer of tokens.
- The owner can enable/disable the wallet limit.
- The owner can exempt wallets from the max hold wallet limit.
- The owner can set any arbitrary value in the max wallet limit, including zero.
- The owner can set any arbitrary value in the minimum swap amount.
- The owner can update the marketing, development wallet address.
- The owner can enable/disable swapping.
- The owner can set any arbitrary value in the swap and liquify limit.
- The owner can update the dev address.
- The owner can set any arbitrary value in the block ban.
- The owner can blacklist wallets from transferring of tokens.
- The owner can update the router version.
- The owner can enable/disable trading.
Note - This Audit report consists of a security analysis of the CryptoFy coin 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 CryptoFy coin 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 | 3 findings
Pending
#1 medium Issue
Liquidity is transferred to an EOA
The contract's liquidity is automatically added to the 'owner' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.
Pending
#2 medium Issue
Owner is able to lock user funds
The owner can set any arbitrary value in the max wallet and max transaction limit, which can lock the transfer function, and the users will not be able to transfer any funds to any wallet if the value is set to zero. Moreover, the owner can start/stop trading anytime, which will lock user funds. Similarly, the owner can manually add wallet addresses to the 'bots' list, which is a transfer blacklist. Thus, the wallets in this list will not be able to transfer their funds.
Pending
#3 medium Issue
Tax can be set upto 100% or more
The owner can adjust the buy and sell tax to 100% or more. If the tax is set to 100%, it implies that the total amount of tokens you intend to buy/sell will be sent to the address specified as the recipient in the contract. This implies that the recipient will never have the intended amount of tokens in their wallet as it has all been used up in paying the tax.
low Issues | 4 findings
Pending
#1 low Issue
Local variables shadowing
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation
Check that the address is not zero.
Pending
#4 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.
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant
Add the `constant` attributes to state variables that never change.
Pending
#2 optimization Issue
Public function that could be declared external
Use the `external` attribute for functions never called from the contract.
informational Issues | 4 findings
Pending
#1 informational Issue
Functions that are not used
Remove unused functions.
Pending
#2 informational Issue
Unused state variables
Remove unused state variables.
Pending
#3 informational Issue
Uninitialized state variables
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.
Pending
#4 informational Issue
Unused return values
Ensure that all the return values of the function calls are used.
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:
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.