The Ethereum Basis Bug Bounty Program is among the earliest and longest working applications of its form. It was launched in 2015 and focused the Ethereum PoW mainnet and associated software program. In 2020, a second Bug Bounty Program for the brand new Proof-of-Stake Consensus Layer was launched, working alongside the unique Bug Bounty Program.
The cut up of those applications is historic because of the means the Proof-of-Stake Consensus Layer was architected individually and in parallel to the present Execution Layer (contained in the PoW chain). For the reason that launch of the Beacon Chain in December of 2020, the technical structure between the Execution Layer and the Consensus Layer has been distinct, apart from the deposit contract, so the 2 bug bounty applications have remained separated.
In gentle of the approaching Merge, immediately we’re joyful to announce that these two applications have been efficiently merged by the superior ethereum.org group, and that the max bounty reward has been considerably elevated!
Merge (of the Bug Bounty Applications) ✨
With The Merge approaching, the 2 beforehand disparate bug bounty applications have been merged into one.
Because the Execution Layer and Consensus Layer grow to be increasingly interconnected, it’s more and more helpful to mix the safety efforts of those layers. There are already a number of efforts being organized by consumer groups and the group to additional improve data and experience throughout the 2 layers. Unifying the Bounty Program will additional improve visibility and coordination efforts on figuring out and mitigating vulnerabilities.
Elevated Rewards 💰
The max reward of the Bounty Program is now 500,000 throughout these intervals!
In complete, this marks a 10x improve from the earlier most payout on Consensus Layer bounties and a 20x improve from the earlier max payout on Execution Layer bounties.
Impression Measurement 💥
The Bug Bounty Program is primarily centered on securing the bottom layer of the Ethereum Community. With this in thoughts, the affect of a vulnerability is in direct correlation to the affect on the community as a complete.
Whereas, for instance, a Denial of Service vulnerability present in a consumer being utilized by <1% of the community will surely trigger points for the customers of this consumer, it might have a better affect on the Ethereum Community if the identical vulnerability existed in a consumer utilized by >30% of the community.
Visibility 👀
Along with the merge of the bounty applications and improve of the max reward, a number of steps have been taken to make clear easy methods to report vulnerabilities.
Github Safety
Repositories equivalent to ethereum/consensus-specs and ethereum/go-ethereum now include info on easy methods to report vulnerabilities in SECURITY.md recordsdata.
safety.txt
safety.txt is carried out and comprises details about easy methods to report vulnerabilities. The file itself may be discovered right here.
DNS Safety TXT
DNS Safety TXT is carried out and comprises details about easy methods to report vulnerabilities. This entry may be considered by working dig _security.ethereum.org TXT.
How are you going to get began? 🔨
With 9 totally different purchasers written in varied languages, Solidity, the Specs, and the deposit sensible contract all throughout the scope of the bounty program, there’s a a lot for bounty hunters to dig into.
In case you’re in search of some concepts of the place to begin your bug looking journey, check out the beforehand reported vulnerabilities. This was final up to date in March and comprises all of the reported vulnerabilities we have now on document, up till the Altair community improve.
We’re wanting ahead to your reviews! 🐛
