UBi
UBi is a platform for all users/influencers/ creators that can freely express themselves on our platform. Many content creators use different social media platforms adding value to web2 platforms. This token is a deflationary token through which the total supply of the token will decrease at a certain burnrate. for more details refer to the tokenomics of this project : https://ubionline.gitbook.io/ubi/tokenomics.
Owner privileges
Comments
Ownership Privileges
- The owner can blacklist wallets.
- The owner can whitelist addresses from burn fees.
- The owner can change the burn rate which will be used to update the burn fee.
- The owner can update the burn fees which will be smaller than the previous fees.
Note - This Audit report consists of a security analysis of the UBi Token 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 UBi team, other contracts associated with the project were not audited by our team. We recommend investors to do their own research before investing.
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
2
Total lines
of code
642
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.
low Issues
Pending
#1 Issue
Floating Pragma Solidity Version
L4
It is recommended to add the constant version of solidity as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.
Pending
#2 Issue
Variable visibility missing
L570
It is recommended to add private visibility to the variables that start with an underscore. Here, mapping is created without any visibility in the blacklist contract.
Pending
#3 Issue
Missing Events Arithmetic (events-maths)
L597-601
L607-609
Emit an event for critical parameter changes.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L124-126
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L185-187
L193-196
L263-265
L271-273
L288-290
L295-297
L302-304
L337-341
L378-382
L398-407
L572-575
L577-580
L597-601
L603-605
L607-609
Use the `external` attribute for functions never called from the contract.
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.