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.

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 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.

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.

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

• 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

Websites and Applications

• Theoretical vulnerabilities without any proof or demonstration
• Content spoofing / Text injection issues
• Self-XSS
• Captcha bypass using OCR
• CSRF with no security impact (logout CSRF, change language, etc.)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
• Server-side information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring unlikely user actions
• Attacks that require the user to click on phishing or malicious links for subdomains can be reported but will be given a Low, Medium or High classification at most
• URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices
• Vulnerabilities primarily caused by browser/plugin defects
• Any vulnerability exploit requiring CSP bypass resulting from a browser bug
• Vulnerabilities that require compromise of the user’s machine / browser
• In the future community-developed applications
• Clickjacking Vulnerabilities

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