The Ethereum Basis Bug Bounty Program is among the earliest and longest working packages of its sort. 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 break up of those packages is historic because of the method the Proof-of-Stake Consensus Layer was architected individually and in parallel to the present Execution Layer (contained in the PoW chain). Because the 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 packages have remained separated.
In mild of the approaching Merge, right now we’re joyful to announce that these two packages have been efficiently merged by the superior ethereum.org staff, 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 packages have been merged into one.
Because the Execution Layer and Consensus Layer grow to be increasingly more interconnected, it’s more and more priceless to mix the safety efforts of those layers. There are already a number of efforts being organized by shopper 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 $250,000 (paid out in ETH or DAI) for vulnerabilities in scope. Upgrades stay on public testnets and focused for a Mainnet launch are additionally scope, and rewards are doubled throughout this time, which implies that the max reward is $500,000 throughout these durations!
In whole, 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.
Affect 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 an entire.
Whereas, for instance, a Denial of Service vulnerability present in a shopper being utilized by <1% of the community will surely trigger points for the customers of this shopper, it could have the next affect on the Ethereum Community if the identical vulnerability existed in a shopper utilized by >30% of the community.
Visibility 👀
Along with the merge of the bounty packages and improve of the max reward, a number of steps have been taken to make clear the way to report vulnerabilities.
Github Safety
Repositories comparable to ethereum/consensus-specs and ethereum/go-ethereum now comprise info on the way to report vulnerabilities in SECURITY.md recordsdata.
safety.txt
safety.txt is applied and accommodates details about the way to report vulnerabilities. The file itself might be discovered right here.
DNS Safety TXT
DNS Safety TXT is applied and accommodates details about the way to report vulnerabilities. This entry might be considered by working dig _security.ethereum.org TXT.
How will you get began? 🔨
With 9 completely different shoppers written in numerous languages, Solidity, the Specs, and the deposit good contract all throughout the scope of the bounty program, there’s a a lot for bounty hunters to dig into.
For those who’re on the lookout for some concepts of the place to start out your bug searching journey, check out the beforehand reported vulnerabilities. This was final up to date in March and accommodates all of the reported vulnerabilities we’ve got on file, up till the Altair community improve.
We’re wanting ahead to your stories! 🐛
