24 May 2022
Live since
No
KYC required
$100,000
Maximum bounty

Program Overview

Gelt is the first savings product at the intersection of Fintech and DeFi enabling anyone to access covered DeFi yields while retaining custody of their funds.

  • Earn interest every second with all transactions secured on-chain
  • End-to-end protocol cover on deposits by Nexus Mutual
  • Native on/off ramp with free bank deposits and withdrawals powered by Plaid
  • No fees or lock-ins, deposits provably remain in your sole custody at all times.

For more information about Gelt, please visit https://gelt.finance

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 Medium, High and Critical Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.

Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 20 000.

All vulnerabilities marked in the Quantstamp security review are not eligible for a reward.

Payouts are handled by the Gelt team directly and are denominated in USD. However, payouts are done in USDC and DAI, with the choice of the ratio at the discretion of the team.

Smart Contract

Critical
Level
Up to USD $100,000
Payout
PoC Required
High
Level
USD $10,000
Payout
PoC Required
Medium
Level
USD $1,000
Payout
PoC Required

Assets in scope

All smart contracts of Gelt can be found at https://github.com/GeltFinance/gelt-contracts-v1. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by Gelt that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This only applies to Critical impacts.

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.

Smart Contract

  • Direct theft or unfair withdrawals from the vault, resulting in a loss of user funds
    Critical
    Impact
  • Circumvention of access control policies
    Critical
    Impact
  • Irreversible locking or freezing of funds (The Gelt USDC Vault allows administrators to temporarily freeze the vault for 2 weeks. Once this period expires it is possible to temporarily freeze the vault again. This is by design.)
    Critical
    Impact
  • Theft of protocol governance tokens awarded to the vault, both claimed and unclaimed
    High
    Impact
  • Inability to upgrade the vault
    High
    Impact
  • Inability for users to withdraw funds from the vault while the vault is not paused (Only applies to the voluntaryExit function.)
    High
    Impact
  • Griefing
    Medium
    Impact
  • Circumvention of the vault’s strategy tolerances (e.g. max slippage)
    Medium
    Impact

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, strategist)

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