All files under /contracts/ folder except contracts/test, and contracts/layerzero/mocks

All files under /main/src except tUSDC.sol contract

Ledger contract (Verifying Contract for  EIP712 Withdraw Msg)

All code of Orderly Network can be found at https://github.com/OrderlyNetwork. Documentation for the assets provided in the table can be found at https://orderly.network/docs/build-on-evm/smart-contract-overview.

Orderly Network is the permissionless liquidity layer for web3. 

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Execute arbitrary system commands

Retrieve sensitive data/files from a running server, such as:   /etc/shadow, database passwords, blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)

Taking down the application/website (no DDoS)

Direct theft of user funds

Temporary freezing of funds

Injecting/modifying the static content on the target application (persistent), such as:    - HTML injection, - Replacing existing text with arbitrary text, Arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as:  Email, Password of the victim etc.

Smart contract unable to operate due to lack of token funds

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Injecting/modifying the static content on the target application (reflected), such as:  - Reflected HTML injection,  - Loading external site data

Contract fails to deliver promised returns, but doesn't lose value

Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction, such as:  Iframing leading to modifying the backend/browser state (demonstrate impact with PoC)

Taking over broken or expired outgoing links, such as:  Social media handles, etc.

Temporarily disabling user to access target site, such as:  Locking up the victim from login, Cookie bombing, etc.

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

__Reward Calculation for Critical Level Reports__
 
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.   


__Repeatable Attack Limitations__

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. 

__Reward Calculation for High Level Reports__

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:

- A loss of funds involving an attack that does not require any user action
- Private key or private key generation leakage leading to unauthorized access to user funds that results in lost user funds

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.  

__Previous Audits__

Orderly Network has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.

- https://github.com/OrderlyNetwork/Audits 

__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 ](https://immunefisupport.zendesk.com/hc/en-us/articles/16913132495377-Feasibility-Limitation-Standards) which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:

- Smart Contract, Critical
- Smart Contract, High
- Smart Contract, Medium
- Smart Contract, Low
- Web/App, Critical
- Web/App, High
- Web/App, Medium
- Web/App, Low

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules). Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Reward Payment Terms__

Payouts are handled by the Orderly Network team directly and are denominated in USD. However, payments are done in USDT.

Orderly Network

Resources & Documentation