CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Qubetics logo
Qubetics
Infrastructure
Layer 1
Stablecoin
Max Payout
$5,000
Project Overview

Qubetics Network is a revolutionary Layer-1, EVM-compatible, aggregated multichain blockchain designed to unify leading blockchain networks and redefine decentralized infrastructure. As the world’s first of its kind, Qubetics bridges ecosystems such as Ethereum, Solana, Cosmos, and Bitcoin—enabling seamless cross-chain interactions. With a focus on scalability, security, and interoperability, Qubetics sets a new standard for dApps, digital payments, and asset tokenization across the decentralized web.

Rewards by Severity

Program Overview The Qubetics Bug Bounty Program is designed to fortify the security of Qubetics’ Layer 1 blockchain, which bridges Bitcoin and Ethereum ecosystems. By inviting ethical hackers, developers, and security researchers to identify vulnerabilities across its protocol, smart contracts, and applications, Qubetics aims to ensure the resilience of its cross-chain infrastructure and advance the future of interoperable Web3 systems.

Reward Structure Bug submissions are evaluated using a standardized 4-tier severity model, with rewards reflecting the criticality and impact of the vulnerability. For critical smart contract vulnerabilities, rewards are capped at 10% of the economic damage, with funds at risk and reputational considerations assessed at the time of submission. High-severity vulnerabilities may receive up to 100% of the affected funds. The maximum payout for a single report is 5,000 TICS.

Submission Requirements All reports must include a functioning proof of concept (PoC) and reproduction steps that demonstrate how the vulnerability impacts an in-scope asset. Submissions lacking executable code or real-world impact will not be considered for rewards.

Payouts All bug bounty rewards are denominated and paid in TICS, and distributed after successful validation of the submission.

Smart Contract
Web Application
Blockchain
The bounty will be paid out in TICS
Assets In-Scope
Target
Severity
Name
https://github.com/Qubetics
Blockchain
All blockchain modules
https://github.com/Qubetics
Smart Contract
Qubetics Smart Contract Assets — Includes all EVM and Cosmos-compatible contracts deployed as part of the Chain Abstraction protocol. This covers intent-based execution logic, cross-chain asset transfer contracts, MPC-powered Escrow Vaults, the Liquidity Provider Network (LPN), and the Cross-Chain Wallet Tracking Extension (CWTE). These assets facilitate secure, trustless interactions between Bitcoin, Ethereum, and other supported chains through Qubetics’ unified Layer 1 framework.
https://testnet.qubetics.work/dashboard
Web Application
Dashboard
https://validator-testnet.qubetics.work/login
Web Application
Validator
https://delegator-testnet.qubetics.work/login
Web Application
Delegator
https://qubeqode-basic-testnet.qubetics.work/work-space
Web Application
QubeQode
https://testnet-qubecode-ide.qubetics.work/#lang=en&optimize=false&runs=200&evmVersion=paris&version=soljson-v0.8.26+commit.8a97fa7a.js
Web Application
Testnet Qubecode
https://play.google.com/store/apps/details?id=com.qubetics.wallet
Web Application
Qubetics Wallet
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
Web Application
Critical
Remote code execution enabling attackers to compromise the entire system
Direct theft of user and project's assets(e.g. NFTs; tokens)
Unauthorized access allowing full control over user accounts or wallets
Access to sensitive internal data (private keys; database and server credentials)
Unauthorized alteration of NFT Metadata
Subdomain(with already-connected wallet) takeover or availability disruption of critical assets (e.g. NFT URI; RPC server)
Major
Sensitive user data disclosed for a large amount of users (p.e. physical address; email; phone number)
Stored Cross-Site Scripting (XSS) without limitations
Access sensitive data from the database through SQL injection
Bypass of essential authentication mechanisms granting administrative privileges
Unauthorized access to functions that modify sensitive user or application data
Server-Side Request Forgery (SSRF) vulnerabilities leading to unauthorized sensitive data access or manipulation of internal systems
Public access to wallet information without connecting the wallet
Medium
Unauthorized access to non-critical user data
Security misconfigurations that could be exploited under certain conditions
Limited Cross-Site-Scripting (XSS)
Malicious redirection without interaction on domains with already-connected wallet
Low
Minor information disclosure of sensitive data with low security risk
UI or UX bugs causing serious user confusion
Use of deprecated or outdated security practices that can cause security risk
Validation errors that lead to low-security risk
HTML and text injection in sensitive features with a low security risk
Other vulnerabilities with low-security impact
Blockchain
Critical
Network not being able to confirm new transactions (Total network shutdown)
Unintended permanent chain split requiring hard fork
Permanent freezing of funds(fix requires hard fork)
Transaction/consensus manipulation
Unauthorized token minting
Major
Unintended chain split (fix not requiring hard fork)
Transient consensus failures
Bad/incorrect usage of cryptography primitives
Validator selection set manipulation
Medium
High compute consumption by validator/mining nodes
Vulnerability in RPC API (except via DDoS attack)
Attacks against thin clients
Unhandled on-chain errors affecting a user corner case
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
Centralization risks
Issues with no security or financial impact
Web Application
Best practice recommendations
Non-Sensitive Data Disclosure
Attacks requiring physical access to a user's device
Exposure of non-sensitive API keys
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions - Login/Logout CSRF
Reports exploiting the behavior of - or vulnerabilities in - outdated browsers
Unconfirmed reports from automated vulnerability scanners
Issues that require unlikely user interaction
Previously known vulnerable libraries without a working Proof of Concept
Missing best practices in SSL/TLS configuration
Any activity that could lead to the disruption of our service (DoS)
Email Spoofing - SPF/DMARC Records Misconfiguration
Spam / Flooding
Tab nabbing
Social engineering
Presence of autocomplete attribute on web forms
CORS misconfiguration with no security impact
Self-XSS with no security impact
CSV/formula injection
Missing HTTP security headers or cookie flags without demonstrated impact
Clickjacking with no security impact
Blockchain
Centralization risks
Best practice critiques
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 Scope8
Live SinceJun 6, 2025
Last Updated2mo 17d ago
Funds Reserved$30,000
Max Payout$5,000
Skynet Score
85.50
A
KYC
Required
PoC
Required
View on Skynet