Sovryn
Sovryn is an on-chain decentralized trading and lending protocol deployed on RSK, a side chain of the Bitcoin blockchain-powered by merge-mining, and is governed by the community. The Sovryn protocol is controlled by its community and stakeholders. There is no single company, organization, or individual that represents or controls the Sovryn protocol.
PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Critical Blockchain/DLT impact leading to direct economic damage
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Ability to execute system commands resulting in a financial loss
Extract Sensitive data/files from the server such as /etc/passwd resulting in a financial loss
Signing transactions for other users
Redirection of user deposits and withdrawals
Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)
Wallet interaction modification resulting in financial loss
Direct theft of user funds
Tampering with transactions submitted to the user’s wallet
Out of scope
- Best practice critiques
- https://github.com/DistributedCollective/Sovryn-smart-contracts/tree/master/contracts/governance is an exception and considered out of scope for this program
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers