Orenium Protocol Info

Orenium is designed to grow with the industry, supporting interoperability and compatibility with popular programming languages. This means developers can seamlessly integrate Orenium into their existing workflows.

Orenium Protocol Logo

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.

42.18
Poor Excellent

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

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xb0Db...03ad
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/02/23
Revision date In progress

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.

Token transfer can be locked

Owner can lock user funds with owner functions.

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:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. 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 can set the max transaction and max wallet amount to any arbitrary number. For example, if it is set to zero then the trading in the contract will be stopped and all the user funds can be locked. Moreover, the owner can also lock the contract by setting an Invalid router address.
  • The Medium issue mentioned in the report will be automatically resolved once the ownership is Renounced.

Note - This Audit report consists of a security analysis of the Orenium 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 Orenium Protocol team. Our team did not audit any other contracts associated with the project. We recommend investors do 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

medium Issues | 1 findings

Pending

#1 medium Issue
Lock of User Funds
OreniumCoin.sol
L531
L535
Description

The owner can completely lock the contract by setting the maximum transaction and wallet amount to zero. If done so, then the users will be unable to transfer their tokens

low Issues | 3 findings

Pending

#1 low Issue
Local variables shadowing
OreniumCoin.sol
L469
L566
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic
OreniumCoin.sol
L504-510
L522-524
L535-537
L539-541
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation
OreniumCoin.sol
L517
L673
Description

Check that the address is not zero.

informational Issues | 2 findings

Pending

#1 informational Issue
Functions that are not used
OreniumCoin.sol
L135-148
L95-97
L99-101
L103-105
L107-112
L125-127
L129-133
L114-116
L118-122
L83-87
L89-93
L75-78
L49-51
L60-65
L45-47
Description

Remove unused functions or implement them if necessary.

Pending

#2 informational Issue
Unused state variables
OreniumCoin.sol
L385
L401
L405
Description

Remove unused state variables.