Divergence

Divergence is a decentralized platform for hedging, trading DeFi-native asset volatility, with its flagship product being an AMM-based marketplace trading synthetic binary options.

To fill this gap, Divergence is developing a range of decentralized volatility derivatives and volatility index products with the aim of becoming the go-to platform for:

• Risk-averse users seeking to hedge volatility risks
• Risk-tolerant users seeking to trade and gain leveraged exposure to volatility
• Risk-neutral users seeking to participate as liquidity providers and earning fees

For more information about Divergence, please visit https://divergence-protocol.com.

This bug bounty program is focused on their smart contracts and app and is focused on preventing the following impacts:

• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Website goes down or malfunctions
• Theft of treasury DAO funds
• Deletion of user data

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.

Payout** At the time of this program publication Divergence is not live with its mainnet yet. “Critical” bounty is currently offered at USD 50 000.

Once Divergence’s V1 product is live, this page will update periodically to reflect changes in TVL and adjust “Critical” bounty cap accordingly.The maximum payout for a “Critical” bounty is 10% of the total value locked of the contracts where the bug is discovered, capped at $1,000,000. The minimum payout for this level of bugs is USD 50 000.

A PoC and a suggestion for a fix is required for all Critical bug reports. Additionally, a PoC is required for all other Web/App bug reports.

Payouts are handled by the Divergence team directly and are denominated in USD. However, payouts are done in USDC.

Only the web/app assets explicitly listed here are in-scope. All else are out-of-scope.

All code of Divergence can be found at https://github.com/DivergenceProtocol. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Any smart contract file labeled as "dummy" or "test", or is within a folder that has that in its name, is considered as out-of-scope.

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

• Loss of user funds staked (principal) by freezing or theft
• Loss of governance funds
• Theft of unclaimed yield
• Freezing of unclaimed yield
• Temporary freezing of funds for 3 hours
• Unable to call smart contract
• Smart contract gas drainage
• Smart contract fails to deliver promised returns
• Vote manipulation
• Incorrect polling actions

Web/App

• Leak of user data
• Deletion of user data
• Redirected funds by address modification
• Site goes down
• Accessing sensitive pages without authorization
• Injection of text
• Users spoofing other users
• Shell access on server

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

Websites and Apps

• Remote Code Execution
• Trusting trust/dependency vulnerabilities
• Vertical Privilege Escalation
• XML External Entities Injection
• SQL Injection
• LFI/RFI
• Horizontal Privilege Escalation
• Stored XSS
• Reflective XSS with impact
• CSRF with impact
• Direct object reference
• Internal SSRF
• Session fixation
• Insecure Deserialization
• DOM XSS
• SSL misconfigurations
• SSL/TLS issues (weak crypto, improper setup)
• URL redirect
• Clickjacking (must be accompanied with PoC)
• Misleading Unicode text (e.g. using right to left override characters)

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

Websites and Apps

• Theoretical vulnerabilities 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
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices

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