KB Chain Info
The cryptocurrency market is paving the way for a better future. The blockchain technology that lies at the foundation of digital assets has been implemented in numerous projects in various fields. With this technology, we have been able to improve various industries and services, reaching a new era of prosperity and development. Bitcoin is not only the prototype of all cryptocurrencies, but also the real driving force behind the entire crypto market. KB Coin goal is not to copy the leading cryptocurrency or compete with it, but to create a new market centered around the creation and education of a community that can use cryptocurrency in business and everyday life.
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.
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 cannot mint new tokens once the contract is deployed.
- The owner cannot burn tokens without any allowances.
- The owner cannot blacklist wallets from transferring tokens.
- The owner cannot update any fee settings in the contract.
- The owner cannot lock the contract or lock functions.
- The owner can update the round closer address.
- The round closer can close the rounds.
Recommendations
To mitigate potential hacking risks, it is advisable for the client to manage the private key of the privileged account with care. We also recommend enhancing the security practices of centralized privileges or roles in the protocol by transitioning to a decentralized mechanism or smart contract-based accounts, such as multi-signature wallets.
Here are some suggestions for the client:
- Consider using multi-signature wallets, such as Gnosis Safe, which require multiple parties to sign off on a transaction before it can be executed, providing an extra layer of security.
- Implement a timelock with a delay of 48-72 hours for privileged operations, allowing time for community awareness.
- Introduce a DAO/Governance/Voting module to increase transparency and user involvement in the project’s decision-making process.
- Consider renouncing ownership after all critical operations are completed, to ensure that no further modifications to the state variables can be made.
Note - This audit report consists of a security analysis of the kbc_Global.sol smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited this contract for the KBGlobal project. Other contracts associated with the project were not audited by our team. We recommend that investors conduct 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
low Issues | 4 findings
Pending
#1 low Issue
Missing events
It is recommended to emit all the critical parameter changes in the contract.
Pending
#2 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
#3 low Issue
Missing zero or dead address check.
It is recommended to check that the address cannot be set to zero or dead address.
Pending
#4 low Issue
Missing visibility.
It is recommended to add ‘public’, ‘private’ or ‘internal’ visibility while declaring a state variable or a mapping in the contract.
informational Issues | 1 findings
Pending
#1 informational Issue
NatSpec Documentation missing.
If you started to comment on your code, also comment on all other functions, variables, etc.