Voltz-logo

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.

Arbitrum
ETH
Defi
AMM
Derivatives
Solidity
Maximum Bounty
$40,000
Live Since
07 April 2022
Last Updated
04 November 2024
  • PoC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - Factory
Added on
7 April 2022
Target
Type
Smart Contract - Master Margin Engine Implementation
Added on
7 April 2022
Target
Type
Smart Contract - Master VAMM Implementation
Added on
7 April 2022
Target
Type
Smart Contract - Periphery
Added on
7 April 2022
Target
Type
Smart Contract - Aave Lend Rate Oracle
Added on
7 April 2022
Target
Type
Smart Contract - Aave Borrow Rate Oracle
Added on
7 April 2022
Target
Type
Smart Contract - Compound Lend Rate Oracle
Added on
7 April 2022
Target
Type
Smart Contract - Compound Borrow Rate Oracle
Added on
7 April 2022
Target
Type
Smart Contract - Lido Staked ETH Rate Oracle
Added on
7 April 2022
Target
Type
Smart Contract - Rocketpool Stacked ETH Rate Oracle
Added on
7 April 2022
Target
Type
Smart Contract - Aave v3 Lend Rate Oracle
Added on
7 April 2022
Target
Type
Smart Contract - GLP Rate Oracle (Arbitrum)
Added on
7 April 2022

Impacts in Scope

Severity
Critical
Title

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Severity
Critical
Title

Permanent freezing of funds (that cannot be resolved via an upgrade)

Out of scope

Program's Out of Scope information
  • Best practice critiques
Default Out of Scope and rules

Smart Contract specific

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks

All categories

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers