Harbor Finance Info

Harbor Finance is a high-performance, gamified DeFi ecosystem that seamlessly merges NFT-based asset structures, sustainable passive income strategies, and immersive financial gameplay. Our mission: to make automated earning not just simple, but genuinely enjoyable. Engineer intricate Yield Items. Harvest $FISH. Collect ongoing incentives. Rise through the ranks as a master-class Fishercat.

Harbor Finance 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.

23.67
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

Select the audit
"Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review"
Contract address
N/A
Network N/A
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2025/05/06
Revision date 2025/05/06

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

Contract is not upgradeable

The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.

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
EarlyTokenRedeemer.sol
  • The DEFAULT_ADMIN_ROLE can grant/revoke all other roles in the system.
  • The DEFAULT_ADMIN_ROLE can set the vesting start date (setStartDate).
  • The DEFAULT_ADMIN_ROLE can set the vesting period length (setPeriodLength).
  • The DEFAULT_ADMIN_ROLE can set the number of vesting periods (setNumberOfPeriods).
  • The DEFAULT_ADMIN_ROLE can deposit vesting tokens into the contract (depositVestingToken).
  • The DEFAULT_ADMIN_ROLE can recover any ERC20 token from the contract (recoverERC20).
  • The REDEEMER_ROLE can redeem tokens on behalf of users (redeemOnBehalf).

Note - This Audit report consists of a security analysis of the Harbor smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited the mentioned contract for the Harbor team. Other contracts associated with the project were not audited by our team. 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

low Issues | 2 findings

Resolved

#1 low Issue
Remove safemath library
EarlyTokenRedeemer.sol
L13
Description

The compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.

Acknowledged

#2 low Issue
Missing REDEEMER_ROLE Assignment in Constructor.
EarlyTokenRedeemer.sol
L44-58
Description

The EarlyTokenRedeemer contract defines a REDEEMER_ROLE, which is required for the crucial redeemOnBehalf function (line 237), but this role is not assigned to any address in the constructor. While the constructor grants DEFAULT_ADMIN_ROLE to the deployer, it fails to grant the REDEEMER_ROLE to anyone. This oversight means that immediately after deployment, the redeemOnBehalf function would be unusable until an admin manually assigns this role. This function is critical for the system's operation as it allows authorized contracts to redeem tokens on behalf of users, which appears to be a core feature given the integration with YieldItemFactory.

informational Issues | 2 findings

Acknowledged

#1 informational Issue
Floating pragma solidity version
EarlyTokenRedeemer.sol
L2
Description

Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.

Acknowledged

#2 informational Issue
Missing emit
EarlyTokenRedeemer.sol
L242-248
L254-260
L266-272
L278-284
Description

It is recommended to emit all the critical parameter changes.