Prism Protocol

Submit a Bug
10 March 2022
Live since
KYC required
Maximum bounty

Program Overview

PRISM is a revolutionary derivatives protocol that introduces new asset classes in DeFi, allowing users to manage the risks associated with volatile prices and unstable yields in a simple and capital-efficient manner. PRISM achieves this by refracting digital assets into two distinct parts: a yield component and a principal component.

Currently, investors in digital assets have inadequate ways to raise capital or access liquidity with their holdings. Many choose to pledge these assets as collateral to borrow against their value. Stories of mass liquidations regularly punctuate newsfeeds given typical crypto market volatility and the usual overcollateralization requirement for these secured loans.

PRISM innovates on these inefficiencies and enables users to raise liquidity instantaneously by selling their future yield for a period of their choosing and effectively borrowing against that future yield. Users no longer face any liquidation risk and can maintain a liquid instrument that can be freely traded or deployed elsewhere in DeFi. The same principles can also be used in yield farms or liquidity pools, where returns can reach thousands of percentage points. PRISM will enable users to guarantee their yield and protect against price movements for a period of their choosing. Conversely, as people fix their interest rates, others will be able to buy the instruments created by PRISM and gain increased exposure to an asset’s yield or principal with no risk of liquidation.

For more information about Prism Protocol, please visit

This bug bounty program is focused on their smart contracts and app and is focused on preventing:

  • Theft of user funds
  • Theft of staking yields from the PRISM farm, yLUNA staking, LP incentives etc
  • Manipulation of xPRISM Governance voting
  • Manipulation of pLUNA meta governance voting
  • Domain takeovers
  • Redirection of users’ funds

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, 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 also come with a suggestion for a fix to be considered for a reward.

Governance/vote manipulation is considered as High severity.

The following known issues are considered as out of scope of this program:

Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 200 000 for Critical bug reports.

Prism Protocol 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 Prism Protocol team directly and are denominated in USD. However, payouts are done in UST.

Smart Contract

Up to USD $1,000,000
PoC Required
USD $150,000
PoC Required
USD $50,000
PoC Required

Websites and Applications

USD $200,000
PoC Required

Assets in scope

All smart contracts of Prism Protocol can be found at However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Prioritized Vulnerabilities

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 Contracts/Blockchain

  • Theft of user funds
  • Theft of staking yields from the PRISM farm, yLUNA staking, LP incentives etc
  • Manipulation of xPRISM Governance voting
  • Manipulation of pLUNA meta governance voting
  • Unstaking of other user’s xPRISM from AMPs vault
  • Unstaking of LP positions
  • Unstaking of yLUNA
  • Unbonding of another user’s cLUNA


  • Domain takeover
  • Redirection of user funds

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