Immunefi
Audit Comp | Base Everest-logo

Audit Comp | Base Everest

|

Base Chain is a fast, low-cost, decentralized network that delivers sub-second, sub-cent global transactions. It is the foundation for a new economy where anyone, anywhere can participate.

Base
Blockchain
L2
Rust
Solidity

Live

11d: 17h remaining
Primary Pool
$175,000
All Stars Pool
$50,000
Podium Pool
$25,000
Start Date
19 November 2026
End Date
01 December 2026
Rewards Token
USDC
Lines of Code
135,275
  • Triaged by Immunefi

  • Runnable PoC Required

  • KYC required

This Audit Competition Is Live!

$250,000 USD is available in rewards for finding eligible bugs in the Base Everest codebase of about 135,000 nSLOC.

KYC is required.

Base team will respond within 48 hours on weekdays to all bug reports. Any technical questions and support requests can be asked directly to Base or Immunefi in the Base Everest Audit Competition Discord channel.

In this contest bug fixes may be applied mid-contest. Further details are in the 'Assets In Scope' section.

When the Audit Competition has ended Immunefi will publish an event-specific leaderboard and bug reports from the event.

MilestoneDate
AnnouncementNov 9, 2026
Launch (competition goes live)Nov 19, 2026
Competition endsDec 1, 2026
Project deadline to resolve all reportsDec 11, 2026
Results frozen and calculatedDec 12, 2026
Final 48-hour dispute deadlineDec 15, 2026
Results publishedDec 24, 2026
Payment completeDec 25, 2026

The dates in this calendar may be adjusted by Immunefi as needed for the execution of the competition.

Start Date
19 November 2026 17:00 UTC
End Date
01 December 2026 12:00 UTC

Rewards

Audit Comp | Base Everest provides rewards in USDC on Base, denominated in USD.

Rewards by Threat Level

Blockchain/DLT
Critical
Portion of the Reward Pool
High
Portion of the Reward Pool
Medium
Portion of the Reward Pool
Low
Portion of the Reward Pool
Smart Contract
Critical
Portion of the Reward Pool
High
Portion of the Reward Pool
Medium
Portion of the Reward Pool
Low
Portion of the Reward Pool
All categories *
Insight
Portion of the Reward Pool
Rewards Body

Rewards are distributed among SRs according to Immunefi’s Standardized Competition Reward Terms and include the All Star Pool and Podium Pool reserved for All Star Program participants.

Rewards are denominated in USD and distributed in USDC on Base.

The total reward pool, shared among eligible researchers under Immunefi’s distribution rules, is determined by the highest-severity valid finding.

  • A Critical is found - USD 250,000
  • A High is found - USD 125,000
  • A Medium is found - USD 70,000
  • A Low is found - USD 30,000
  • If none of the above conditions apply, the reward pool is USD 20,000

Private known issues, meaning known issues that were not publicly disclosed, are valid and unlock the corresponding reward pool.

A private known issue that is publicly disclosed during the competition becomes a public known issue, as set out in the Private Known Issues Reward Policy.

Immunefi will administer researcher payouts from the prepaid reward pool. After the competition has concluded and the final bug reports have been resolved, rewards are distributed all at once based on Immunefi’s distribution formula.

Program Overview

Base Chain is a fast, low-cost, decentralized network that delivers sub-second, sub-cent global transactions. It is the foundation for a new economy where anyone, anywhere can participate.

Most recent upgrades

Key dates

MilestoneDate
AnnouncementNov 9, 2026
Launch (competition goes live)Nov 19, 2026
Competition endsDec 1, 2026
Project deadline to resolve all reportsDec 11, 2026
Results frozen and calculatedDec 12, 2026
Final 48-hour dispute deadlineDec 15, 2026
Results publishedDec 24, 2026
Payment completeDec 25, 2026

The dates in this calendar may be adjusted by Immunefi as needed for the execution of the competition.

For more information about Base, please visit https://base.org/.

KYC required

The submission of KYC information is a requirement for payout processing.

Participants must adhere to the Eligibility Criteria.
Additional information: From a restricted country or territory per Immunefi's Terms of Use (https://immunefi.com/terms-of-use/); under 18 years of age (participants under 18 cannot pass KYC and will not receive rewards). Security auditors who participated in an audit of the code in scope may participate only with the project's permission.

Proof of Concept

Proof of concept is always required for all severities.

Prohibited Activities

Program's custom prohibited activities
  • Validity-transaction testing against the public sequencer endpoint (sepolia-sequencer.base.org) is prohibited; use a local devnet.
Default prohibited activities
  • Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
  • Any testing with pricing oracles or third-party smart contracts
  • Attempting phishing or other social engineering attacks against our employees and/or customers
  • Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
  • Any denial of service attacks that are executed against project assets
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty
  • Any other actions prohibited by the Immunefi Rules

Feasibility Limitations

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.

Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.