Skip to content
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Cannot retrieve contributors at this time

ParaSpace Bug Bounty

Bounty Guideline

  • Active Since: Apr 4th, 2023
  • Accept Threat Level: Critical, High, Medium
  • PoC required: Yes
  • Medium Reward: 3,000 USD
  • High Reward: 10,000 USD
  • Critical Reward: 200,000 USD
  • KYC Required for Reward: No
  • Submit Bug -> Submit

Project Overview

ParaSpace is a decentralized protocol with a foundation of providing lending and borrowing services for various assets on the Ethereum blockchain. Users can lend their NFTs and ERC-20 tokens to earn income in the form of interest, as well as use their lended assets as collateral for borrowing assets. One of the main entry bars for retail users into the NFT market is the high price of NFT items, especially blue-chip NFTs, therefore, ParaSpace introduces its Marketplace, allowing users to access NFTs through leveraged buy and leveraged bid, using the purchased item as collateral for the outstanding loan.

The ParaSpace protocol aims to provide users access to cash and profits without selling their assets. ParaSpace uses a pool-based money market model whereby users supply their assets to a pool to earn interest and instantly borrow from the pool when collateralizing their asset.

For more information about ParaSpace, please visit

Reward by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Secure3 Bug Bounty Severity Definition. 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 bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. In addition, all bug reports must come with a suggestion for a fix in order to be considered for a reward.

Known issues highlighted in the following audit reports are considered out of scope:

To be eligible for a reward under this Program, you must:

  • Discover a previously unreported, non-public vulnerability within the scope of this Program. Vulnerabilities must be distinct from the issues covered in the previously conducted publicly available audits.
  • Be the first to disclose the unique vulnerability to the Team by the disclosure requirements below. If similar vulnerabilities are reported, the first submission shall be rewarded (if determined valid and otherwise in the scope of this Program).
  • Possess sufficient technical knowledge and provide sufficient information necessary to reproduce and fix the vulnerability.
  • Not engage in any unlawful conduct when disclosing the bug, including through threats, demands, or any other coercive tactics.
  • Not exploit the vulnerability in any way, including by making it public or obtaining a profit (other than a reward under this Program). Any publicity in any way, whether direct or indirect, relating to any bug or vulnerability will automatically disqualify it and you from the Program.
  • Make a good faith effort to avoid privacy violations, data destruction, interruption or degradation of ParaSpace.
  • Submit only one vulnerability per submission unless you need to chain vulnerabilities to impact any vulnerabilities. If you want to add more information to a provided issue, create a new submission referencing the initial one.
  • Not submit a separate vulnerability caused by an underlying issue that is the same as an issue on which a reward has been paid under this Program. However, if a vulnerability is found that bypasses a previous fix that was deployed, it will still be considered within the scope of this program.

Payouts are handled by the ParaSpace team directly and are denominated in USD. However, payouts are conducted in USDC. Future payouts may be done in our own protocol token, at the discretion of the team.

Impacts in Scope


  • Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
  • Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties
  • Permanent freezing of user funds
  • Permanent freezing of user NFTs
  • Unauthorized minting of NFTs
  • Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)
  • Protocol insolvency


  • Theft of unclaimed yield
  • Theft of unclaimed royalties
  • Permanent freezing of unclaimed yield
  • Permanent freezing of unclaimed royalties
  • Temporary freezing of funds for at least 24 hours
  • Temporary freezing NFTs for at least 24 hours

KYC Requirement


Asset In Scope

Out of Scope & Rules

The following vulnerabilities are excluded from the rewards for this bug bounty program:

Vulnerabilities related to domains, DNS or servers of websites

  • Any already-reported bugs
  • 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)

Smart Contracts and Blockchain

  • Vulnerabilities already reported and/or discovered in contracts built by third parties on ParaSpace
  • Bugs in any third party contract or platform that interacts with ParaSpace
  • 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

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