INTMAX
Bounty Range
$1,000 - $10,000
external program
INTMAX
INTMAX is a stateless Layer 2 rollup combining Plasma and ZKPs to enable fast, private, and gas-efficient Ethereum transactions. It removes on-chain storage entirely, supports infinite users without state bloat, and offers a novel approach to scalability and privacy.
INTMAX is an extremely scalable layer for Ethereum transfers that incorporates ethically sound privacy. It is a stateless zkRollup structure, theoretically achieving scalability similar to Plasma and Lightning Network, as envisioned in 2018.
By distributing both data and computation costs across users' devices, INTMAX inherits security from Ethereum while achieving scalability even greater than centralized financial systems using databases.
Maximum Bounty: $10,000
Live Since: 25 May 2025
Last Updated: 29 January 2026
Requirements:
INTMAX provides rewards in USDC on Arbitrum, denominated in USD.
Funds available: $6,999.04
30d Avg. Funds availability: $12,132.60
Public vault address: 0xd4FA95db98aab2E4E8AEfAE4a841CE016d020fD1
Critical
High
Medium
Critical Reward Calculation: Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of $10,000. Minimum reward to discourage security researchers from withholding a bug report: $5,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.
Critical
High
Medium
Low
Critical Reward Calculation:
Reward amount is 10% of the funds directly affected up to a maximum of $10,000. Minimum reward to discourage security researchers from withholding a bug report: $5,000.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Reward Calculation for Critical Level Reports
For critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward $10,000. However, a minimum reward of USD $4,000 is to be rewarded in order to incentivize security researchers against withholding on a bug report.
For critical Blockchain/DLT bugs with a non-funds-at risk impact, the reward will be paid out as follows:
For critical Blockchain/DLT bugs, 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.
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 $4,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
For critical smart contract bugs on testnet assets, the reward is paid as a flat amount. This is because there are no actual funds at risk on the testnet, hence limits objective calculation.
All other impacts that would be classified as Critical would be rewarded a flat amount of $5,000. The rest of the severity levels are paid out according to the Impact in Scope table.
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
For high Blockchain/DLT non-funds-at risk impacts, the reward will be paid out as follows:
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of $2,000 to $3,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 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 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.
Reward Payment Terms
Payouts are handled by the INTMAX team directly and are denominated in USD. However, payments are done in USDC on Arbitrum.
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.
INTMAX 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.
The submission of KYC information is a requirement for payout processing.
Participants must adhere to the Eligibility Criteria.
Proof of concept is always required for all severities.
Category 1: Transparent
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.
| Auditor | Link | Completed at |
|---|---|---|
| ChainSecurity | https://drive.google.com/file/d/1OuUvG0ugnXcJs0-eLyiAMBtnHSZYTbTR/view?usp=sharing | 30 October 2024 |
| ChainSecurity | https://www.chainsecurity.com/security-audit/plonky2-bn254-keccak256 | 19 December 2024 |
| ChainSecurity | https://drive.google.com/file/d/1BwyrrGpavYJXLqaujIzZFkRQz2M_L7Qh/view?usp=sharing | 20 December 2024 |
| ChainSecurity | https://drive.google.com/file/d/1aYe5IwkKxEJTQboIoJ5O4igzdMwMDgH3/view?usp=sharing | 23 December 2024 |