pStake on Cosmos
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.
BSC
Blockchain
Defi
L1
Liquid Restaking
Liquid Staking
Staking
Go
NextJS
Maximum Bounty
$100,000Live Since
18 April 2023Last Updated
24 July 2024PoC required
Select the category you'd like to explore
Assets in Scope
Target
Type
Added on
Primacy Of Impact
Websites and Applications
5 October 2023
Target
Type
Added on
Primacy Of Impact
Smart Contract
5 October 2023
Target
Type
Added on
Primacy Of Impact
Blockchain/DLT
5 October 2023
Impacts in Scope
Critical
Network not being able to confirm new transactions (Total network shutdown)
Critical
Direct loss of funds
Critical
Permanent freezing of funds (fix requires hardfork)
Critical
RPC API crash
Critical
Any governance voting result manipulation
Critical
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Critical
Permanent freezing of funds
Critical
Protocol insolvency
Critical
Taking down the application/website
Critical
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.
Critical
Direct theft of user funds
Critical
Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions
Out of scope
Program's Out of Scope information
The following impacts and attack vectors are excluded from rewards by default for all Immunefi bug bounty programs:
- 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), except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
- Broken link hijacking is out of scope
Smart Contracts and Blockchain/DLT
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
- Centralization risks
- Validator slashing impact on TVL; if a validator in the pSTAKE validator list gets slashed, and this results in economic damage, we will not pay out any rewards (unless there is a bug in our platform that causes the validator to get slashed)
- Temporary freezes of funds due to chain upgrades (Persistence chain OR Cosmos chain) or Persistence chain downtime (unless the downtime is caused by a bug in the pSTAKE app itself)
- App downtime/temporary freezes of funds due to Cosmos hub downtime
Websites and Apps
- Theoretical impacts 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
- Attacks involving DDoS
- Attacks requiring privileged access from within the organization
- SPF records for email domains
- Feature requests
- Best practices
| Category | Additional specific vulnerabilities and/or attacks to exclude |
|---|---|
| Blockchain/DLT | Validator slashing impact on TVL; if a validator in the pSTAKE validator list gets slashed, and this results in economic damage, we will not pay out any rewards (unless there is a bug in our platform that causes the validator to get slashed) |
| Blockchain/DLT | Temporary freezes of funds due to chain upgrades (Persistence chain OR Cosmos chain) or Persistence chain downtime (unless the downtime is caused by a bug in the pSTAKE app itself) |
| Blockchain/DLT | App downtime/temporary freezes of funds due to Cosmos hub downtime |
| Blockchain/DLT | Anything that affects the lscosmos directory: https://github.com/persistenceOne/pstake-native/tree/main/x/lscosmos |
| Blockchain/DLT | Anything that affects Persistence chain’s app.go: https://github.com/persistenceOne/persistenceCore/blob/main/app/app.go |
| Blockchain/DLT | Anything that affects the ibchooker module: https://github.com/persistenceOne/persistence-sdk/tree/master/x/ibchooker |
Prohibited Activities
The following activities are prohibited by this bug bounty program. Violation of these rules can result in a temporary suspension or permanent ban from the Immunefi platform at the sole discretion of the Immunefi team, which may also result in: 1) the forfeiture and loss of access to all bug submissions, and 2) zero payout.
Please note that Immunefi has no tolerance for spam/low-quality/incomplete bug reports, “beg bounty” behavior, and misrepresentation of assets and severity. Immunefi exists to protect the global crypto community, not facilitate grift.
Prohibited:
- Any testing with mainnet or public testnet deployed code; all testing should be done on private testnets
- 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
- Any other actions prohibited by the Immunefi Rules. These rules are subject to change at any time.