CertiK LogoCertiK Logo
BlackCardCoin / BCCoin logo
BlackCardCoin / BCCoin
Payment
DeFi
AI
Max Payout
$1,000
Project Overview

BlackCardCoin is a crypto project focused on bridging the gap between traditional finance and digital assets through its real-world utility: the BlackCard, a crypto credit card. Users can spend their crypto globally without transaction fees, bringing everyday usability to digital currencies. With a strong focus on security, simplicity, and inclusivity, BlackCardCoin envisions a future where spending crypto is as seamless as using fiat.

Rewards by Severity

Program Overview The Blackcardcoin Bug Bounty Program aims to enhance the security and trustworthiness of its blockchain infrastructure and smart contract ecosystem. This initiative invites ethical hackers, developers, and cybersecurity researchers to identify vulnerabilities that could affect protocol integrity, financial safety, or user experience.

Reward Structure Submissions are reviewed using a standardized 4-tier severity model, with rewards based on the impact, exploitability, and type of system affected—whether it be smart contracts, core APIs, or supporting platform components. Higher-severity vulnerabilities that pose real threats to user funds or protocol stability receive greater compensation.

Submission Requirements To qualify for a reward, all bug reports must include a working proof of concept (PoC) and detailed reproduction steps that clearly demonstrate the issue’s impact on an in-scope asset. Submissions that lack code or provide only descriptive analysis without demonstrable results will not be accepted.

Payouts All bounty rewards are denominated and paid in USDT, distributed directly by the Blackcardcoin team upon successful validation of the report and completion of KYC requirements.

Smart Contract
Application/Web
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
Web Application
Website
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
Freezing or shutdown of systems
Unauthorized mint/burn/transfer of assets
Permanent denial of services
Major
Temporary denial of services
Access control is bypassed - including privilege escalation
Theft or permanent freezing of unclaimed yield
Medium
Unexpected logic executions (doesn’t lose value)
Low
Non-intuitive return values
Application/Web
Critical
Non-intuitive return values
Major
Remote code execution and code injection
SQL injection
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
Reflected XSS - DOM XSS and Flash-based XSS
No return value and no in-depth utilization of successful SSRF
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)
Application/Web
Email Spoofing - SPF/DMARC Records Misconfiguration
Clickjacking
Missing best practices in SSL/TLS configuration
Previously known vulnerable libraries without a working Proof of Concept
Unconfirmed reports from automated vulnerability scanners
Reports exploiting the behavior of - or vulnerabilities in - outdated browsers
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions - Login/Logout CSRF
Self-XSS with no security impact
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:
  • Any testing with mainnet or public testnet contracts
  • all testing should be done on private testnets., 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 Scope1
Live SinceJul 25, 2024
Last Updated4mo 28d ago
Funds Reserved$2,000
Max Payout$1,000
Skynet Score
81.86
A
KYC
Required
PoC
Required