PoolTogether
The PoolTogether Protocol promotes financial security by making it fun to save. PoolTogether unlocks organic usage for wallets, yield sources & blockchains.
PoC required
KYC required
Rewards by Threat Level
Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.
Reward Calculation for Critical Level Reports
For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 22 727. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 11 363.50 is to be rewarded in order to incentivize security researchers against withholding a bug report.
Reward Calculation for High Level Reports
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD 2272.50 to USD 4 545 depending on the funds at risk, capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional [24h] that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.
Repeatable Attack Limitations
In cases of repeatable attacks for smart contract bugs, only the first attack will be counted, regardless of whether the smart contract is upgradable, pausable, or killable.
Previous Audits
G9 Software Inc. has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
- https://audits.sherlock.xyz/contests/225
- https://0xmacro.com/library/audits/pooltogether-1
- https://code4rena.com/reports/2024-03-pooltogether
- https://code4rena.com/reports/2023-07-pooltogether
- https://code4rena.com/reports/2023-08-pooltogether
- https://code4rena.com/reports/2022-12-pooltogether
Known Issue Assurance
G9 Software Inc commits to providing Known Issue Assurance to bug submissions through their program. This means that G9 Software Inc will either disclose known issues publicly, or at the very least, privately via a self-reported bug submission.
In a potential scenario of a mediation, this allows for a more objective and streamlined process, in order to prove that an issue is known. Otherwise, assuming the bug report is valid, it would result in the report being considered as in-scope, and due a reward.
Feasibility Limitations
At Immunefi, we sometimes receive reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what a Projects should or should not cite when downgrading a bug report’s impact, severity, and/or payout amount.
Proof of Concept (PoC) Requirements
A PoC is required for the following severity levels:
- Smart Contract - Critical
- Smart Contract - High
- Smart Contract - Medium
All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.
Reward Payment Terms
Payouts are handled by the G9 Software Inc. team directly and are denominated in USD. However, payments are done in USDC.
Program Overview
The PoolTogether Protocol promotes financial security by making it fun to save!
For more information about PoolTogether, please visit https://pooltogether.com/.
Generation (G9) Software Inc. is one of the companies that developed the smart contracts that power the PoolTogether protocol. G9 Software Inc. provides rewards for the code in USDC. For more details about the payment process, please view the Rewards by Threat Level section further below.
KYC Requirement
The provision of KYC is required to receive a reward for this bug bounty program where the following information will be required to be provided:
- Full name
- Address
KYC information is only required on confirmation of the validity of a bug report.
Responsible Publication
G9 Software Inc. adheres to category 3:Approval Required. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.
Primacy of Impact vs Primacy of Rules
G9 Software Inc. adheres to the Primacy of Impact for the following impacts:
- Smart Contract - Critical - Direct theft of any user funds ( prizes or yield not included)
- Smart Contract - Critical - Permanent freezing of user funds (prizes or yield not included).
- Smart Contract - Critical - Protocol insolvency
- Smart Contract - High - Freezing or theft of prizes or unclaimed yield
If an impact is covered within the Primacy of Impact, it means that even if the impacted asset is not in-scope but is owned by the project, then it would be considered as in-scope of the bug bounty program. When submitting a report, just select the Primacy of Impact asset placeholder. If the team behind this project has multiple projects, those other projects are not covered under the Primacy of Impact of this program. Instead, check if those other projects have a bug bounty program on Immunefi.
Testnet and mock files are not covered under the Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms of the bug bounty program.
Immunefi Standard Badge
G9 Software Inc. has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to our best practices.
KYC required
The submission of KYC information is a requirement for payout processing.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- 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
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.