Elixir Protocol
Elixir is building the industry’s decentralized, algorithmic market making protocol. Through the Elixir Protocol, anyone will be able to passively supply liquidity to orderbook pairs on spot and perp DEXes across the space, earning subsidized APYs from existing long term liquidity incentive programs offered by exchanges.
PoC required
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD $250,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 $75,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
Repeatable Attack Limitations
- If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attacks within the first hour 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 considered at the full amount of funds at risk, capped at the maximum high reward. This is to incentivize security researchers to uncover and responsibly disclose vulnerabilities that may have not have significant monetary value today, but could still be damaging to the project if it goes unaddressed.
- In the event of temporary freezing, the reward increases at a multiplier of two from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lenghents, 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 $50,000, only if the impact leads to:
- A loss of funds involving an attack that does not require any user action
- Unauthorized minting of tokens on-chain
- Private key or private key generation leakage leading to unauthorized access to user funds
All other impacts that would be classified as Critical would be rewarded a flat amount of $10,000. The rest of the severity levels are paid out according to the Impact in Scope table.
Reward Payment Terms
Payouts are handled by the Elixir Protocol team directly and are denominated in USD. However, payments are done in $USDC.
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
Elixir is building the industry’s decentralized, algorithmic market making protocol. Through the Elixir Protocol, anyone will be able to passively supply liquidity to orderbook pairs on spot and perp DEXes across the space, earning subsidized APYs from existing long term liquidity incentive programs offered by exchanges.
Elixir will serve as crucial infrastructure for decentralized (and eventually) centralized exchanges, enabling ecosystem participants to provide liquidity to orderbook pairs via a purpose-built, decentralized DPoS consensus protocol in development for over two years. Elixir utilizes the orderbook equivalent of x*y=k curves, similar to Uniswap v2, to build up order books and tighten the bid/ask spread, bringing a familiar delta-neutral risk/return profile for liquidity providers.
For more information about Elixir, please visit elixir.finance
Elixir provides rewards in USDC, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.
Responsible Publication
Elixir 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
Elixir adheres to the Primacy of Impact for the following categories and severity levels:
- Smart Contract: Critical
- Smart Contract: High
- Smart Contract: Medium
- Web/App:Critical
- Web/App:High
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 projects, those other projects 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 set within this program.
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
Elixir commits to providing Known Issue Assurance to bug submissions through their program. This means that Elixir will either disclose known issues publicly or at the very least privately via a self-reported bug submission.
In scenarios where there might be a mediation, this allows for a more objective and streamlined process 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
Elixir Protocol has provided these completed audit reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward. All Audit reports for Elixir can be accessed on:
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, Elixir has satisfied the requirements for the Immunefi Standard Badge.
KYC not required
No KYC information is required for payout processing.
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.