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.
PoC required
Rewards by Threat Level
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:
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.
Program Overview
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
KYC not required
No KYC information is required for payout processing.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.