Orderly Network
Bounty Range
$1,000 - $100,000
external program
Orderly Network
Orderly Network is the permissionless liquidity layer for web3.
For more information about Orderly Network, please visit https://orderly.network/
Orderly Network provides rewards in USDT on Ethereum, denominated in USD.
Smart Contract
| Severity | Reward |
|---|---|
| Critical | Max: $100,000 / Min: $25,000 |
| High | Max: $20,000 / Min: $5,000 |
| Medium | Flat: $5,000 |
| Low | Flat: $1,000 |
Websites and Applications
| Severity | Reward |
|---|---|
| Critical | Max: $10,000 / Min: $7,500 |
| High | Flat: $5,500 |
| Medium | Flat: $4,000 |
| Low | Flat: $1,000 |
For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 100,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 25,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of $5,000 to $20,000 depending on the funds at risk, capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 48h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.
For critical web/apps bug reports will be rewarded with $10,000, only if the impact leads to:
All other impacts that would be classified as Critical would be rewarded a flat amount of $7,500. The rest of the severity levels are paid out according to the Impact in Scope table.
Payouts are handled by the Orderly Network team directly and are denominated in USD. However, payments are done in USDT.
Orderly Network has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
Proof of concept is always required for all severities:
All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.
Orderly Network provides rewards in USDT. For more details about the payment process, please view the Rewards by Threat Level section further below.
Orderly Network adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page.
No KYC information is required for payout processing.
Category 3: Approval Required
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 regarding: