Volt Protocol is a decentralized savings and credit system. Users can mint or redeem the natively yield bearing stablecoin VOLT with no slippage or swap fees, just like depositing into a vault or lending market. VOLT is live on Ethereum mainnet and Arbitrum. Unlike other stablecoins, VOLT holders will have governance rights. The market governance system that will power VOLT as the best on chain savings venue is under active development, read the whitepaper to learn more.
For more information about Volt Protocol, please visit https://www.voltprotocol.io/.
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.
All 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.
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 for Critical smart contract bug reports.
Previous issues highlighted in the following audit reports are considered to be out of scope:
Payouts are handled by Volt Protocol directly and are denominated in USD. However, payouts are done in USDC or VOLT, at the discretion of the team.
- Up to USD $100,000
- USD $10,000
- USD $2,000
Assets in scope
- Smart Contract - ERC20AllocatorType
- Smart Contract - DAI PSMType
- Smart Contract - USDC PSMType
- Smart Contract - Oracle Pass ThroughType
- Smart Contract - Volt System OracleType
- Smart Contract - CoreType
- Smart Contract - VoltType
- Smart Contract - DAI PCV DepositType
- Smart Contract - USDC PCV DepositType
- Smart Contract - Timelock ControllerType
- Smart Contract - PCV GuardianType
- Smart Contract - PCV Guard AdminType
All smart contracts of Volt Protocol can be found at https://github.com/volt-protocol/volt-protocol-core. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
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.
- Any governance voting result manipulationCriticalImpact
- Direct theft of any user or protocol funds, whether at-rest or in-motion, other than unclaimed yield without privileged roleCriticalImpact
- Permanent freezing of funds without privileged roleCriticalImpact
- Protocol InsolvencyCriticalImpact
- Logic errors in the oracle contracts that would cause loss of PCVCriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Miner-extractable value from PCV (MEV)HighImpact
- Temporary freezing of funds for at least 2 days without permissioned roleHighImpact
- Unauthorized privilege escalation by user without a role in the systemHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Unbounded gas consumptionMediumImpact
- Theft of gasMediumImpact
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, pcv controller, pcv guard, minter, burner, pcv guard admin, etc)
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