Is HOME Safe? Smart Contract Security Analysis

Security Checklist

3/5 checks passed

Contract VerifiedPass

Ownership RenouncedFail

No Mint FunctionPass

Liquidity LockedFail

Not a ProxyPass

Audit History

2 audits on record

Jul 2352

Every audit run adds a dated snapshot — history is append-only and cannot be edited.

Audit Summary

This report covers a security review of the provided Solidity source code. It is important to note that the submitted code consists solely of LayerZero v2 interface definitions. The actual implementation code for the 'HomeCanonical' contract, which is the target of this audit, was not provided. Consequently, a comprehensive security assessment of the contract's logic, state management, access control, and potential vulnerabilities could not be performed. The findings below highlight the critical limitation of this audit due to the absence of the core contract implementation.

Final Recommendation: It is critically important to provide the complete and correct Solidity source code for the 'HomeCanonical' contract to enable a thorough security audit. Without the full implementation, any assessment of the contract's security posture is impossible, leaving it vulnerable to unknown risks. Once the full source code is available, a comprehensive audit should be conducted to identify and mitigate potential vulnerabilities related to logic, access control, economic models, and upgrade mechanisms.

Category Ratings

TechnicalLow

8/10

The technical review was severely limited as only LayerZero v2 interface definitions were provided, not the implementation code for the 'HomeCanonical' contract. This prevents any assessment of the contract's internal logic, state variables, or specific vulnerability patterns (e.g., r

GovernanceHigh

2/10

The economic and governance aspects of the 'HomeCanonical' contract could not be evaluated due to the absence of its implementation code. This means no assessment of tokenomics, fee structures, incentive mechanisms, or governance decision-making processes (7.5 Governance) was possible. Cro

UpgradesMedium

6/10

The upgradeability mechanisms (7.7 Upgrades) of the 'HomeCanonical' contract could not be assessed as its implementation code was not provided. Without the contract's source, it is impossible to determine if it uses a proxy pattern (e.g., UUPS, Transparent), if it has an owner-control

LP Distribution

Top-1 Unlocked Holder98.7%

Top-3 Unlocked100.0%

What Raised This Score

7 factors

Ownership NOT renounced — strong Multisig (4-of-7)
Top-10 concentration > 30% (89.2% total → 48.9% effective; 22.0% in EOAs, 67.1% in contracts — moderate)
Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
Liquidity < $50k ($44,128 across 3 pairs — thin market)
LP top1 unlocked holder = 98.7% (independent LP — depth risk)
LP top3 unlocked holders = 100.0% (independent LP — depth risk)
1 Critical finding(s) from audit

Each factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed

Security Findings

4 total

1 Critical 3 Info

C-01CriticalUnresolved

Missing Core Contract Implementation

The provided source code consists solely of LayerZero v2 interface definitions (e.g., `ILayerZeroEndpointV2`, `ILayerZeroReceiver`). The actual implementation code for the `HomeCanonical` contract, which is the stated target of this audit, was not included. This prevents any meaningful security analysis of the contract's logic, state variables, access control, and potential vulnerabilities like reentrancy, integer overflows, or specific business logic flaws.

Recommendation: Provide the complete and verified Solidity source code for the `HomeCanonical` contract, including all its dependencies and libraries, to enable a comprehensive security audit.

I-01InformationalUnresolved

Reliance on LayerZero v2 Protocol Security

The `HomeCanonical` contract, as indicated by the provided interfaces, relies heavily on the LayerZero v2 protocol for cross-chain messaging. The security and integrity of the `HomeCanonical` contract will be directly dependent on the robustness and security of the underlying LayerZero v2 infrastructure, including its endpoints, message libraries, and relayers. Any vulnerabilities or compromises within the LayerZero v2 protocol could potentially impact the `HomeCanonical` contract.

Recommendation: While the LayerZero v2 protocol is designed for security, it is crucial for the project team to stay informed about any security updates, audits, or known vulnerabilities related to LayerZero. Implement robust monitoring for cross-chain operations and consider circuit breakers for extreme scenarios.

I-02InformationalUnresolved

Unassessable Access Control Mechanisms

Without the implementation code for `HomeCanonical`, it is impossible to assess the access control mechanisms (7.3 Access Control) governing critical functions. This includes identifying privileged roles (e.g., owner, admin, governor), verifying proper authorization checks (e.g., `onlyOwner`, `require(msg.sender == _someRole)`), and ensuring that sensitive operations are adequately protected against unauthorized execution.

Recommendation: Once the full contract code is available, a detailed review of all access control patterns should be conducted. Ensure that the principle of least privilege is applied, and that multi-signature wallets are used for critical administrative functions where appropriate.

I-03InformationalUnresolved

Unverified Economic and Governance Model

The economic model (7.4 Economic) and governance structure (7.5 Governance) of the `HomeCanonical` contract cannot be verified or audited without its full implementation. This includes aspects such as fee collection, reward distribution, tokenomics, and any on-chain voting or administrative processes. Unforeseen economic incentives or governance flaws could lead to instability or manipulation.

Recommendation: Upon receiving the full contract code, a thorough review of the economic and governance logic should be performed. This includes simulating various scenarios to identify potential attack vectors or unintended consequences related to incentives, fees, and decision-making processes.

Is HOME Safe? HOME