Voltz is a noncustodial automated market maker for Interest Rate Swaps (IRS). Voltz uses a Concentrated Liquidity Virtual AMM (vAMM) for price discovery only, with the management of the underlying assets performed by the Margin Engine.
The combined impact of these modules enables counterparties to create and trade fixed and variable rates through a mechanism that is up to 3,000x more capital efficient than alternative interest rate swap models, whilst also providing Liquidity Providers and Traders with significant control and flexibility over their positions.
For more information about Voltz, please visit https://www.voltz.xyz/.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.1. 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 Critical/High severity smart contract 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.
Issues previously highlighted in the following audit reports are considered as out of scope:
Some additional bug reporting guidelines:
- Report a single vulnerability per submission, unless it is necessary to chain vulnerabilities to provide context regarding any of the issues.
- A reporter cannot be one of Voltz’s current or former team members, vendors, contractors or an employee of any of those contractors or vendors.
Voltz Protocol V1 has been audited and certified by Quantstamp, for additional information, go to https://docs.voltz.xyz/security/audits.
All the issues discussed in the Quantstamp report certificate are considered out of scope of the Bug Bounty Program.
Payouts are handled by the Voltz team directly and are denominated in USD. However, payouts are done in USDC or USDT, at the discretion of the team.
- USD $100,000
- USD $15,000
- USD $5,000
- USD $1,000
Assets in scope
- Smart Contract - Factory (Deployed Address)Type
- Smart Contract - Factory (Github)Type
- Smart Contract - MarginEngine (Deployed Address)Type
- Smart Contract - MarginEngine (Github)Type
- Smart Contract - VAMM (Deployed Address)Type
- Smart Contract - VAMM (Github)Type
- Smart Contract - AaveRateOracle (Deployed Address)Type
- TargetSmart Contract - AaveRateOracle (Github)Type
- Smart Contract - AaveFCM (Deployed Address)Type
- Smart Contract - AaveFCM (Github)Type
- Smart Contract - Periphery (Deployed Address)Type
- Smart Contract - Periphery (Github)Type
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.
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Protocol InsolvencyHighImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Smart contract unable to operate due to lack of fundsMediumImpact
- Block stuffing for profitMediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumption (gas drainage)MediumImpact
- 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)
Smart Contracts and Blockchain
- Incorrect data supplied by third party oracles
- Basic economic governance attacks (e.g. 51% attack)
- DDOS attacks
- 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