pStake

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.

At present, pSTAKE supports Binance (BNB), Cosmos (ATOM), Persistence (XPRT), and Ethereum (ETH) networks’ native tokens, with a view to support more chains and assets in the future (SOL, and AVAX).

Binance Labs is supporting pSTAKE to develop a liquid staking solution for the Binance chain in order to unlock liquidity of staked BNB and boost the growth of DeFi. pSTAKE’s BNB liquid staking product allows holders of BNB to stake their assets using the pSTAKE staking interface. Users are then issued stkBNB that can be used in DeFi to generate high yields.

For more information about pStake’s liquid staking product for BNB, please visit https://pstake.finance/bnb

Rewards are distributed according to the impact of the vulnerability based on the 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
• Halborn Audit Report

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.

Smart Contract

Websites and Applications

All smart contracts of pStake can be found at 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.

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
• Attacks requiring physical access to the victim device
• Attacks requiring access to the local network of the victim
• Reflected plain text injection ex: url parameters, path, etc.
  • This does not exclude reflected HTML injection with or without javascript
  • This does not exclude persistent plain text injection
• Self-XSS
• Captcha bypass using OCR without impact demonstration
• CSRF with no state modifying security impact (ex: logout CSRF)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
• Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used only to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Feature requests
• Issues related to the frontend without concrete impact and PoC
• Best practices issues without concrete impact and PoC
• Vulnerabilities primarily caused by browser/plugin defects
• Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
• Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass

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