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.
PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Theft of unclaimed yield
Permanent freezing of unclaimed yield
Temporary freezing of funds
Smart contract unable to operate due to lack of token funds
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Contract fails to deliver promised returns, but doesn't lose value
Out of scope
-
All data stored in the Sapience database is intentionally public. Reports regarding exposure of database contents will not be considered valid findings.
-
DoS attacks due to a lack of rate limiting, improper handling of large HTTP request data, or exhaustion of server resources via high query volume are not eligible for rewards and are considered out of scope.
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers