CertiK LogoCertiK Logo
Shade Protocol logo
Shade Protocol
DeFi
Privacy
DEX
Max Payout
$120,000
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.

Infrastructure
Smart Contract
Application/Web
The bounty will be paid out in SHD
Assets In-Scope
Target
Severity
Name
Application/Web
Shade Website
Application/Web
Shade 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.
Infrastructure
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
Access to any central keys address controlled by the project (e.g. private keys; seed phrases; etc.)
Access to Central Database
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
Low
Underpricing transaction fees relative to computation time
Griefing (e.g. triggering abnormally high gas fees for everyone or abnormal cpu consumption for validator/mining nodes)
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
Governance Voting Result Manipulation
Major
Faulty usage of proxy patterns
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)
Smart contract unable to operate due to lack of token funds
Theft of gas
Unbounded gas consumption
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
Contract fails to deliver promised returns; but doesn’t lose value
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
Taking down the website/application
Execute arbitrary system commands
Retrieve sensitive data from a server
Taking state-modifying authenticated actions on behalf of other users with any interaction by that users.
Subdomain takeover with already connected wallet interaction
Malicious interactions with an already-connected wallet
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
Improperly disclosing confidential user information
Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction.
Injecting/modifying the static content on the target application without Javascript (Persistent) such as: HTML injection without Javascript; Replacing existing text with arbitrary text; Arbitrary file uploads; etc.
Medium
Account takeover
Stored XSS on general pages
CSRF involving core business; etc
IDOR with medium security impact/Horizontal and Vertical Privilege Escalation
The leakage of locally-stored sensitive authentication key information
Medium impact information disclose
Injecting/modifying the static content on the target application without Javascript (Reflected) such as: - Reflected HTML injection - Loading external site data
Redirecting users to malicious websites (Open Redirect)
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
Taking over broken or expired outgoing links
Disabling access to site for users
Preventing connection to wallet
Cookie bombing
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.
Infrastructure
Centralization risks
Best practice critiques
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)
Best practice critiques
Sybil attacks
Centralization risks
Application/Web
Email Spoofing - SPF/DMARC Records Misconfiguration
Clickjacking
Any activity that could lead to the disruption of our service (DoS)
Missing best practices in SSL/TLS configuration
Previously known vulnerable libraries without a working Proof of Concept
Issues that require unlikely user interaction
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
Non-Sensitive Data Disclosure - for example server version banners
CSV/formula injection
Self-XSS with no security impact
CORS misconfiguration with no security impact
Missing HttpOnly or Secure flags on cookies
Presence of autocomplete attribute on web forms
Any vulnerability exploit requiring CSP bypass resulting from a browser bug
Vulnerabilities primarily caused by browser/plugin defects
Attacks requiring privileged access from within the organization
Lack of SSL/TLS best practices
DNS Sabotage
Feature requests
Captcha bypass using OCR
DDoS vulnerabilities
URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
Server-side information disclosure such as IPs; server names; and most stack traces
Missing HTTP Security Headers or cookie security flags
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.
  • Unless otherwise noted
  • users should create accounts for testing purposes.
  • Users must submit a Proof of Concept (PoC) in order to receive bounties for bug reports. Example PoC can be found in the Shade Security Advisories: https://github.com/securesecrets/shade/security/advisories
  • See all Program Rules Here: https://github.com/securesecrets/shade/blob/main/Shade_Protocol_Resposible_Disclosure.md
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.
  • Misrepresenting assets in scope: claiming that a bug report impacts/targets an asset in scope when it does not
  • Misrepresenting severity: claiming that a bug report is critical when it clearly is not
  • Harassment, i.e., excessive, abusive, or bad faith communication
  • Publicly disclosing a bug report--or even the existence of a bug report for a specific project--before it has been fixed and paid
  • Publicly disclosing a bug report deemed to be a duplicate or well-known to the project
  • Submitting spam/very low-quality bug reports and submitting information through our platform that is not a bug report
  • Submitting AI-generated/automated scanner bug reports
  • Unauthorized disclosure or access of sensitive information beyond what is necessary to submit the report.
  • See all prohibited activities here: https://github.com/securesecrets/shade/blob/main/Shade_Protocol_Resposible_Disclosure.md
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 Scope22
Live SinceMay 7, 2023
Last Updated2mo 16d ago
Funds Reserved$167,000
Max Payout$120,000
Skynet Score
87.33
AA
KYC
Required
PoC
Required