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 as a result of method 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 mild of the approaching Merge, in the present day we’re blissful to announce that these two applications 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 Packages) ✨
With The Merge approaching, the 2 beforehand disparate bug bounty applications have been merged into one.
Because the Execution Layer and Consensus Layer change into an increasing number of interconnected, it’s more and more invaluable to mix the safety efforts of those layers. There are already a number of efforts being organized by consumer groups and the neighborhood to additional improve information 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 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.
Impression Measurement 💥
The Bug Bounty Program is primarily centered on securing the bottom layer of the Ethereum Community. With this in thoughts, the influence of a vulnerability is in direct correlation to the influence 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 will have the next influence 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 report vulnerabilities.
Github Safety
Repositories akin to ethereum/consensus-specs and ethereum/go-ethereum now include data on report vulnerabilities in SECURITY.md information.
safety.txt
security.txt is carried out and incorporates details about report vulnerabilities. The file itself can be found here.
DNS Safety TXT
DNS Security TXT is carried out and incorporates details about report vulnerabilities. This entry will be seen by working dig _security.ethereum.org TXT.
How will you 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 lots 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 previously reported vulnerabilities. This was final up to date in March and incorporates all of the reported vulnerabilities we’ve got on file, up till the Altair community improve.
We’re trying ahead to your experiences! 🐛
