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.
Evaluating
Triaged by Immunefi
Step-by-step PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Proof of Concept (PoC) Requirements
A runnable PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Asset Accuracy Assurance
Bugs found on assets incorrectly listed in-scope are valid.
Previous Audits
VeChain’s completed audit reports can be found:
- https://github.com/slowmist/Knowledge-Base/blob/master/open-report/VeChainThorNodeToken-Smart-Contract-Security-Audit-Report.md
- https://www.nccgroup.com/media/f05ojmp4/ncc_group_vechainfoundationsanmarinosrl_e0237_.pdf
- https://www.coinspect.com/doc/Coinspect%20-%20Source%20Code%20Audit%20-%20VeChainThor%20Galactica%20V250512.pdf
Unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Public Disclosure of Known Issues
Bug reports for publicly disclosed bugs are not eligible for a reward.
- Underflow enables contract drain, https://github.com/vechain/thor/pull/1348.
- No delegations allowed in Exiting Validator, https://github.com/vechain/thor/pull/1384
Private Known Issues Reward Policy
Private known issues, meaning known issues that were not publicly disclosed, are valid for a reward.
Mainnet AC (Audit Competition) Bug Fix Policy
The project may make bug fixes during the competition.
- Fixed bugs immediately become out of scope once the fix is public.
- Duplicate submissions of a bug are only valid if they’re submitted before the fix is public.
All project made bug fixes immediately become in scope for the mitigation competition once the fix is public, including fixes to bugs found independently of SRs.
Read our full mainnet AC rules for more info.
Insight Reporting
Insight reports may be reported to this program and do not require a PoC. Insights are rewarded according to Immunefi’s Standardized Competition Reward Terms.
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
Direct loss of funds
Permanent freezing of funds (fix requires hardfork)
Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Network not being able to confirm new transactions (total network shutdown)
Unintended chain split (network partition)
Temporary freezing of network transactions by delaying one block by 500% or more of the average block time of the preceding 24 hours beyond standard difficulty adjustments
Causing network processing nodes to process transactions from the mempool beyond set parameters
RPC API crash affecting programs with greater than or equal to 25% of the market capitalization on top of the respective layer
Out of scope
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers