Voltz
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.
PoC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$40,000Minimum reward to discourage security researchers from withholding a bug report:
$10,000Rewards 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 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.
Note, the bounty amount for a critical submission is capped to be 10% of funds at risk.
Issues previously highlighted in the following audit reports are considered as out of scope:
- https://docs.google.com/spreadsheets/d/1RDdZD5W26UhjY-GTCDcUpIJHaSJDko6EaUkpky62mYg/edit#gid=0
- https://drive.google.com/file/d/1dcb5onZCRIFyCdt-1eun09qsjU-0LMK9/view?usp=sharing
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.
Program Overview
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/.
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
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.