Blue Art Token Info
We are building a metaverse universe that will bring the world of visual arts to the blockchain network. BlueArt; will organize exhibitions on Metaverse with famous names from the painting and animation world. We have implemented an ecosystem that will also create opportunities for new and promising artists to be recognized. Users on the BlueArt platform can buy and sell unique digital items such as artwork, game items and more in the form of Non Fungible Tokens (NFT). The platform offers users a fully featured marketplace that is filtered and sorted using different categories to create a smooth and easy user experience. BlueArt Token; It operates as a BEP20 token on Binance Smart Chain and has a maximum supply of 88 million units. It is technically impossible to increase the supply of BlueArt Token as this feature has been canceled in the smart contract. Maximum Supply; will decrease continuously with regular manual burning.
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.
On-Chain Insights
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 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 cannot be burned
There is no burn function within the contract.
Ownership is not renounced
Contract can be manipulated by owner functions.
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.
Scope of Work
Files and details
This audit covered the following files listed below with a SHA-1 Hash. The Team mentioned above provided us with the files that need to be evaluated.
- Review the specifications, sources, and instructions provided to SolidProof to ensure we understand the smart contract's size, scope, and functionality.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Specification comparison checks whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis determines whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution is analyzing a program to determine what inputs cause each part of a program to execute.
- Based on the established industry and academic practices, recommendations, and research, best practices review smart contracts to improve efficiency, effectiveness, clarity, maintainability, security, and control.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.
Findings and Audit result
low Issues | 6 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.
Pending
#4 low Issue
Missing Error Message
We recommend to put error messages in all require checks to avoid any confusion.
Pending
#5 low Issue
Floating Pragma
The current pragma Solidity directive is “^0.8.2". Contracts should be deployed with the same compiler version and flags that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions.
Pending
#6 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities
medium Issues | 1 findings
Pending
#1 medium Issue
Missing balance check
The transfer functions do not check for the sender's balance which will result in users sending more tokens than their balance and affect the price and supply of the token
Ownership Privileges:- Include/Exclude accounts from fees
- Set charity account address
- Update the fees and it can be set up to 99.99%