Attackathon | VeChain Hayabusa Upgrade
The VeChain Hayabusa upgrade is the second phase of the VeChain Renaissance. The Hayabusa upgrade will upgrade VeChainThor’s consensus mechanism, tokenomics and degree of decentralization. Key Highlights:
- Upgrade to Delegated Proof of Stake (DPoS): VeChainThor will migrate from PoA to DPoS, a more decentralized consensus mechanism, while maintaining strong security and performance.
- Enhanced VTHO Tokenomics: A dynamic VTHO generation rate will be distributed as a block reward to validators and delegators that contribute to securing the VeChainThor network.
Live
Triaged by Immunefi
Step-by-step PoC Required
KYC required
This Attackathon Is Live!
$160,000 USD in conditional rewards are available for finding bugs on the VeChain Hayabusa Upgrade.
-
Rewards are distributed among SRs according to Immunefi’s Standardized Competition Reward Terms and includes All Star Pool and Podium Pool reserved for All Star Program participants.
-
KYC is required.
-
Conditional Reward Pool
-
Any technical questions and support requests can be asked directly to VeChain or Immunefi in the VeChain Hayabusa Upgrade Attackathon Discord channel.
-
When the Attackathon has ended, Immunefi will publish an event-specific leaderboard and bug reports from the event.
-
Runnable POCs are required. Read our Proof-of-Concept Rules
-
Insight reports can be submitted. Read our Insight validity rules
Rewards
Rewards by Threat Level
Rewards are distributed among SRs according to Immunefi’s Standardized Competition Reward Terms.
Rewards are denominated in USD and distributed in USDT on Ethereum.
The reward pool is determined by the greatest severity bug found.
- A Critical is found - $160,000 USD
- A High is found - $100,000 USD
- A Medium is found - $70,000 USD
- A Low is found - $40,000 USD
If none of the above conditions apply then the reward pool is - $24,000 USD
Private known issues, meaning known issues that were not publicly disclosed, are valid and unlock the corresponding reward pool.
Mitigation Competition Rewards
The maximum reward pool for the mitigation competition is $40,000 USD.
If any bug in scope is fixed during the mainnet AC then a mitigation competition will begin immediately, run simultaneously, and end 5 days after the mainnet AC has ended.
The mitigation competition’s reward pool is based on how many bugs are fixed while the competitions are live relative to how many bugs are found in the mainnet AC. So if projects make more bug fixes mid-competition then the size of the mitigation competition reward pool increases up to the maximum.
The full mitigation competition reward terms can be read here.
Code Updates Log TBD
Program Overview
For more information about VeChain Foundation, please visit https://vechain.org/.
This is a mainnet AC (audit competition) and the project may fix bugs mid-competition. The more bugs a project fixes the more rewards will be unlocked for a simultaneously running mitigation competition with up to $40,000 USD in rewards that is open for everyone to participate in. Read our full mainnet AC rules for more info.
VeChain is running 2 audits in parallel with the Attackathon. Due to this, some findings could be invalidated as duplicates from the ongoing audits.
Responsible Publication
Immunefi will publish bug reports, earnings, and a leaderboard for this Attackathon.
Security Researchers may publish their bug reports as well, but only after Immunefi has published the valid bug reports as part of the competition results.
Dispute Resolution
If there is any dispute over bug reports between projects and security researchers, Immunefi has final say on validity and severity based on the terms of this program.
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
- 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.