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 April 2024
  • PoC required

Submit a Bug

Rewards by Threat Level

Smart Contract
Critical
USD $3,333,333
Websites and Applications
Critical
USD $3,333,333

This is a Custom Program, governed by OlympusDAO. The program is subcategorized into four tiers, with only the below impacts considered for a reward:

  • Tier 1: For bugs/exploits which would lead to a loss of bond funds or a loss of user funds, a reward amount equal to the potential loss of funds up to USD 333 333 (paid in OHM) is provided.

  • Tier 2: For bugs/exploits which would lead to a loss of treasury funds, a reward amount equal to the potential loss of funds up to __USD 3,333,333 __(paid in OHM) is provided.

  • Tier 3: For bugs/exploits which would lead to an incorrect rebase amount, a reward amount equal to the potential loss of funds up to USD 33,333 (paid in OHM) is provided.

  • Tier 4: The Bug Bounty Management team may from time to time, at its discretion, issue an award of up to $16,942.00 for submissions which do not qualify for bounties under other tiers, but which the team feels nonetheless are high effort, high quality, and of material use in improving Olympus’ security. Note that this bounty is not available to Olympus contributors, who should contact the Bug Bounty Management team directly for a bounty if they have found a bug or inefficiency that is outside of their mandate as a contributor. Further note that this bounty will not be awarded regularly. It is meant only for extremely high quality submissions which have significant material impacts to Olympus. No person submitting a bounty should assume that they are entitled to this or will be awarded it, as the bar to qualify for it will be very high.

For vulnerabilities of websites and applications, only bugs that lead to direct financial damage listed in the Impacts in Scope are accepted and are categorized as critical. All others are not accepted. An example of an acceptable vulnerability in this category would be https://rekt.news/badger-rekt/

Bugs that have been previously disclosed, either publicly or in an earlier bug submission, are ineligible for a reward.

Payouts are handled by the Olympus DAO directly and are denominated in USD, under the terms set out in OIP-38. However, payouts are done in OHM.

Reward Payment Terms

Payouts are handled by the Olympus team directly and are denominated in USD. However, payments are done in OHM

The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.

Program Overview

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.

For more information about Olympus, please visit https://www.olympusdao.finance/

This bug bounty program is focused on their smart contracts and app and is focused on preventing:

  • Loss of treasury funds
  • Loss of user funds
  • Loss of bond funds

This bug bounty program is managed by OlympusDAO under the provisions of OIP-38, an extension of OIP-17 and OIP-34. Note that this bounty is not available to Olympus Contributors, who should submit via the Olympus Discord page found here.

Olympus provides rewards in OHM, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.

Responsible Publication

Olympus adheres to category 3 - Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.

Primacy of Impact vs Primacy of Rules

Olympus adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page.

Proof of Concept (PoC) Requirements

A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.

Known Issue Assurance

Olympus commits to providing Known Issue Assurance to bug submissions through their program. This means that Olympus will either disclose known issues publicly, or at the very least, privately via a self-reported bug submission.

In a potential scenario of a mediation, this allows for a more objective and streamlined process, in order to prove that an issue is known. Otherwise, assuming the bug report is valid, it would result in the report being considered as in-scope, and due a reward.

Previous Audits

A full list of Olympus completed audit reports can be accessed below. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.

Feasibility Limitations

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.

Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.

Immunefi Standard Badge

By adhering to Immunefi’s best practice recommendations, Olympus has satisfied the requirements for the Immunefi Standard Badge.

KYC not required

No KYC information is required for payout processing.

Prohibited Activities

Default 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 testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
  • 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
  • Any other actions prohibited by the Immunefi Rules

Feasibility Limitations

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.

Total paid
260.5k
Med. Resolution Time
12 hours
Total Assets in Scope
35