Arkadiko
Bounty Range
$1,000 - $100,000
external program
Arkadiko
Arkadiko is a decentralized, non-custodial liquidity protocol where users can collateralize their assets and mint a stablecoin called USDA.
Launched in October 2021, Arkadiko was the first Decentralized Finance protocol on Stacks, bringing native stablecoin liquidity to the on-chain ecosystem.
Arkadiko 2.0 is the next-generation iteration of Arkadiko, introducing several improvements to the core protocol.
Maximum Bounty: $100,000
Live Since: 03 June 2024
Last Updated: 22 January 2026
Arkadiko provides rewards in USDC on Ethereum, denominated in USD.
Smart Contract
Websites and Applications
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $100,000.
Minimum reward to discourage security researchers from withholding a bug report: $20,000
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 20,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 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 USD 1,000 to USD 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 24 hours 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 USD 25,000, only if the impact leads to:
All other impacts that would be classified as Critical would be rewarded a flat amount of USD 5,000.
Reward Payment Terms
Payouts are handled by the Arkadiko team directly and are denominated in USD. However, payments are done in USDC on Ethereum.
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.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Proof of Concept (PoC) Requirements
Proof of concept is always required for all severities and has to comply with the Immunefi PoC Guidelines and Rules.
KYC not required
No KYC information is required for payout processing.
Responsible Publication
Category 3: Approval Required
Primacy of Impact vs Primacy of Rules
Arkadiko adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page.
Known Issue Assurance
Arkadiko commits to providing Known Issue Assurance to bug submissions through their program. This means that Arkadiko 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.
Previous Audits
Arkadiko's completed audit reports can be found at https://www.coinfabrik.com/blog/arkadiko-audit/. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Immunefi Standard Badge
By adhering to Immunefi's best practice recommendations, Arkadiko has satisfied the requirements for the Immunefi Standard Badge.
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.
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, including Chain Rollbacks, Pre-Impact Bug Monitoring, Attack Investment Amount, Attacks With A Financial Risk To The Attacker, and When Is An Impactful Attack Downgraded To Griefing.