Smart Contract - EarningsEscrow.sol - 103

Smart Contract - ExchangeStargateV2Adapter.sol - 153

Smart Contract - IDEXIndexAndOraclePriceAdapter.sol - 107

Smart Contract - PythIndexPriceAdapter.sol - 119

Smart Contract - PythOraclePriceAdapter.sol - 76

Smart Contract - AssetUnitConversions.sol - 21

Smart Contract - BalanceTracking.sol - 468

Smart Contract - ClosureDeleveraging.sol - 179

Smart Contract - FundingMultiplierQuartetHelper.sol - 103

Smart Contract - IndexPriceMargin.sol - 273

Smart Contract - LiquidationValidations.sol - 113

Smart Contract - NonceInvalidations.sol - 31

Smart Contract - OraclePriceMargin.sol - 295

Smart Contract - PositionBelowMinimumLiquidation.sol - 142

Smart Contract - PositionInDeactivatedMarketLiquidation.sol - 58

Smart Contract - SortedStringSet.sol - 53

Smart Contract - TradeValidations.sol - 177

Smart Contract - WalletExitAcquisitionDeleveraging.sol - 222

Smart Contract - WalletExitLiquidation.sol - 147

Smart Contract - WalletInMaintenanceAcquisitionDeleveraging.sol - 160

Smart Contract - WalletInMaintenanceLiquidation.sol - 147

__Asset Accuracy Assurance__

Bugs found on assets incorrectly listed in-scope will be considered valid and be rewarded.

__Private Known Issues Reward Policy__

Private known issues, meaning known issues that were not publicly disclosed, are valid for a reward.

__Known Issue Assurance__

IDEX commits to providing Known Issue Assurance to bug submissions through their program. This means that IDEX 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.

__Primacy of Impact vs Primacy of Rules__

IDEX adheres to the Primacy of Impact for all impacts.

Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope. For more information, please see Best Practices: Primacy of Impact 
When submitting a report on Immunefi’s dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.

__Eligibility Criteria__

Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
- On OFACs SDN list 
- Official contributor, both past or present
- Employees and/or individuals closely associated with the project 
- Security auditors that directly or indirectly participated in the audit review

__Responsible Publication__

Whitehats may publish their bug reports after they have been fixed & paid, or closed as invalid, with the following exceptions:
- Bug reports in mediation may not be published until mediation has concluded and the bug report is resolved.

Immunefi may publish bug reports submitted to this audit competition and a leaderboard of the participants and their earnings.

__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.

__Immunefi Standard Badge__

By adhering to Immunefi’s best practice recommendations, IDEX has satisfied the requirements for the [Immunefi Standard Badge](https://immunefisupport.zendesk.com/hc/en-us/articles/15006865432209-The-Immunefi-Standard-Badge).

Paludo0x

Hoverfly9132

marchev

OxSCSamurai

holydevoti0n

https://drive.google.com/file/d/17Di_yuDq20EiDy-W9UtCBnKB6IfxiUbL/view?usp=sharing

IDEX is a high-performance decentralized perpetual swaps exchange. It operates on XCHAIN, an IDEX specific Arbitrum Orbit layer 2. XCHAIN's performance supports gas free and nearly instant settlement of all IDEX transactions. Positions on IDEX are collateralized by USDC bridged into XCHAIN via Stargate's Hydra protocol.

For more information about IDEX please visit https://idex.io/ 




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

Changing details of other users (including modifying browser local storage) without an already-connected wallet interaction and with significant user interaction, such as iframing leading to modifying backend/browser state (must show 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.

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds

Injecting/modifying the static content on the target application without JavaScript (persistent), such as: HTML injection without JavaScript, 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.

Improperly disclosing confidential user information, such as: Email address, Phone number, Physical address, etc.

Subdomain takeover without already-connected wallet interaction

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

Theft of gas

Unbounded gas consumption

Changing non-sensitive details of other users (including modifying browser local storage) without an already-connected wallet interaction and with up to one click of user interaction, such as changing the first/last name or enabling/disabling notifications

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

Redirecting users to malicious websites (open redirect)

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

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as:   Changing registration information, Commenting, Voting, Making trades, Withdrawals, etc.

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet, such as:  Modifying transaction arguments or parameters Substituting contract addresses Submitting malicious transactions

Injection of malicious HTML or XSS through metadata

__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.

__Whitehat Educational Resources & Technical Info__

- Documentation
1) Smart Contracts: https://github.com/idexio/idex-contracts-ikon 
2) API: https://api-docs-v4.idex.io/ 
- Technical education: Technical articles, ReadMe's, whitepaper, etc
1) https://docs.idex.io/ 

__Is this an upgrade of an existing system? If so, which? And what are the main differences?__

No, it is a new system design.

__What ERC20 / ERC721 / ERC777 / ERC1155 token standards are supported? Which are not?__

IDEX supports a single whitelisted ERC20 token as collateral for deposits and withdrawals. Specifically, IDEX deposits and withdrawals are limited to Stargate v2 Hydra-wrapped USDC on XCHAIN.

__What external dependencies are there?__

Stargate v2 and LayerZero v2 provide bridge support for depositing and withdrawing USDC. See ExchangeStargateV2Adapter.sol.
Pyth provides index and oracle pricing. See PythIndexPriceAdapter.sol and PythOraclePriceAdapter.sol.

__Where might whitehats confuse out-of-scope code to be in-scope?__

IDEX has multiple third party integrations and components including the Stargate/Layerzero protocol, Pyth oracle prices, and the Arbitrum Orbit layer 2 settlement network. IDEX specific components to support these integrations, e.g. the index price adapter contracts, are in scope, while any issues or exploits with the third party systems themselves (e.g. a bridge exploit) are out of scope.

__Are there any unusual points about your protocol that may confuse whitehats?__

IDEX employs a hybrid design where the API, order books, and the matching engine operate off chain while smart contracts custody funds and verify operations. As a result, nearly all contract functionality is permissioned. Aside from standard owner and admin wallets, a designated dispatcher wallet, also operated by IDEX, is solely responsible for submitting trade settlements, liquidations, funding payments, etc. The use of a single dispatcher wallet guarantees the settlement sequence of off-chain actions within the contracts.

__Where do you suspect there may be bugs?:__

There are a few key areas that deserve extra attention.

_Unauthorized access to permissioned components_

- Admin access (both onchain admin functions and offchain admin system access)
- Upgrade mechanism exploits
- Access to user wallet delegated key
- Ability to place orders, cancel orders, or withdraw funds without wallet signature

_Trading and smart contract rules violations_

- Trade settlement violating the terms of the wallet-authorized orders
- Margin requirement violations allowing wallets to exceed allowed leverage
- Balance tracking errors leading to loss of funds

__What is the test suite setup information?__

- See the GitHub [README](https://github.com/idexio/idex-contracts-ikon/?tab=readme-ov-file#usage) for test suite operation.

 __Public Disclosure of Known Issues__

Bug reports covering previously-discovered bugs (listed below) are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to “fix”, necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk. 

- Issues resulting from index or oracle price manipulation.
- Issues due to very low pricing.
- Loss of unrealized profits during wallet [exit withdrawals](https://github.com/idexio/idex-contracts-ikon?tab=readme-ov-file#wallet-exits).
- Loss of withdrawn value due to old oracle pricing during [exit withdrawals](https://github.com/idexio/idex-contracts-ikon?tab=readme-ov-file#wallet-exits).
- Issues related to the USDC proxy implementation being switched to something malicious.
- EarningsEscrow.sol contract replay prevention mechanism only includes the contract’s address.
- Behavior within the stated design intent as defined in documentation.
- See the previously completed audits for identified issues.

__Previous Audits__

IDEX’s completed audit reports can be found at https://github.com/idexio/idex-contracts-ikon/tree/main/audits. 
Any unfixed vulnerabilities  mentioned in these reports are not eligible for a reward.

- 0xMacro A-1
- 0xMacro B-1
- PeckShield

The following reward terms are a summary, for the full details read our [IDEX Audit Competition Reward Terms](https://immunefisupport.zendesk.com/hc/en-us/articles/27112340939665-IDEX-Audit-Competition-Reward-Terms)

The reward pool will be entirely distributed among participants. The size depends on the bugs found:
If no High or Critical severity bugs are found the reward pool will be **$30,000 USD**
If one or more High or Critical severity bugs are found the reward pool will be **$45,000 USD**

For this audit competition, duplicates and private known issues are valid for a reward.

Rewards are distributed according to the impact of the vulnerability based on the Immunefi [Vulnerability Severity Classification System V2.3](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/). 

__Reward Payment Terms__

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

Rewards will be distributed all at once based on Immunefi’s distribution formula after the event has concluded and the final bug reports have been resolved.

IDEX’s up to date codebase can be found at https://github.com/idexio/idex-contracts-ikon/tree/901b1d30ce77f8704867546b500e3cee7c89c59b

NAME	EARNINGS	TOTAL VALID BUGS	INSIGHTS	HIGH
1 Paludo0x	$40,500	1	0	1
2 Hoverfly9132	$1,350	0	1	0
3 marchev	$1,350	0	1	0
4 OxSCSamurai	$1,350	0	1	0
5 holydevoti0n	$450	0	1	0

Audit Comp | IDEX

Status

Status