Lendvest Smart Contracts: Program info

IN SCOPE CONTRACTS

Critical

• LVLidoVault — src/LVLidoVault.sol
• LVLidoVaultUtil — src/LVLidoVaultUtil.sol
• LVLidoVaultUpkeeper — src/LVLidoVaultUpkeeper.sol

High

• LiquidationProxy — src/LiquidationProxy.sol
• VaultLib — src/libraries/VaultLib.sol

Medium

• LVToken — src/LVToken.sol

IN SCOPE CRE (Chainlink Runtime Environment)

Feat-integrate-chainlink-cre (branch):

• cre-workflows/workflow/main.ts — Chainlink workflow definition (TypeScript)
• cre-workflows/workflow/config.json — Configuration for testnet deployment
• cre-workflows/workflow/config.production.json — Configuration for mainnet deployment
• cre-workflows/workflow/workflow.yaml — Workflow metadata and settings
• cre-workflows/project.yaml — Project configuration
• src/LVLidoVaultUtil.sol — Contains checkUpkeep() and performUpkeep()
• src/LVLidoVaultUpkeeper.sol — Contains closeEpoch() for taskId=2

KNOWN ISSUES

https://github.com/Lendvest/lendvest-smart-staking/blob/main/KNOWN_ISSUES.md

OUT OF SCOPE CONTRACTS

• test/* — Test files
• script/* — Deployment scripts
• src/LVLidoVaultReader.sol — View-only reader (no state changes)
• src/LVLidoVaultUtilRescue.sol — One-time emergency contract
• src/UpkeepAdmin.sol — Admin utilities
• src/interfaces/* — Interface definitions

OUT OF SCOPE Attack Vectors

• Privileged Access: Attacks requiring leaked private keys, owner access, or forwarder access
• Consensus Attacks: 51% attacks, block reorganizations
• External Protocol Bugs: Ajna, Morpho Blue, Aave V3, Lido, Chainlink vulnerabilities
• Known MEV: Sandwich attacks, arbitrage, front-running (unless novel impact)
• Social Engineering: Phishing, social manipulation
• Infrastructure: DDoS attacks, physical access requirements
• External Events: Oracle data errors not caused by Lendvest code, stETH depeg events

• Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
• Make every effort not to damage or restrict the availability of products, services, or infrastructure
• Avoid compromising any personal data, interruption, or degradation of any service
• Don’t access or modify other user data, localize all tests to your accounts
• Perform testing only within the scope
• Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
• Don’t spam forms or account creation flows using automated scanners
• In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
• Don’t break any law and stay in the defined scope
• Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
• All communication regarding the program must take place exclusively through the HackenProof platform. Contacting the project team directly through support channels, social media, or any other external communication channels is strictly prohibited. Researchers who violate this rule may be disqualified from the program and may face account suspension.

• Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
• No vulnerability disclosure, including partial is allowed for the moment.
• Platform-Only Disclosure: Disclosure is only possible through the HackenProof Disclosure function.
• Researchers may request disclosure (Limited or Full) within the report ticket;
• We reserve the right to approve, redact, or deny disclosure requests at our sole discretion.
• Mutual Required: Any publication requires explicit mutual agreement. Reports must remain Private until the status is officially changed to "Public" on the HackenProof platform by the team.

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability.
• Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
• You must not be a former or current employee of us or one of its contractor.
• ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded).
• Provide detailed but to-the point reproduction steps.
• AI-generated reports without runable PoC are not accepted under this program.