CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
B18 logo
B18
Infrastructure
Max Payout
$800
Project Overview

"B18 is an on-chain banking system built on the Base network, based on the B4626 protocol. It aims to establish a comprehensive financial infrastructure for Web3 that supports interest accrual, cyclical operations, liquidation, hedging, and payments.

By introducing a unified “banking semantic layer,” B18 transforms on-chain assets from passive holdings into functional bank-like accounts. This enables users to interact with blockchain-based financial products in a way that closely resembles traditional banking experiences."

Rewards by Severity
Smart Contract
The bounty will be paid out in USDC
Assets In-Scope
https://github.com/b18labs/contracts
Smart Contract
B18 Token
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Smart Contract
Critical
Direct theft of project funds
other than unclaimed rewards.
Direct theft of user funds
other than unclaimed rewards.
Permanent freezing of funds.
Unauthorized mint/burn/transfer of crypto assets
Bad randomness leading to predictable results with serious financial impact.
Governance voting result manipulation.
Protocol insolvency
Major
Issues leading to temporary freezing of funds for a limited amount of time.
Theft or permanent freezing of unclaimed yield and rewards.
Temporary denial of services.
Broken access control leads to high security risks
Medium
Unexpected logic executions (doesn’t lose value)
Smart contract unable to operate due to lack of funds or misconfiguration.
Griefing attacks that can damage users or the protocol without profiting the attacker
Block stuffing for profit.
Low
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official documentation.
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters.
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Smart Contract
Incorrect data supplied by third party oracles (Not to exclude oracle manipulation/flash loan attacks)
Basic economic governance attacks (e.g. 51% attack)
Not following best practices
with no security risk.
Sybil attacks
Issues with no security or financial impact.
Program Rules
  • Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services., Do not attempt to perform brute-force attacks or denial-of-service attacks., Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
The following activities are prohibited by this bug bounty program:
  • Social engineering (e.g. phishing
  • vishing
  • smishing) of any kind.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope1
Live SinceMar 28, 2026
Last Updated1d ago
Funds Reserved$100,000
Max Payout$800
Skynet Score
78.65
BBB
KYC
Required
PoC
Required
View on Skynet