The Ethereum Basis Bug Bounty Program is likely one of 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, aside from the deposit contract, so the 2 bug bounty packages have remained separated.

In gentle of the approaching Merge, right this moment we’re comfortable to announce that these two packages have been efficiently merged by the superior ethereum.org workforce, 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 change into an increasing number of interconnected, it’s more and more precious 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 reside on public testnets and focused for a Mainnet launch are additionally scope, and rewards are doubled throughout this time, which signifies that the max reward is$

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.

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 shopper being utilized by <1% of the community would definitely trigger points for the customers of this shopper, it will 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 right way to report vulnerabilities.

Github Safety

Repositories reminiscent of ethereum/consensus-specs and ethereum/go-ethereum now comprise info on the right way to report vulnerabilities in SECURITY.md recordsdata.

safety.txt

safety.txt is applied and incorporates details about the right way to report vulnerabilities. The file itself may be discovered right here.

DNS Safety TXT

DNS Safety TXT is applied and incorporates details about the right way to report vulnerabilities. This entry may be seen 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 good contract all inside the scope of the bounty program, there’s a loads for bounty hunters to dig into.

If you happen to’re in search of some concepts of the place to start out your bug looking journey, check out the beforehand reported vulnerabilities. This was final up to date in March and incorporates all of the reported vulnerabilities now we have on file, up till the Altair community improve.

We’re wanting ahead to your reviews! 🐛