Spool
Submit a BugProgram Overview
Spool is decentralized middleware that allows anyone to create an automated, diversified, and risk-reward-optimized yield-farming strategy.
In more comprehensible terms, Spool is a "custom vault creator". Spool allows a user to pick their favorites from a list of supported protocols and create a diversified portfolio from them based on their individual risk appetite. This vault/portfolio is accessible through a single deposit address.
After depositing, Spool will automatically recognize changing yields (and potential risks) via oracles and off-chain risk models and rebalance between the chosen protocols as needed.
For more information about Spool, please visit https://www.spool.fi/.
This bug bounty program is focused on their smart contracts and on preventing
- Loss of user funds
- Loss of treasury funds
- Permanent freezing of funds
- Theft of principal funds
- Theft of unclaimed yield funds
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
Critical and High bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. In addition, all bug reports must come with a suggestion for a fix in order to be considered for a reward.
Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 50 000 and a maximum reward of USD 1 500 000 for Critical smart contract bug reports.
Rewards for High severity smart contract vulnerabilities will be further capped at up to 100% of the funds affected. However, there is a minimum reward of USD 20 000 and a maximum reward of USD 50 000 for High severity smart contract bug reports.
Issues previously highlighted in the following audit reports are considered as out of scope:
- Quantstamp Spool Core Audit: https://www.spool.fi/documents/QuantstampAudit.pdf
- Peckshield Spool Core Audit: https://github.com/peckshield/publications/blob/master/audit_reports/PeckShield-Audit-Report-Spool-v1.0.pdf
- Peckshield Spool Voting and Staking Audit: https://drive.google.com/file/d/1eNmeiGxFDgyV5XtQhl3sny4ichnRdBPa/view?usp=sharing
- Zokyo Spool Core Audit: https://drive.google.com/file/d/1NNm2RT9DTfZs6G4lG2UU2LmKzUi_tPlq/view?usp=sharing
- Zokyo Spool Vesting Audit:
https://drive.google.com/file/d/1X1DR9un-hglsNV2eCON2m0V2mPlQMEWX/view?usp=sharing
In addition, any vulnerabilities that involve whitelisted roles abusing their power to gain profit or hurt the system are considered out of scope of this program.
Spool requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is a national ID or passport photo, along with a bank statement or utility bill issued within the past 3 months.
Payouts are handled by the Spool team directly and are denominated in USD. However, payouts are done in DAI.
If an invoice from a non-DAO establishment is required, the invoice amount (payout) will come with a cut of currently 5% due to regulation and transfer pricing rules.
Smart Contract
- Critical
- Level
- Up to USD $1,500,000
- Payout
- High
- Level
- Up to USD $50,000
- Payout
- Medium
- Level
- USD $5,000
- Payout
- Low
- Level
- USD $1,000
- Payout
Assets in scope
- Smart Contract - SPOOL TokenType
- Smart Contract - VaultType
- Smart Contract - Spool DAI Lower RiskType
- Smart Contract - Spool DAI Higher RiskType
- Smart Contract - Spool USDC Lower RiskType
- Smart Contract - Spool USDC Higher RiskType
- Smart Contract - Spool USDT Lower RiskType
- Smart Contract - Spool USDT Higher RiskType
- Smart Contract - Aave DAIType
- Smart Contract - Aave USDCType
- Smart Contract - Aave USDTType
- Smart Contract - Compound DAIType
- Smart Contract - Compound DAI HelperType
- Smart Contract - Compound USDCType
- Smart Contract - Compound USDC HelperType
- Smart Contract - Compound USDTType
- Smart Contract - Compound USDT HelperType
- Smart Contract - Convex DAIType
- Smart Contract - Convex DAI HelperType
- Smart Contract - Convex USDCType
- Smart Contract - Convex USDC HelperType
- Smart Contract - Convex USDTType
- Smart Contract - Convex USDT HelperType
- Smart Contract - Curve DAIType
- Smart Contract - Curve USDCType
- Smart Contract - Curve USDTType
- Smart Contract - Harvest DAIType
- Smart Contract - Harvest USDCType
- Smart Contract - Harvest USDTType
- Smart Contract - Idle DAIType
- Smart Contract - Idle USDCType
- Smart Contract - Idle USDTType
- Smart Contract - Yearn DAIType
- Smart Contract - Yearn USDCType
- Smart Contract - Yearn USDTType
- Smart Contract - ControllerType
- Smart Contract - Risk Provider RegistryType
- Smart Contract - Master SpoolType
- Smart Contract - Fast WithdrawType
- Smart Contract - Fee HandlerType
- Smart Contract - Reward DistributorType
- Smart Contract - Strategy RegistryType
- Smart Contract - SPOOL StakingType
- Smart Contract - voSPOOL RewardsType
- Smart Contract - voSPOOL TokenType
For proxy contracts, only the current implementation and any further updates to the implementation contracts are considered in scope.
All smart contracts of Spool can be found at https://github.com/SpoolFi/. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
If an impact can be caused to any other asset managed by Spool that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.
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 Contract
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Protocol InsolvencyCriticalImpact
- Theft of unclaimed yieldHighImpact
- Miner-extractable value (MEV)HighImpact
- Permanent freezing of unclaimed yield (unless emergency withdraw of a strategy was performed, in which case we do not claim the protocol rewards)HighImpact
- Temporary freezing of funds for at least 90 daysHighImpact
- Smart contract unable to operate due to lack of token funds (except the RewardDistributor contract where the rewards have to be transferred manually)MediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumptionMediumImpact
- Smart contract fails to deliver promised returns, but doesn’t lose valueLowImpact
Out of Scope & Rules
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
- Centralization risks
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