AGNI
Bounty Range
$1,000 - $10,000
external program
AGNI
AGNI is a permissionless, AMM-based exchange that supercharges spot trades with concentrated liquidity within preferred price ranges for a customized trading experience, driving maximum gains at the lowest risks possible. It runs on Mantle Network, a modular Ethereum layer-2 blockchain that delivers hyperscale performance at low fees, while deriving its security from Ethereum.
A one-stop platform that also offers an easy-to-access launchpad and yield-generating features, users will not only get to know new, innovative crypto tokens, but accelerate their decentralized trading experience in safe and trusted environment. Driven by a robust community, AGNI is set to lead the charge for AMM DEXs based on its efficiency, reliability and usability — fit for all types of traders, the DEX companion that you need.
It is AGNI's vision to build an inclusive, open and community-governed DEX that brings users the best of what decentralized platforms have to offer at present, all in one place.
AGNI provides rewards in USDT on Mantle, denominated in USD.
Smart Contract
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 10,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 1,000 is to be rewarded in order to incentivize security researchers against withholding a critical 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.
The amount of funds at risk will be calculated with the impact of the first attack being at 100% and then a reduction of 25% from the amount of the first attack for every 300 blocks the attack needs for subsequent attacks from the first attack, rounded down.
Payouts are handled by the AGNI team directly and are denominated in USD. However, payments are done in USDT on Mantle.
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.
AGNI adheres to Category 3: Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports.
AGNI adheres to the Primacy of Impact for the following 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.
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.
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Proof of concept is always required for all severities.
AGNI's completed audit reports can be found at https://github.com/Secure3Audit/AgniFinance_PancakeV3_Similarity_Analysis. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
| Auditor | Link | Completed at |
|---|---|---|
| All audits | https://github.com/Secure3Audit/AgniFinance_PancakeV3_Similarity_Analysis | 18 February 2026 |
The submission of KYC information is a requirement for payout processing.
Participants must adhere to the Eligibility Criteria.
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
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.