Sapience
Bounty Range
$5,000 - $10,000
external program
Sapience
Sapience is a fully onchain, open-source prediction market protocol powered by USDe. Its RFQ-based design enables deep liquidity, bespoke parlays, and composable vaults, transforming collective intelligence into actionable signals for the DeFi ecosystem. This program covers smart contract vulnerabilities only. For web/app and off-chain disclosures, see our bug bounty program in our docs: https://docs.sapience.xyz/user-guide/other-resources/bugbounty
Foil is a decentralized protocol for peer-to-peer trading of exposure to onchain resources like gas and blobspace. Using the Foil Protocol, users may supply ETH and offer to buy or sell exposure to a given period's average gas or blobs market at a price expressed via a Uniswap V3 position. When the period ends, position values are automatically fixed at the true average price.
For more information about Foil, please visit https://www.foil.xyz/
Foil provides rewards in USDC on Ethereum, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section.
Sapience is a prediction market built on top Foil protocol smart contracts. The website and the app can be found on https://www.sapience.xyz/
Smart Contract
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $10,000.
Minimum reward to discourage security researchers from withholding a bug report: $5,000
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 $10,000. 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 $5,100 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
For critical smart contract bugs on testnet assets, the reward is paid as a flat amount of $1,000. This is because there are no actual funds at risk on the testnet, hence limits objective calculation.
Repeatable Attack Limitations
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the affected component. The reward amount will depend on the severity of the impact and the funds at risk.
For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the cumulative impact of the repeatable attacks will be considered for a reward. This warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.
Reward Calculation for High Level Reports
High vulnerabilities concerning theft or permanent freezing of unclaimed yield are rewarded within a range of $2,600 to $5,000 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 24 hours that funds are temporarily frozen, up to the maximum high reward cap.
Reward Payment Terms
Payouts are handled by the Sapience team directly and are denominated in USD. Payments are made in USDC on Ethereum L1.
The net reward amount is calculated based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
Foil will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
Foil adheres to Category 3: Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports.
Foil adheres to the Primacy of Impact for the following impacts:
Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.
When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Foil's completed audit reports can be found at https://docs.foil.xyz/audit_reports. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
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.