SilvaFinance Info
An Investment, Multi Currency and Multi Functional Online Platform Based on Blockchain Technology.
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
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 can mint
It is possible to mint new tokens.
Contract owner cannot blacklist addresses.
It is not 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.
Contract cannot be locked
Owner cannot lock any user funds.
Token can be burned
There is a function to burn tokens in the contract.
Ownership is not renounced
Contract can 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.
- The owner owns the private key of the uint256->uint160->address (0x62336122684185cbcb91fb2942d324ed2a223f68). That means, that the "baseSign" function in the SafeMath library will return true, if that address calls any function where this function is called.
- baseSign is used in
- the onlyOwner modifier
- that means also when the ownership is renounced this address is still able to call any functions with the "onlyOwner" modifier
- _approve function
- that means when this address above calls the approve function he is able to increase the allowance of any other addresses that holds tokens of the contract. This causes that when you are investing in this token you can lose all your funds when the owner approves your address. We highly recommend you to be aware of this.
- Alleviation of the owner:
- BaseSign is a back wallet dev that we anticipate that if the SILVA wallet dev is hacked it will still be safe. To be sure we are displaying the office address on the website
- PT SILVA NETWORK FINANCE <== Name My physical company
- https://ptp.ahu.go.id/sertifikat?id=687d4b8547431b50667e1cd92dfae203:4248a30e9e011acc3becc8072f6b6f96 <== this verify By Indonesia Goverment
- Alleviation of the owner:
- that means when this address above calls the approve function he is able to increase the allowance of any other addresses that holds tokens of the contract. This causes that when you are investing in this token you can lose all your funds when the owner approves your address. We highly recommend you to be aware of this.
- the onlyOwner modifier
- baseSign is used in
- The owner is able to
- set the fees above 100%
- lock user funds by setting the max tx amount to 0
- There is a burnwallet but the owner is able to set the burn address.
- That causes that the owner is able to set a private key wallet to get the "burned tokens" instead of real burning it.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 1 findings
Pending
#1 medium Issue
Regaining ownership
The owner is able to lock the ownership to set the "_previousOwner" variable. That means, that this variable is set all the time and can only be reset by setting calling the lock again. In this case the owner can regain the ownership after transferring the ownership to another address by calling the unlock function. Beware of it.
low Issues | 3 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
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 | 1 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.