
Alpen Labs
Bounty Range
$1,000 - $5,000
external program
Alpen gives developers the freedom to program nearly any locking conditions for BTC imaginable, limited only by the Alpen block size and gas limits. This enables developers to create new kinds of applications for BTC with features such as:
Smart Contract
Websites and Applications
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $5,000
Testnet assets: For critical smart contract bugs on testnet assets, the reward is paid as a flat amount of USD 2,500. For high level smart contract bugs on testnet assets, the reward is paid as a flat amount of USD 2,500.
Payouts are handled by the Alpen Labs team directly and are denominated in USD. Payments are done via wire transfer.
Alpen Labs will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
Alpen Labs adheres to Category 3: Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports.
Alpen Labs 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.
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules. Proof of concept is always required for all severities.
Alpen Labs's completed audit reports can be found at Project's Audits URL. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
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 feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.