CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
bitsCrunch logo
bitsCrunch
AI
NFT
Marketplace
Max Payout
$25,000
Project Overview

bitsCrunch is a security-first Web3 analytics platform committed to safeguarding the integrity of decentralized networks. Through its proactive Bug Bounty Program, bitsCrunch invites ethical hackers and security researchers to identify and report vulnerabilities, strengthening the ecosystem through community-driven defense. By prioritizing transparency, data integrity, and collective intelligence, bitsCrunch plays a vital role in securing the future of Web3 infrastructure.

Rewards by Severity

Program Overview BitsCrunch operates a formal bug bounty program to identify and resolve security vulnerabilities across its smart contracts and platform components. The initiative is a core part of BitsCrunch’s mission to ensure trust, data integrity, and platform resilience.

Reward Structure All submissions are evaluated under a 4-tier severity model, with rewards varying according to the criticality of the vulnerability and whether it affects a smart contract or frontend system. For critical smart contract vulnerabilities, rewards are capped at 10% of the economic damage, factoring in both the funds at risk and broader impacts such as brand and PR concerns, at the discretion of the team. High-severity smart contract issues are also capped at up to 10% of affected funds. All calculations of funds at risk are based on the conditions present at the time of the bug report submission.

Submission Requirements A working proof of concept (PoC) is required for all reports. Submissions must include sufficient technical detail to demonstrate the vulnerability and its exploitability on an in-scope target. Reports without a functional PoC will not be considered.

Payouts All bounties are denominated in USD and distributed in BCUT, the native token of BitsCrunch. Payouts are processed directly by the BitsCrunch team upon successful verification and completion of KYC.

Smart Contract
Application/Web
The bounty will be paid out in BCUT
Assets In-Scope
Target
Severity
Name
https://github.com/bitscrunch-protocol/smartcontracts/tree/external-audits
Smart Contract
bitsCrunch Protocol Contracts
https://app.bitscrunch.com/
Web Application
bitsCrunch Protocol Interface
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 any user funds - whether at-rest or in-motion - other than unclaimed yield
Freezing or shutdown of systems
Major price manipulation (>=50)
Unauthorized mint/burn/transfer of assets
Permanent denial of services
Double spending
Protocol insolvency
Major
Minor price manipulation
Temporary denial of services
Temporary freezing of funds for any amount of time
Access control is bypassed - including privilege escalation
Theft or permanent freezing of unclaimed yield
Medium
Unexpected logic executions (doesn’t lose value)
Users could lose funds due to rounding
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Weak random sources
Low
Non-intuitive return values
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official repo
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters
Application/Web
Critical
Non-intuitive return values
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official repo
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters
Major
Remote code execution and code injection
SQL injection
Obtaining high-impact sensitive information from the internal system
XXE/XML injection vulnerability with high-security impact
Authentication and authorization bypass with high impact
Wormable stored XSS
Large scale account takeover
Leakage of a lot of source code
Medium
Account takeover
Stored XSS on general pages
CSRF involving core business
IDOR with medium security impact/Horizontal and Vertical Privilege Escalation
The leakage of locally-stored sensitive authentication key information
Medium impact information disclose
Low
General information leakage - such as web path traversal - system path traversal - directory browsing etc
Reflected XSS - DOM XSS and Flash-based XSS
SMS bombs - mail bombs (each system only accepts one type of this vulnerability)
No return value and no in-depth utilization of successful SSRF
Other vulnerabilities with low-security impact
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
Best practice critiques
Centralization risks
Application/Web
Missing best practices in SSL/TLS configuration
Previously known vulnerable libraries without a working Proof of Concept
Program Rules
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward.
  • Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
  • 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:
  • Automated testing of services that generate significant amounts of traffic.
  • Public disclosure of an unpatched vulnerability in an embargoed bounty.
  • 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 Scope2
Live SinceDec 21, 2023
Last Updated2mo 18d ago
Funds Reserved$100,000
Max Payout$25,000
Skynet Score
91.85
AA
KYC
Required
PoC
Required
View on Skynet