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.

86.18
PoorExcellent

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.

TrustNet DataPulse

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0xA7fB...15F6
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/10/26
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 can set high fees

Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.

Token transfer can be locked

Owner can lock user funds with owner functions.

Token cannot be burned

There is no burn function within the contract.

Ownership is not renounced

Contract can be manipulated by owner functions.

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.


  • Liquidity will be send to the owner
  • owner is able to
    • take out tokens
    • take out bnb
    • set fees without any limitation
      • It can be set above 100%
        • We recommend you to restrict the setting to a certain value for every fees
    • lock user funds by
      • setting "maxSellTransactionAmount" to 0

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
Owner can take out native tokens
ORBN.sol
L1734
Description

We recommend you to prevent passing the own contract address to the function. Otherwise the owner is able to take out native tokens.

low Issues | 3 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
ORBN.sol
L1373
L1373
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
ORBN.sol
L1824-1831
L1833-1840
L1842-1844
L1963-1965
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
ORBN.sol
L1730
L1846
Description

Check that the address is not zero.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
ORBN.sol
L1760
Description

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

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
ORBN.sol
L855-857
L863-865
L880-882
L906-909
L925-928
L943-957
L971-974
L990-998
L1197-1199
L1205-1208
L1226-1228
L1230-1235
L1237-1239
L1243-1245
L1410-1412
L1438-1440
L1452-1454
L1619-1636
L1663-1708
L1730-1732
L1824-1831
L1833-1840
L1842-1844
L1846-1848
L1926-1930
L1939-1941
L1943-1947
L1949-1955
L1957-1961
L1963-1965
L1978-1983
L1997-1999
L2001-2003
L2005-2007
L2009-2011
L2061-2064
Description

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

informational Issues | 2 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
ORBN.sol
L699-701
L1472-1478
L2192-2194
L593-596
L647-650
L629-632
L611-614
L665-668
L488-491
L548-551
L473-476
L533-536
L518-521
L563-566
L503-506
L409-418
L369-371
L435-444
L386-395
L240-246
L282-287
L294-299
L265-275
L253-258
L191-193
L177-179
Description

Remove unused functions.

Pending

#2 informational Issue
Missing error messages
ORBN.sol
-
Description

Add missing error messages to the require statements