CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Crypto DAO logo
Crypto DAO
DeFi
Max Payout
$10,000
Project Overview

The Crypto DAO Bug Bounty Program is established to strengthen the security, reliability, and transparency of our decentralized ecosystem. We welcome security researchers, developers, and blockchain experts from around the world to help identify potential vulnerabilities and contribute to the ongoing protection of our protocol and community.

As a decentralized protocol governed by its community, Crypto DAO relies on smart contracts, governance mechanisms, treasury management systems, and other core infrastructure to operate securely and efficiently. We encourage researchers to thoroughly review these components and responsibly disclose any security issues that could affect user funds, protocol integrity, governance processes, or platform functionality.

All valid and verified vulnerability reports will be carefully assessed and rewarded according to their severity and potential impact. Our security team is committed to maintaining an efficient disclosure process, including timely acknowledgment, transparent communication, and fair evaluation of all submissions.

This Bug Bounty Program reflects Crypto DAO’s long-term commitment to security, responsible innovation, and community collaboration. By working together with the global security community, we aim to continuously improve the resilience, trustworthiness, and sustainability of the decentralized ecosystem we are building.

Rewards by Severity
Smart Contract
The bounty will be paid out in USD
Assets In-Scope
https://github.com/CDAOIT/cryptodao-docs
Smart Contract
All the smart contracts are currently used by Gluwa excluding deprecated products
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.
Major
Issues leading to temporary freezing of funds for a limited amount of time.
Medium
Griefing attacks that can damage users or the protocol without profiting the attacker
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.
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 SinceJun 10, 2026
Last Updated1d ago
Funds Reserved$100,000
Max Payout$10,000
KYC
Required
PoC
Required
View on Skynet