Mantle LSP-logo

Mantle LSP

Mantle Liquid Staking Protocol (LSP) is a permissionless, non-custodial ETH liquid staking protocol deployed on Ethereum L1 and governed by Mantle. Mantle Staked Ether (mETH) serves as the value-accumulating receipt token.

Defi
Staking
Solidity
Maximum Bounty
$500,000
Live Since
28 November 2023
Last Updated
28 November 2023
  • PoC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Added on
Smart Contract - mETH Token L1
28 November 2023
Target
Type
Added on
Smart Contract - Staking
28 November 2023
Target
Type
Added on
Smart Contract - UnstakeRequestsManager
28 November 2023
Target
Type
Added on
Smart Contract - Oracle
28 November 2023
Target
Type
Added on
Smart Contract - OracleQuorumManager
28 November 2023
Target
Type
Added on
Smart Contract - ReturnsAggregator
28 November 2023
Target
Type
Added on
Smart Contract - ConsensusLayerReceiver
28 November 2023
Target
Type
Added on
Smart Contract - ExecutionLayerReceiver
28 November 2023
Target
Type
Added on
Smart Contract - Pauser
28 November 2023
Target
Type
Added on
Smart Contract - mETH Token L2
28 November 2023

Impacts in Scope

Critical
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Critical
Permanent freezing of staked funds
High
Protocol insolvency
High
Theft of unclaimed yield or tokenized staking yield
High
Permanent freezing of unclaimed or tokenized staking yield
High
Acquiring owner/admin rights without contract’s owner/admin action
Medium
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Medium
Unbounded gas consumption
Medium
Susceptibility to frontrunning

Out of scope

Program's Out of Scope information

These impacts are out of scope for this bug bounty program.

All Categories:

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program
  • Any issues identified in Published Audits https://docs.mantle.xyz/meth/security/audits

Blockchain/DLT & Smart Contract Specific:

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks
  • Impact of future improper configuration of contracts that are not deployed
  • Impacts from an assumption of a malicious majority of oracles
  • Best practice recommendations
  • Gas optimization

Prohibited Activities:

  • Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
  • Any testing with pricing oracles or third-party smart contracts
  • Attempting phishing or other social engineering attacks against our employees and/or customers
  • Any denial of service attacks that are executed against project assets
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty