CertiK LogoCertiK Logo
Shieldeum logo
Shieldeum
AI
DePIN
Infrastructure
Max Payout
$5,000
Project Overview

Shieldeum is a decentralized physical infrastructure network (DePIN) focused on delivering Web3 cybersecurity solutions for cryptocurrency users and enterprises. Leveraging data center servers, Shieldeum provides application hosting, data encryption, threat detection, and high-performance computing services to safeguard assets and enhance security across the blockchain ecosystem.

Rewards by Severity

Program Overview Shieldeum operates a bug bounty program to uphold the security and robustness of its ecosystem. Designed for developers, ethical hackers, and security experts, the program focuses on identifying vulnerabilities in the core components of the Shieldeum platform, including smart contracts and infrastructure services. By encouraging responsible disclosure, Shieldeum aims to maintain high software security standards and reduce the risk of user fund loss.

Reward Structure Submissions are evaluated under a 4-tier severity model, with rewards varying based on the criticality of the issue and the system component affected. Higher-tier rewards are reserved for vulnerabilities that pose a substantial risk to user assets or platform integrity. All reports are subject to internal review and classification by the Shieldeum security team.

Submission Requirements To qualify for a reward, all bug reports must include a valid proof of concept (PoC) along with detailed steps to reproduce the vulnerability. The report must demonstrate real-world impact on an in-scope asset. Submissions that only contain explanations or lack executable code will not be considered.

Payouts Bounties are denominated in USD and paid in USDT, issued by the Shieldeum team upon successful validation and KYC completion.

Smart Contract
The bounty will be paid out in USDT
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 user funds other than unclaimed rewards
Major
Theft or permanent freezing of unclaimed yield and rewards
Broken access control leads to high security risks
Medium
Smart contract unable to operate due to lack of funds or misconfiguration
Low
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official documentation
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters
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.
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 SinceNov 11, 2024
Last Updated2mo 21d ago
Funds Reserved$50,000
Max Payout$5,000
Skynet Score
86.18
A
KYC
Required
PoC
Required