Blue Art Token
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.
Owner privileges
Comments
Ownership Privileges:
- Include/Exclude accounts from fees
- Set charity account address
- Update the fees and it can be set up to 99.99%
Audit Scope
This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.
We will verify the following claims:- Correct implementation of Token standard
- Deployer cannot mint any new tokens
- Deployer cannot burn or lock user funds
- Deployer cannot pause the contract
- Overall checkup (Smart Contract Security)
- Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
- Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been modified, intentionally or otherwise, 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.
Functions
public
31
State variables
public
5
Total lines
of code
825
Capabilities
Hover on items
Audit Details
Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.
Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.
medium Issues
Pending
#1 Issue
Missing balance check
L640
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
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L523
L632
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L591-626
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L477
L477
L477
L613
Check that the address is not zero.
Pending
#4 Issue
Missing Error Message
L619
We recommend to put error messages in all require checks to avoid any confusion.
Pending
#5 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 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
Diagrams
Disclaimer
SolidProof.io reports are not, nor should be considered, an âendorsementâ or âdisapprovalâ of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any âproductâ or âassetâ created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etcâ...)
SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.
SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProofâs position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.