Oceanic Horrors Info

www.oceanic-horror.com

Oceanic Horrors is a horror game survival. It is an open world where you can find objects, create others, build your house, and with your team, you can even make a city. Obtain special items, create them, and sell them on the secondary market. The game will be available for PC and in 2024 for mobile.

Overall Score
80.15
Poor Excellent
Oceanic Horrors Logo

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

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x7431...F353
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/11/01
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.

Contract cannot be locked

Owner cannot 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.

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 transfer the contract's ETH to the treasury wallet address.
  • The owner can withdraw tokens to any wallet.
  • The owner can set the treasury wallet address.
  • The owner can manually swap tokens.
  • The owner can set the reflection and treasury tax of not more than 20%.
  • The owner can enable/disable swapping.
  • The owner can exclude multiple wallets from fees.
  • This contract contains the functionality where the ETH will be transfer to the treasury wallet address once the swapping is completed.

Note - This Audit report consists of a security analysis of the Oceanic Horrors 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 Oceanic Horrors team. Other contracts associated with the project were not audited by our team. We recommend investors to 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

optimization Issues | 2 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function).
Redis.sol
L374-376
L378-380
L382-384
L386-388
L390-392
L394-400
L402-407
L409-415
L417-431
Description

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

Pending

#2 optimization Issue
State variables that could be declared constant (constable-states)
Redis.sol
L271-273
Description

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