Hyperlane

Back to Explore Hyperlane Hyperlane is the modular interoperability platform, empowering developers to build interchain applications, apps that can easily and securely communicate between blockchains. Arbitrum BSC Celo ETH Gnosis Moonbeam Optimism Polygon Blockchain Infrastructure Services NextJS Solidity Maximum Bounty $2,500,000 Live Since 10 January 2023 Last Updated 28 July 2026 PoC Required KYC required Submit a Bug Information Scope Resources Rewards Hyperlane provides rewards in USDC on Ethereum , denominated in USD. Rewards by Threat Level Smart Contract Critical Max: $2,500,000 Min: $10,000 Primacy of Rules High Max: $200,000 Min: $5,000 Primacy of Rules Medium Flat: $2,500 Primacy of Rules Low Flat: $1,000 Primacy of Rules Critical Reward Calculation Mainnet assets: Reward amount is 10 % of the funds directly affected up to a maximum of: $2,500,000 Minimum reward to discourage security researchers from withholding a bug report: $10,000 Websites and Applications Critical Flat: $20,000 Primacy of Rules High Flat: $10,000 Primacy of Rules Medium Flat: $2,000 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 in order to be considered for a reward. Critical and High Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required. Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 10 000 . High smart contract vulnerabilities are capped at 10% of economic damage as well, with a minimum reward of USD 5 000 . Hyperlane requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed are Name and Identity Proof (Passport, / Driving License / National ID). The collection of this information will be done by the project team. Payouts are handled by the Hyperlane team directly and are denominated in USD. However, payouts are done in USDC . View impacts in scope Program Overview Hyperlane is the modular interoperability platform, empowering developers to build interchain applications, apps that can easily and securely communicate between blockchains. For more information about Hyperlane, please visit https://www.hyperlane.xyz/ . 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. 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 222