All smart contracts of pStake can be found at [https://github.com/persistenceOne/stkBNB-contracts/tree/main/contracts](https://github.com/persistenceOne/stkBNB-contracts/tree/main/contracts). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

pSTAKE is a liquid staking protocol that unlocks liquidity for your staked assets. With pSTAKE, users can securely stake their Proof-of-Stake (PoS) assets, participate in protocol improvements and security to earn staking rewards, and receive staked underlying representative tokens (stkASSETs) which can be used to explore additional yield opportunities across DeFi.

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Execute arbitrary system commands

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)

Taking down the application/website

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.

Direct theft of user funds

Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

Theft of unclaimed yield

Temporary freezing of funds

Acquiring owner/admin rights or roles without contract’s owner/admin action

Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.

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.

Improperly disclosing confidential user information such as email address, phone number, physical address, etc.

Smart contract unable to operate due to lack of token funds

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Changing non-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 changing the first/last name of user, or en/disabling notification

Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data

Redirecting users to malicious websites (Open Redirect)

Smart contract fails to deliver promised returns, but doesn’t lose value

Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction such as iframing leading to modifying the backend/browser state (demonstrate impact with PoC)

Any impact involving a publicly released CVE without a working PoC

Taking over broken or expired outgoing links such as social media handles, etc.

Temporarily disabling user to access target site, such as locking up the victim from login, cookie bombing, etc.

Subdomain takeover with already-connected wallet interaction

Subdomain takeover without already-connected wallet interaction

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2). 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.

__Smart Contracts Rewards Breakdowns__

Smart Contracts (Critical):
  - Loss of user funds:
    - 10% of assets at risk, minimum __USD 50 000__, maximum __USD 300 000__
  - Loss of non-user funds (e.g. treasury):
    - 10% of assets at risk, minimum __USD 25 000__, maximum __USD 200 000__

Smart Contracts (High):
  - 10% of assets at risk
  - Minimum __USD 20 000__, maximum of __USD 100 000__

Previous issues highlighted in the following audit reports are considered out of scope: 
  - [PeckShield Audit Report](https://github.com/persistenceOne/pStake-auditReports/blob/main/stkBNB/pStake_stkBNB_Smart_Contract_Audit_Peckshield%20%5B04.07.2022%5D.pdf)
  - [Halborn Audit Report](https://github.com/persistenceOne/pStake-auditReports/blob/main/stkBNB/pSTAKE_stkBNB_Smart_Contract_Audit_Halborn%20%5B05.08.2022%5D.pdf)

In addition, the following issues are known and considered out of scope of the program: 

The gas consumed by claim __All()__ depends on the number of unstake requests made by the user calling the __claimAll()__ function. The higher the number of unstake requests made by the user, the higher the gas usage of the __claimAll()__ function will be. The more unstake requests they create, the more gas they will have to pay for __claimAll()__.
  - The following contracts have Admin/Owner roles in them:
    - AddressStore
    - FeeVault
    - stkBNB Token
    - StakePool
    - TimelockedAdmin

Payouts are handled by the __pStake__ team directly and are denominated in USD. However, payouts are done in __PSTAKE__, __BUSD__ or __USDC__, at the discretion of the team.

pStake

Resources & Documentation