Impossible Cloud Network
Impossible Cloud Network (ICN) is developing the foundational layer for the next-gen internet.
Triaged by Immunefi
PoC Required
KYC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$25,000Minimum reward to discourage security researchers from withholding a bug report:
$10,000Rewards by Threat Level
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 smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 25 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 10 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. 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 1h the attack needs for subsequent attacks from the first attack, rounded down Reward Calculation for High Level Reports
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD 3 000 to USD 5 000 with the reward calculated based on 100% of the funds at risk, though 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.
Primacy of Impact vs Primacy of Rules
Impossible Cloud Network adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.
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.
Public Disclosure of Known Issues
Bug reports covering previously-discovered bugs (listed below) are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to “fix”, necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.
Intended functionality:
-
Temporary freezing of funds: The ICN Protocol has implemented a pause feature which stops funds from being able to transit through the protocol. Meaning ICNT cannot be deposited or withdrawn until unpaused. This is used only in critical scenarios of catastrophic bugs that may jeopardize user funds or protocol economies to minimize damage and give time for the team to issue fixes.
-
Smart contract unable to operate due to lack of token funds: Protocol rewards are funded by a smart contract that rewards activity via a reward fund. As the reward fund depletes, the ICN protocol will be topped up to maintain healthy operation. While there is no protocol rule to prevent the reward fund from depleting completely, ICN is regularly maintaining checks and periodically returns the fund to healthy levels.
-
Scenarios that involve unsupported states or rely on assumptions (such as transferring an NFT while staked, etc) are not considered valid and will be rejected.
Known issues:
-
ScalerNode can be removed before its utilized capacity is reset: Users can create bookings for resources on ScalerNodes. The BookingManager is responsible for updating the utilized capacity trackers for the region, cluster and hardware provider for the node that's being booked/re-booked. As a booking expires the updates to these trackers are not updated immediately, instead a call to expireCapacity() needs to be made which will perform the desired operations. Currently a node can be removed by a call to removeScalerNode() on ICNRegistry which does not check whether the capacity for the node is still marked as utilized. After removing the node it will be impossible to revert the utilized capacity updates that were made in creating the last booking for the removed node. As a result various computations around protocol rewards will be inaccurate since they'll operate with inaccurate utilized capacity numbers.
-
Users are not guarded against price increase in the extendBooking path: Users are guarded against unexpected price increases in the bookCapacity function by specifying a maxBookingPrice. But this guard is not present in the extendBooking function where similar similar issue can occur.
-
Link token ids must be smaller than the max uint32 value: The modules supporting link staking and reward claiming assume that link token ids have a value lower than the max uint32 value.Currently the ICN link contract supports minting tokens that do not satisfy this constraint, as a result governance might accidentally mint tokens that are incompatible with the modules.
Reward Payment Terms
Payouts are handled by the Impossible Cloud Network team directly and are denominated in USD. However, payments are done in USDC on Base.
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
Impossible Cloud Network (ICN) is developing the foundational layer for the next-gen internet. Challenging the dominance of centralized tech giants, ICN introduces a fully open, multi-service, permissionless and composable cloud infrastructure that integrates storage, compute, and networking at scale. Our enterprise-grade, decentralized architecture ensures high performance, security, and censorship resistance – making web3 as seamless as web2. With real-world adoption and a pragmatic approach to decentralization, ICN is positioned to become the foundation of a future internet, powering the next generation of cloud services, AI agents, enterprise software, and digital ecosystems.
Unlimited Scale: AI and cloud demand cannot be met. Traditional cloud is hitting scalability limits, preventing dynamic expansion and restricting new entrants. The internet needs infrastructure that can adapt to an evolving digital era.
Unrestricted Cloud: Most of the internet is controlled by a handful of large players, limiting opportunities for individuals and businesses to participate in AI and cloud growth. Web3 offers greater trustlessness, data authenticity, and accessibility with ICNs performance and efficiency.
Networks without demand: Many Web3 companies are bootstrapping networks without a viable path to profitability. ICN introduces a decentralized, market-driven approach that enables sustainable growth and economic opportunity with a network that dynamically shifts with the ecosystem. ICN decentralizes cloud infrastructure by bringing together a global network of Hardware Providers (HPs) and Builders in a transparent and open ecosystem with a deeply enabled crypto-native core. This model allows protocols and businesses to access top-tier computing power and storage capacity without the limitations of traditional cloud services—ensuring scalable, secure, and performant solutions while maintaining composability and trust optionality for a truly modular network layer.
For more information about Impossible Cloud Network, please visit https://www.icn.global/
Impossible Cloud Network provides rewards in USDC on Base, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.
The assessment of the extent of any potential indirect economic damage, defined as damage other than that evidenced by a PoC that showcases the direct exploitation of the vulnerability leading to impact, is at the full discretion of the project.
KYC required
The submission of KYC information is a requirement for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Responsible Publication
Category 3: Approval Required
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.