Olympus-logo

Olympus

Olympus is a protocol with the goal of establishing OHM as a crypto-native reserve currency. It conducts autonomous and dynamic monetary policy, with market operations supported by the protocol-owned Olympus Treasury.

Arbitrum
Avalanche
Boba Network
ETH
Fantom
Optimism
Polygon
Defi
DAO
Token
Solidity
Maximum Bounty
$3,333,333
Live Since
06 January 2022
Last Updated
08 November 2024
  • PoC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - Clearinghouse V2
Added on
27 December 2023
Target
Type
Smart Contract - OHM (Arbitrum)
Added on
15 May 2023
Target
Type
Smart Contract - gOHM - (Arbitrum)
Added on
15 May 2023
Target
Type
Smart Contract - gOHM - (Avalanche)
Added on
15 May 2023
Target
Type
Smart Contract - gOHM - (Polygon/MATIC)
Added on
15 May 2023
Target
Type
Smart Contract - gOHM - (Fantom)
Added on
15 May 2023
Target
Type
Smart Contract - gOHM - (Optimism)
Added on
15 May 2023
Target
Type
Smart Contract - gOHM - (Boba Network)
Added on
15 May 2023
Target
Type
Smart Contract - Boosted Liquidity Vault Implementation
Added on
19 April 2023
Target
Type
Smart Contract - Boosted Liquidity Vault Manager
Added on
19 April 2023
Target
Type
Smart Contract - Boosted Liquidity Registry
Added on
19 April 2023
Target
Type
Smart Contract - Kernel
Added on
27 February 2023

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Severity
Critical
Title

Loss of treasury funds

Severity
Critical
Title

Loss of treasury funds

Severity
Critical
Title

Loss of user funds

Severity
Critical
Title

Loss of user funds

Severity
Critical
Title

Loss of bond funds

Severity
Critical
Title

Loss of bond funds

Out of scope

Default Out of Scope and rules

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

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 (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
  • 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
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers