Partisia

Submit a Bug
03 March 2022
Live since
Yes
KYC required
$50,000
Maximum bounty

Program Overview

The Partisia Blockchain Foundation’s mission is to establish a WEB 3.0 infrastructure with no single point of trust for generic coordination of public and private information to be used by all applications across all platforms.

The Partisia Blockchain is built for trust, transparency, privacy, and speed of light finalization by combining secure multiparty computation (MPC) and blockchain technology.

For more information about Partisia, please visit https://partisiablockchain.com/.

This bug bounty program is focused on their blockchain infrastructure, smart contracts and wallet app and is focused on preventing:

  • Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)
  • Direct loss of funds
  • Any governance voting result manipulation
  • Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
  • Permanent freezing of funds
  • Protocol Insolvency
  • Wallet interaction modification resulting in financial loss
  • Direct theft of user funds
  • Signing transactions for other users

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

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.

Partisia requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is a National ID scan along with a selfie.

Payouts are handled by the Partisia team directly and are denominated in USD. However, payouts are done in USDC.

Blockchain/DLT

Critical
Level
USD $50,000
Payout
PoC Required
High
Level
USD $25,000
Payout
PoC Required

Smart Contract

Critical
Level
USD $50,000
Payout
PoC Required
High
Level
USD $25,000
Payout
PoC Required

Websites and Applications

Critical
Level
USD $25,000
Payout
PoC Required
High
Level
USD $5,000
Payout
PoC Required

Assets in scope

All smart contracts of Partisia can be found at https://gitlab.com/partisiablockchain/. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

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.

Blockchain/DLT

  • Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)
    Critical
    Impact
  • Direct loss of funds
    Critical
    Impact
  • Permanent freezing of funds (fix requires hardfork)
    Critical
    Impact
  • DoS of greater than 30% of validator or miner nodes and does not shut down the network
    High
    Impact
  • Theft of unclaimed bp rewards
    High
    Impact
  • Network not being able to confirm new transactions (Total network shutdown)
    High
    Impact

Smart Contract

  • Any governance voting result manipulation
    Critical
    Impact
  • Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
    Critical
    Impact
  • Permanent freezing of funds
    Critical
    Impact
  • Wallet interaction modification resulting in financial loss
    Critical
    Impact
  • Temporary freezing of funds
    High
    Impact
  • Theft of gas and unbounded gas consumption
    High
    Impact

Websites and Applications

  • Direct theft of user funds
    Critical
    Impact
  • Signing transactions for other users
    Critical
    Impact
  • Wallet interaction modification resulting in financial loss
    Critical
    Impact
  • Tampering with transactions submitted to the users wallet
    High
    Impact
  • Privilege escalation to access unauthorized functionalities to relative to repositories
    High
    Impact
  • Redirecting users to malicious websites
    High
    Impact
  • SDK Man in the middle attacks
    High
    Impact

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)

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
  • Self-XSS
  • 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

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