Solv Protocol

Solv Protocol is a decentralized platform for creating, managing, and trading Financial NFTs.

With the development of Decentralized Finance, explorations into bringing NFTs to more tangible scenarios of finance are birthing the concept of “Financial NFTs” - NFTs that can represent and certify any type of financial equity.

But as the ERC-721 Non-Fungible Token Standard describes, NFT is used to identify something or someone in a unique way, which is not natural for many financial scenarios. This is why Solv introduces its Fractionalized NFT Standard, vNFT - an ERC-721 extension that enhances NFTs with a quantitative property and some quantitative operations, thus making them much more fitting for financial scenarios.

Based on this sophisticated token standard, Solv Protocol provides Financial NFTs with a comprehensive solution for their creation, management, and transactions. To emphasize the financial side, they name the NFT that is minted on Solv Protocol a voucher. There are various financial scenarios that are developed by Solv and its partners for the economy of corresponding vouchers.

For more information about Solv Protocol, please visit https://solv.finance/home.

This bug bounty program is focused on their smart contracts and is focused on preventing:

• Loss of user funds staked (principal) by freezing or theft
• Theft of unclaimed yield
• Freezing of unclaimed yield
• Smart contract fails to deliver promised returns

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All Critical/High severity bug reports must come with a PoC and a suggestion for a fix in order to be considered for a reward.

Payouts are handled by the Solv Protocol team directly and are denominated in USD. Payouts are done in USDT.

All smart contracts of Solv can be found at https://github.com/solv-finance. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contracts/Blockchain

• Loss of user funds staked (principal) by freezing or theft
• Theft of unclaimed yield
• Freezing of unclaimed yield
• Smart contract fails to deliver promised returns

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

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

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