Skip to content

BlockPI Network

Bug bounty on Immunefi blockpi.io

Accepting reports No KYC Arbitrum Avalanche BSC
Top reward
$5,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 $5,000
for critical bugs, from $1,000.
Paid by USDC
No identity check to get paid.
No public write-ups
Keep findings private.

Rewards

What Immunefi lists as the payout for each severity.

Severity Reward
Critical $5,000 from $2,500
High $1,500
Medium $1,200
Low $1,000

Scope

2 assets you may test.

Domains 2

  • blockpi.io
  • dashboard.blockpi.io

Rules

What the policy asks of you, and the bug types it won't reward, quoted from BlockPI Network (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
  • All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope and a suggestion for a fix in order to be considered for a reward.
  • Proof of concept is always required for all severities.
  • Public disclosure of an unpatched vulnerability in an embargoed bounty

Not accepted

  • 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

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 35 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.

Search 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 BlockPI Network BlockPI Network is a distributed multichain acceleration layer. Now it provides high-quality, robust, and efficient RPC service. To avoid the single-point of failure and limitation of scalability, the network is designed to be a distributed structure with expandable working nodes. Arbitrum Avalanche BSC Base Cronos ETH Fantom Gnosis Klaytn Linea Meter Oasis Optimism Polygon Scroll Starknet Viction zkSync Infrastructure Services Maximum Bounty $5,000 Live Since 11 November 2022 Last Updated 13 August 2026 PoC Required Submit a Bug Information Scope Resources Rewards BlockPI Network provides rewards in USDC , denominated in USD. Rewards by Threat Level Websites and Applications Critical Max: $5,000 Min: $2,500 Primacy of Rules High Flat: $1,500 Primacy of Rules Medium Flat: $1,200 Primacy of Rules Low Flat: $1,000 Primacy of Rules Rewards Body Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2 . This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported. All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope and a suggestion for a fix in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. Only those in the Assets in Scope table are considered as in-scope of the bug bounty program. If an impact can be caused to any other asset managed by BlockPI that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This only applies to Critical and High impacts. Payouts are handled by the BlockPI team directly and are denominated in USD. However, payouts are done in USDC . View impacts in scope Program Overview BlockPI Network is a distributed multichain acceleration layer. Now it provides high-quality, robust, and efficient RPC service. To avoid the single-point of failure and limitation of scalability, the network is designed to be a distributed structure with expandable working nodes. For more information about BlockPI, please visit https://blockpi.io/ and go to the documentation at https://docs.blockpi.io/ KYC not required No KYC information is required for payout processing. Proof of Concept Proof of concept is always required for all severities. 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 paid 30.4k Med. Resolution Time 1 day Total Assets in Scope 2