PoC required
KYC required
Rewards
Rewards by Threat Level
Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of:
$100,000Minimum reward to discourage security researchers from withholding a bug report:
$35,000Rewards are distributed according to the impact the vulnerability described in the Bug Bounty Report and determined by VeChain that could otherwise cause based on the Impacts in Scope table further below.
For critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward USD 100 000. However, a minimum reward of USD 35 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 to the legal name of Security Researcher submitting the Bug Bounty Report as follows:
- Network not being able to confirm new transactions (total network shutdown) - USD 35 000
- Unintended permanent chain split requiring hard fork (network partition requiring hard fork) - USD 35 000
- Permanent freezing of funds (fix requires hardfork) - USD 35 000
For high Blockchain/DLT impacts, the reward will be paid out as follows:
- Unintended chain split (network partition) - USD 20 000
- Causing network processing nodes to process transactions from the mempool beyond set parameters - USD 15 000
Program Overview
VeChain (VET) is a versatile enterprise-grade L1 smart contract platform.
VeChain began in 2016 working with a host of enterprises to explore applications of blockchain. VeChain would begin their transition to public blockchain in 2017 with the ERC-20 token VEN, before launching a mainnet of their own in 2018 using the ticker VET.
VeChain aims to use distributed governance and Internet of Things (IoT) technologies to create an ecosystem which solves major data hurdles for multiple global industries from medical to energy, food & beverage to sustainability and SDG goals. By leveraging the power of trustless data, VeChain is building the digital backbone that will underpin the fourth industrial revolution, which demands real-time and trustless data sharing between many participants.
For more information about VeChain, please visit https://www.vechain.org/
VeChain provides rewards in USDC. For more details about the payment process, please view the Rewards by Threat Level section further below. Please note that the VeChain team may take up to two business days to reply to bug submissions.
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.