Welcome to the DEEPSPACE Metaverse!
DEEPSPACE is a Play-to-Earn space multiverse exploration strategy game!
Earn passive income from holding $DPS, trading proprietary, upgradeable, smart NFTs, and taking risks as you explore DEEPSPACE with your fleet of ships!
Prepare to explore, harvest, and fight your way through the DEEPSPACE universe!
DEEPSPACE - Outpost
One of the crown jewels of the DEEPSPACE Metaverse is the Outpost. The Outpost is a decentralized exchange hub where you can buy, sell, and trade your ships, cores, and other upgradeable Smart NFTs with fellow explorers. You can use the marketplace to build limited edition ships and acquire other valuable collectible assets. Build up your fleet to explore, harvest, and fight your way through the DEEPSPACE universe!
Players buy and sell land, weapons, spacecraft and other items to help them in exploring the platform in the marketplace.
Players can gain value as they advance in the game and grow their ship fleet. The custom decentralized app (dapp) marketplace is integrated with the rest of the DEEPSPACE (DPS) platform to allow for quick connection players looking for items to trade to help further their progress in the metaverse game.
Ship modifications, whether temporary or permanent, can all be transacted on the marketplace.
DEEPSPACE - Game
Game assets such as ships and equipment are blockchain NFTs, allowing gamers to have full ownership over all of their in-game assets. Players can mint their own starships or purchase from the proprietary NFT marketplace, and choose up to 4 ships from their fleet to the start of the game to explore, engage and discover planets, places and players within the 3D space-based metaverse.
Four starship archetypes allow you to explore the universe openly, engage in combat, or mine resources:
- Fighters - Ships with state of the art weapon technology
- Tank - Ships designed for managing enemy engagements, longevity, and withstanding damage.
- Mining - Ships specially engineered for efficient resource collection
- Support - A ship focused on utility and boosting the capabilities of your other ships.
Each ship has their own benefits in the form of 8 different stats: attack, special attack, shields, special defense, speed, luck, mining, and health.
Players can apply permanent and temporary modifications as they play. Modifications allow for many added battle benefits, situational adaptability and other stats. Temporary modifications give players single use bonuses during gameplay with specific use and unique outcomes.
Resource mining allows players to gather raw materials, like ore, for ship or property add-ons and modifications. Mined materials will allow you to customize your ships, creating a unique experience for anyone who plays.
Battles occur frequently within the game, battles can take one of two forms:
- Player vs Player (PvP) - PvP will allow others to battle against each other for prizes, leaderboard placement, and bragging rights.
- Player-vs-Environment (PvE) - PvE involves battling Non-Playable Characters (NPCs; i.e. game-based Artificial intelligence (AI) players) throughout the game as a mechanism for winning rewards that can yield profits for earnings.
For more information about DeepSpace please visit https://deepspace.game/.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.1. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All web/app bug reports must come with a Proof of Concept (PoC) with an end-effect impacting an asset-in-scope in order to be considered for a reward. All High and Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
All vulnerabilities marked in the Certik security review are not eligible for a reward.
Payouts are handled by the DEEPSPACE team directly and are denominated in USD. However, payouts are done in a mix of DPS, BNB and BUSD, with the choice of the ratio at the discretion of the team.
- USD $50,000
- USD $30,000
- USD $5,000
Websites and Applications
- USD $5,000
- USD $2,500
- USD $1,000
Assets in scope
- Smart Contract - DPS TokenType
- Websites and Applications - OutpostType
- TargetWebsites and Applications - Main Web AppType
- Websites and Applications - AssetsType
- Websites and Applications - BSGType
All smart contracts of DEEPSPACE can be found at https://github.com/deepspace-game. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
If an impact can be caused to any other asset managed by DEEPSPACE that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
- Any governance voting result manipulationCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Miner-extractable value (MEV)CriticalImpact
- Protocol InsolvencyCriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumptionMediumImpact
- Temporary freezing of funds for any amount of timeMediumImpact
Websites and Applications
- Execute arbitrary commands on production serversCriticalImpact
- Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)CriticalImpact
- Taking down the application/websiteCriticalImpact
- Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.CriticalImpact
- Subdomain takeover without already-connected wallet interactionCriticalImpact
- Direct theft of user fundsCriticalImpact
- Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactionsCriticalImpact
- Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.HighImpact
- Improperly disclosing confidential user information such as email address, phone number, physical address, etc.HighImpact
- Subdomain takeover without already-connected wallet interactionHighImpact
- Changing non-sensitive details of other users (including modifying browser local storage) w/o already-connected wallet interaction & with up to one click of user interaction, such as changing the first/last name of user, or enabling/disabling notificationsMediumImpact
- Open Redirect in H2O production’s environmentMediumImpact
Out of Scope & Rules
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- Attacks that the reporter has already exploited themselves, leading to damage
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist)
- Attacks that rely on social engineering
Smart Contracts and Blockchain
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
- Centralization risks
Websites and Apps
- Theoretical vulnerabilities without any proof or demonstration
- Content spoofing / Text injection issues
- Captcha bypass using OCR
- CSRF with no security impact (logout CSRF, change language, etc.)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
- Server-side information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring unlikely user actions
- URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Attacks requiring privileged access from within the organization
- Feature requests
- Best practices
- Vulnerabilities primarily caused by browser/plugin defects
- Any vulnerability exploit requiring CSP bypass resulting from a browser bug
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
- Any testing with pricing oracles or third party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty