Project overview - USEON

Type ERC20/BEP20
Language Solidity
Request date 2022/07/06
Latest Revision date 2022/07/06

No description provided

Price Chart

Audit Summary

Static analysis Dynamic analysis Symbolic Execution SWC check
Network Binance Smart Chain
License & Compiler MIT / v0.8.9+commit.e5eed63a
Contract address 0xF57a34a3c50E007C8176E1dC19CBfb526cbb7052
No critical issues found The contract does not contain issues of high or medium criticality.
Contract owner cannot mint It's not possible to mint new tokens.
Contract cannot be locked Owner can't 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.
No Issues found.
No Issues found.
No Issues found.
3 Issues found. 0 resolved.
3 Issues found. 0 resolved.
2 Issues found. 0 resolved.

  • Owner
    • can take out contract eth balance with recover function

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)
The auditing process follows a routine series of steps:
  • 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.

Public functions Public state variables Total lines of code Capabilities
95 14 1199

Public functions Public state variables Total lines of code Capabilities
95 14 1199

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.

#1 | Local variables shadowing (shadowing-local)
Severity Location Status
Low UERN.sol: 937 Pending

Rename the local variables that shadow another component.

#2 | Missing Events Arithmetic (events-maths)
Severity Location Status
Low UERN.sol: 997-1001, 1008-1014, 1016-1022 Pending

Emit an event for critical parameter changes.

#3 | Missing Zero Address Validation (missing-zero-check)
Severity Location Status
Low UERN.sol: 1041, 1046 Pending

Check that the address is not zero.

#2 | Functions that are not used (dead-code)
Severity Location Status
Informational UERN.sol: 28-31, 416-424, 593-595, 609-612, 717-720, 708-712, 688-694, 676-683, 699-703, 723-726, 730-734 Pending

Remove unused functions.

#3 | Low level calls (low-level-calls)
Severity Location Status
Informational UERN.sol: 1158-1198 Pending

Avoid low-level calls. Check the call success. If the call is meant for a contract, check for code existence.

#5 | Unused state variables (unused-state)
Severity Location Status
Informational UERN.sol: 671 Pending

Remove unused state variables.

#1 | State variables that could be declared constant (constable-states)
Severity Location Status
Optimization UERN.sol: 978 Pending

Add the `constant` attributes to state variables that never change.

#2 | Public function that could be declared external (external-function)
Severity Location Status
Optimization UERN.sol: 223-225, 231-233, 248-250, 274-277, 282-284, 293-296, 311-319, 333-336, 352-355, 651-654, 660-664 Pending

Use the `external` attribute for functions never called from the contract.


Disclaimer 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. do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etc’...) 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. 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.