So Noisy Info
We propose the SoNoisy Platform as a solution to these problems. The mission of the Platform is to give everyone the freedom to distribute, monetize, and stream any audio content.
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.
TrustNet DataPulse
0x2Ed7204Ec9fD77D3758Dc7d3c5de4c9b510ad72B
Data provided by We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!
We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.
In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.
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 renounced
Contract cannot be manipulated by owner functions.
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 owner can update the market pair address.
- The owner can exclude wallets from wallet limits, transaction limits, and fees.
- The owner can enable trading only once.
- The marketing wallet address can manually swap tokens.
- The owner can set buy and sell fees of not more than 20%.
- The owner can set any arbitrary value in the max wallet and transaction amount, including zero.
- The owner can enable/disable wallet limits.
- The owner can set any address as a marketing wallet address.
- The owner can enable/disable swapping.
- The marketing wallet address can enable/disable swapping limits in the contract.
- The owner can claim the contract ETH in his wallet.
- The owner can change the router address in the contract.
- The marketing wallet address will receive the ETH once the swapping is completed.
The ownership of the token is renounced. Hence, the owner cannot change the above contract settings.
Note - This Audit report consists of a security analysis of the So Noisy 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 So Noisy 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 | 4 findings
Resolved
#1 medium Issue
The owner can lock tokens.
The owner can set any arbitrary value in the max wallet and transaction amount, including zero. This can lock the transfer functionality of the contract. If the amount is set to 0, then un-whitelisted users will not be able to transfer any tokens. There must be a threshold amount where the max wallet and transaction amount cannot get below that number.
Resolved
#2 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
#3 medium Issue
Liquidity is added to externally owner account.
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.
Resolved
#4 medium Issue
Missing 'require' check (Potential Honeypot)
The owner can set any address as the marketing wallet address. If the owner sets the contract address that cannot receive ETH, the transactions will fail, and the ETH will be stuck in the contract, which is not recommended. Add a 'require check that the marketing wallet address cannot be set as a contract address.
low Issues | 6 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 because if it is then the ETH sent to the contract will never be received.
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.
Pending
#5 low Issue
Missing visibility
It is recommended to add visibility during the declaration or initialization of a state variable or a mapping.
Pending
#6 low Issue
Missing 'require' error message.
No error message is present in the check. It is recommended to add an error message while using the 'require' check inside the function.
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Pending
#2 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 2 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Unused state variables (unused-state)
Remove unused state variables.