The Ethereum Basis Bug Bounty Program is among the earliest and longest operating packages of its type. 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, operating alongside the unique Bug Bounty Program.
The cut up of those packages is historic because of the approach the Proof-of-Stake Consensus Layer was architected individually and in parallel to the prevailing 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, aside from the deposit contract, so the 2 bug bounty packages have remained separated.
In mild of the approaching Merge, right now we’re comfortable to announce that these two packages 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 Packages) ✨
With The Merge approaching, the 2 beforehand disparate bug bounty packages have been merged into one.
Because the Execution Layer and Consensus Layer turn out to be increasingly more interconnected, it’s more and more beneficial to mix the safety efforts of those layers. There are already a number of efforts being organized by shopper groups and the neighborhood to additional enhance information and experience throughout the 2 layers. Unifying the Bounty Program will additional enhance 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 enhance from the earlier most payout on Consensus Layer bounties and a 20x enhance 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 impression of a vulnerability is in direct correlation to the impression 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 impression 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 enhance of the max reward, a number of steps have been taken to make clear the way to report vulnerabilities.
Github Safety
Repositories corresponding to ethereum/consensus-specs and ethereum/go-ethereum now comprise data on the way to report vulnerabilities in SECURITY.md recordsdata.
safety.txt
security.txt is applied and accommodates details about the way to report vulnerabilities. The file itself can be found here.
DNS Safety TXT
DNS Security TXT is applied and accommodates details about the way to report vulnerabilities. This entry could be considered by operating 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 loads for bounty hunters to dig into.
In case you’re in search of some concepts of the place to begin your bug searching journey, check out the previously reported vulnerabilities. This was final up to date in March and accommodates all of the reported vulnerabilities now we have on report, up till the Altair community improve.
We’re trying ahead to your experiences! 🐛