- Top reward
- $1,000
- Top severity paid
- Critical
- Assets in scope
- 2
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $1,000
- for critical bugs, from $1,000.
- Report on Immunefi
- Submit through the program page.
- Paid by USDT, USDC
- No identity check to get paid.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What Immunefi lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$1,000 1% of funds at risk |
Scope
2 assets you may test.
Source code 2
- https://github.com/AcalaNetwork/Acala
- https://github.com/open-web3-stack/open-runtime-module-library
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Acala (via Immunefi)'s policy. "We" in these lines means the program, not this site.
While testing
-
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
-
Proof of concept is always required for all severities.
Summarised with AI from the program policy on Immunefi, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 22 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from immunefi.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Back to Explore Acala Acala is the decentralized finance network and liquidity hub of Polkadot. It’s a layer-1 smart contract platform that’s scalable, Ethereum-compatible, and optimized for DeFi with built-in liquidity and ready-made financial applications. With its trustless exchange, DOT Liquid Staking (LDOT), and EVM+, Acala lets developers access the best of Ethereum and the full power of Substrate. Polkadot Blockchain Defi Stablecoin Staking Rust Maximum Bounty $1,000 Live Since 14 December 2021 Last Updated 14 August 2026 Runnable PoC Required Submit a Bug Information Scope Resources Rewards Acala provides rewards in USDT, USDC on Ethereum , denominated in USD. Rewards by Threat Level Blockchain/DLT Critical Flat: $1,000 Primacy of Rules Critical Reward Calculation Reward amount is 1 % of the funds directly affected, capped at the maximum critical reward of: $1,000 The reward is dependent on the ratio between the funds at risk, which includes all affected projects on top of the respective blockchain/DLT, and the market cap according to the average between CoinMarketCap.com and CoinGecko.com, calculated at the time the bug report is submitted. Rewards Body Reward Calculation for Critical Level Reports For critical Blockchain/DLT bugs, the reward amount is 5% of the funds directly affected, capped at the maximum critical reward USD $1,000. Reward Payment Terms Payouts are handled by the Acala team directly in crypto tokens of their choices, valued at the US dollar market rates, e.g. USDT, 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. View impacts in scope Program Overview Acala is the decentralized finance network and liquidity hub of Polkadot. It’s a layer-1 smart contract platform that’s scalable, Ethereum-compatible, and optimized for DeFi with built-in liquidity and ready-made financial applications. With its trustless exchange, decentralized stablecoin (aUSD), DOT Liquid Staking (LDOT), and EVM+, Acala lets developers access the best of Ethereum and the full power of Substrate. For more information about Acala, please visit https://acala.network/ . KYC not required No KYC information is required for payout processing. Proof of Concept Proof of concept is always required for all severities. Responsible Publication Category 3: Approval Required Prohibited Activities Default 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. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug Total Assets in Scope 2