PoolTogether

PoolTogether is a protocol for no-loss prize games on the Ethereum blockchain. The protocol enables developers to build their own no-loss prize games and offers governance-managed no-loss prize games. Prize games are pools of funds whose accrued interest is distributed as prizes. The concept is well-established and otherwise known as "no loss lotteries" or "prize savings accounts".

The PoolTogether Protocol governance serves two primary functions: Governing the prize pool creation tools and governing a subset of prize pools.

The bug bounty program is focused around its smart contract and is mostly concerned with the loss of user funds.

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.

Payouts are handled by the PoolTogether team directly and are denominated in USD. However, payouts are done in DAI assuming a full 1:1 ratio.

Only the smart contracts listed in this specific section noted here.

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

Smart Contracts/Blockchain:

• Re-entrancy
• Logic errors
  • Including user authentication errors
• Solidity/EVM details not considered
  • Including integer over-/under-flow
  • 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)
• 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 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