PERI Finance

Submit a Bug
16 June 2021
Live since
Yes
KYC required
$3,000
Maximum bounty

Program Overview

PERI Finance is a decentralized cross-chain synthetic issuance and derivative exchange protocol that provides unlimited liquidity on the Polkadot network. It gives an opportunity to access a wide range of both traditional financial and crypto assets in the forms of leveraged and none-leveraged synthetic products. We empower you with lower GAS fees, speedy transactions, and ample security from front-running or flash loans.

For more information about PERI Finance, please visit https://www.pynths.com/.

The bug bounty program covers its smart contracts and staking page and is focused on the prevention of loss of user funds.

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. 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 web and app bugs must come with a PoC in order to be accepted. All web and app bug reports without a PoC will be rejected with a request for a PoC.

The final decision of the reward, which is affected by the exploitability of the bug report, is done by the PERI Finance team.

Payouts are handled by the PERI Finance team directly and are denominated in USD. Payouts are done in USDT.

Smart Contract

Critical
Level
USD $1,000 - USD $3,000
Payout
High
Level
USD $500 - USD $1,000
Payout
Medium
Level
USD $300 - USD $500
Payout
Low
Level
USD $100 - USD $300
Payout

Websites and Applications

Critical
Level
USD $500
Payout
PoC Required
High
Level
USD $300
Payout
PoC Required
Medium
Level
USD $200
Payout
PoC Required
Low
Level
USD $100
Payout
PoC Required

Assets in scope

Only web/app vulnerabilities that directly affect the web/app assets listed in this table are accepted within the bug bounty program. All others are out-of-scope.

Under the GitHub link, only the smart contract vulnerabilities that affect the following processes are accepted and are eligible for a reward.

  • Staking PERI/USDC(Issue pUSD)
  • Unstaking PERI/USDC(burn Pynths)
  • Claiming(Inflationary Reward)

All testnet and mock smart contracts, even those that are around Staking, Unstaking, and Claiming, are considered as out-of-scope for this 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.

Smart Contract

  • Critical Smart Contract Impact
    Critical
    Impact
  • High Smart Contract Impact
    High
    Impact
  • Medium Smart Contract Impact
    Medium
    Impact
  • Low Smart Contract Impact
    Low
    Impact

Websites and Applications

  • Critical Websites and Applications Impact
    Critical
    Impact
  • High Websites and Applications Impact
    High
    Impact
  • Medium Websites and Applications Impact
    Medium
    Impact
  • Low Websites and Applications Impact
    Low
    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

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 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