pStake on Cosmos

Liquid staking ATOM on pSTAKE generates high yields by auto-compounding ATOM staking rewards while enabling you to easily use your staked ATOM in Cosmos DeFi.

For more information about pSTAKE on Cosmos, please visit https://pstake.finance/

For Whitehats: It is highly recommended that you review the details of this program in full. Although many Bug Bounty programs have standard terms and conditions, each also has their own unique details that are critical to your success.

Prior to submitting a report please review the Immunefi Bug Report Template and Best Practices.

Please review how rewards are distributed based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale system with separate scales for Blockchain/DLTs, Smart Contracts and Websites/Apps.

Payouts and Payout Requirements:

Payouts are handled by the pSTAKE on Cosmos team directly and are denominated in USD. However, payouts are done in USDC or USDT. pSTAKE on Cosmos commits to honoring payouts according to the terms set out in this program at the time of report submission, and to treat this program as the agreement and source of truth concerning bug reports and responsible disclosures.

For the purposes of determining report validity, this is a Primacy of Impact program.

Learn more about report validity best practices here: Best Practice - Primacy of Impact vs Primacy of Rules.

Rewards for critical blockchain/DLT and smart contract vulnerabilities are further capped at 10% of the funds at risk. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused. However, there is a minimum reward of USD 10 000.

pSTAKE on Cosmos does not have a Know Your Customer (KYC) requirement for bug bounty payouts.

Audit Discoveries and Known Issues:

Bug reports covering previously-discovered bugs are not eligible for any reward through the bug bounty program. If a bug report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the bug report via Immunefi.

Previous audits and known issues can be found at: https://github.com/persistenceOne/pStake-auditReports/tree/main/stkATOM.

Impacts only apply to assets in active use by the project like contracts on mainnet or web/app assets used in production. Any impact that applies to assets not in active use, like test or mock files, are out-of-scope of the bug bounty program unless explicitly mentioned as in-scope.

Blockchain/DLT

• Blockchain/DLT - PoC, Blockchain/DLT bug reports are to include a runnable Proof of Concept (PoC) in order to prove impact.
• For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules

Smart Contracts/pSTAKE Module

• Smart Contracts/pSTAKE module - PoC, Smart Contract/pSTAKE module bug reports are to include a runnable Proof of Concept (PoC) in order to prove impact.
• For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules

Web/App

• Web/App - Bug reports are required to include a runnable Proof of Concept (PoC) in order to prove impact.
• All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All PoC content must adhere to the PoC guidelines and rules of Immunefi. In the event that a PoC requires an attack on a web/app asset provided, they must still adhere to the rules provided, otherwise eligibility for a reward may be revoked.
• For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules

Whitehats we highly encourage you to review any potential subdomains and what specific port(s) are in scope. Even though the domain may be the same, different ports may point to different assets.

Impacts to other assets

Hackers are encouraged to submit issues outside of the outlined Impacts and Assets in Scope.

If whitehats can demonstrate a critical impact on code in production for an asset not in scope, pSTAKE on Cosmos encourages you to submit your bug report using the “primacy of impact exception” asset. Impacts in Scope

(For Blockchain/DLTR and Smart Contracts Only) This program is considered to be governed by Primacy of Impact. For more information on what this means visit: Best Practice - Primacy of Impact vs Primacy of Rules.

Impacts are based on the Immunefi Vulnerability Severity Classification System V2.2.

At Immunefi, we classify bugs on a simplified 5-level scale:

• Critical
• High
• Medium
• Low
• None

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

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.