Goldivault Diff - Goldilocks


Prepared by:

Halborn Logo

HALBORN

Last Updated 04/01/2025

Date of Engagement: March 21st, 2025 - March 24th, 2025

Summary

100% of all REPORTED Findings have been addressed

All findings

6

Critical

0

High

0

Medium

0

Low

1

Informational

5


1. ASSESMENT SUMMARY

The team at Halborn assigned a full-time security engineer to assess the security of the smart contracts. The security engineer is a blockchain and smart-contract security expert with advanced penetration testing, smart-contract hacking, and deep knowledge of multiple blockchain protocols.

The purpose of this assessment is to:

    • Ensure that smart contract functions operate as intended.

    • Identify potential security issues with the smart contracts.

No major issues were identified.

2. SCOPE

REPOSITORY
(a) Repository: goldilocks-core
(b) Assessed Commit ID: 0222634
(c) Items in scope:
  • Goldivault4626.sol
  • Goldivault.sol
  • PointsGoldivault.sol
Out-of-Scope: Third party dependencies and economic attacks.
Remediation Commit ID:
Out-of-Scope: New features/implementations after the remediation commit IDs.

3. Findings Overview

Security analysisRisk levelRemediation
Usage of direct approve callsLowRisk Accepted
Unlocked pragma compilerInformationalSolved - 03/28/2025
Misleading _unstakableYT logicInformationalSolved - 03/28/2025
Duplicated deposit logicInformationalSolved - 03/27/2025
Missing NonReentrant protectionInformationalSolved - 03/27/2025
Consider using named mappingsInformationalSolved - 03/28/2025

Halborn strongly recommends conducting a follow-up assessment of the project either within six months or immediately following any material changes to the codebase, whichever comes first. This approach is crucial for maintaining the project’s integrity and addressing potential vulnerabilities introduced by code modifications.

// Download the full report

Goldivault Diff

* Use Google Chrome for best results

** Check "Background Graphics" in the print settings if needed