The Ethereum Basis Bug Bounty Program is without doubt one of the earliest and longest operating 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, operating alongside the unique Bug Bounty Program.
The cut up of those packages is historic as a result of manner 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 gentle of the approaching Merge, in the present day we’re blissful 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 change into 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 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 intervals!
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.
Influence 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 would definitely trigger points for the customers of this consumer, it could have a better 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 packages and improve of the max reward, a number of steps have been taken to make clear find out how to report vulnerabilities.
Github Safety
Repositories resembling ethereum/consensus-specs and ethereum/go-ethereum now include info on find out how to report vulnerabilities in SECURITY.md information.
safety.txt
safety.txt is carried out and accommodates details about find out how to report vulnerabilities. The file itself could be discovered right here.
DNS Safety TXT
DNS Safety TXT is carried out and accommodates details about find out how to report vulnerabilities. This entry could be considered by operating dig _security.ethereum.org TXT.
How are you going to get began? 🔨
With 9 totally different purchasers written in numerous 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.
In case you’re searching for some concepts of the place to begin 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 report, up till the Altair community improve.
We’re wanting ahead to your experiences! 🐛
