Prepared by:
HALBORN
Last Updated Unknown date
Date of Engagement: January 30th, 2025 - February 7th, 2025
Summary
100% of all REPORTED Findings have been addressed
All findings
4
Critical
0
High
0
Medium
0
Low
1
Informational
3
Table of Contents
1. Introduction
The Vault engaged Halborn to conduct a security assessment on their Solana Validator program beginning on January 30th, 2025 and ending on February 7th, 2025. The security assessment was scoped to the smart contracts provided in the GitHub repository liquid-unstaker, commit hashes, and further details can be found in the Scope section of this report.
The Vault team is releasing Liquid Unstaker, a protocol that relies on liquidity providers to supply SOL to a liquidity pool, enabling users to unstake instantly without waiting for the stake deactivation period. In return, liquidity providers earn fees for fronting liquidity and staking rewards.
2. Assessment Summary
Halborn was provided 7 days for the engagement and assigned one full-time security engineer to review the security of the Solana Programs in scope. The engineer is a blockchain and smart contract security expert with advanced smart contract hacking skills, and deep knowledge of multiple blockchain protocols.
The purpose of the assessment is to:
Identify potential security issues within the codebase.
Verify that the funds of the liquidity providers are safe of any leakage
Validate that the platform is not vulnerable to arbitrage
Verify that the fees are properly calculated and distributed fairly
In summary, Halborn identified some improvements to reduce the likelihood and impact of multiple risks, which has been addressed by the The Vault team. The main one was the following:
Consider the case where an staking account has less lamports than what the user is requiring to withdraw
3. SCOPE
- src/error.rs
- src/fee.rs
- src/instructions/create_or_update_token_metadata.rs
4. Findings Overview
| Security analysis | Risk level | Remediation |
|---|---|---|
| Potential loss of funds when withdrawing from validator removal stake accounts | Low | Solved - 02/07/2025 |
| Unstaking funds steal in case of manual funds approval | Informational | Solved - 02/07/2025 |
| Incorrect cap validation in deposit_sol entry point | Informational | Solved - 02/10/2025 |
| Unused is_active boolean in StakeAccountInfo | Informational | Solved - 02/07/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.
Table of Contents
// Download the full report
Liquid Unstaker
* Use Google Chrome for best results
** Check "Background Graphics" in the print settings if needed