CertiK LogoCertiK Logo
Shade Protocol logo
Shade Protocol
DeFi
Privacy
DEX
Max Payout
40000 SHD
Project Overview

Shade Protocol is a suite of interconnected, privacy-focused DeFi applications built on Secret Network. At its core is Silk, an overcollateralized stablecoin that offers native transactional privacy by default. Designed to protect user data while enabling powerful financial tools, Shade Protocol brings privacy-preserving DeFi infrastructure to the Secret Network ecosystem.

Rewards by Severity

Program Overview Shade Protocol runs a security-focused bug bounty program to identify vulnerabilities within its privacy-preserving smart contracts, frontend applications, and voting mechanisms. The program is designed to enhance the security of its confidential DeFi infrastructure by encouraging responsible disclosures from the security community.

Reward Structure The program uses a 4-tier severity model with distinctions based on both the target type and impact. For critical smart contract vulnerabilities, rewards are capped at 10% of the potential economic damage, primarily based on the funds at risk. In scenarios involving repeatable attacks, only the first instance is considered—unless the contract in question cannot be upgraded or paused. High-severity smart contract vulnerabilities are capped at 100% of the affected funds.

For critical website and application vulnerabilities, the payout is 10,000 SHD only if the impact causes direct loss of funds, vote manipulation, or visual misrepresentation of votes or results. All other critical frontend or app issues that do not meet these criteria will be rewarded 1,000 SHD. Reward values are calculated based on on-chain conditions at the time the bug report is submitted.

Submission Requirements All bug reports must include a working proof of concept (PoC) and clear steps to reproduce the issue. The report must demonstrate real impact on an in-scope asset or system component. Reports without code or tangible outcomes will not qualify for rewards.

Payouts Bounties are denominated in USD-equivalent value and paid in SHD, the native token of Shade Protocol. Payouts are issued by the Shade team after successful validation and KYC compliance.

Smart Contract
The bounty will be paid out in SHD
Assets In-Scope
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.
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.
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.
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., https://github.com/securesecrets/shade/blob/main/Shade_Protocol_Responsible_Disclosure.md
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 Scope4
Live SinceMay 7, 2023
Last Updated1mo 2d ago
Funds Reserved167000 SHD
Max Payout40000 SHD
Skynet Score
89.00
AA
KYC
Required
PoC
Required