3A Lending Protocol
  • 👋Welcome to 3A
    • Quick Start
  • PROTOCOL DOCUMENTATION
    • Lending
      • Vaults
        • Issuance Fee
      • Stability Pool
      • Liquidation
        • Stability Pool Liquidations
        • Dutch Auction
        • Community Liquidations
      • Redemptions
    • EURO3 Coin
      • EURO3 Price Stability
      • WatchDog Bot
    • A3A Token
      • A3A Staking and Cashbacks
      • A3A Rewards
    • 3A Ecosystem Incentives
    • Premium Services
      • Vault Optimization Bot
  • TECHNICAL DOCUMENTATION
    • User Interface
    • Smart Contracts
      • Linea Mainnet Contracts
      • Polygon Mainnet Contracts
      • RedBelly Testnet Contracts
      • API
      • Interacting with contracts
        • Creating a vault
        • Adding and removing collateral
        • Borrowing and Repaying
    • Audit Report
      • Hypernative
    • Bug Bounties
  • WHITELISTING CRITERIA
    • Overview
    • Mandatory Requirements
    • Risk Methodology
      • Fundamental Risk Score
      • Technical Risk Score
      • Market Risk Score
    • Risk Sensitive Parameters
    • Whitelisted Tokens
  • COMMUNITY REWARDS
    • Centurion
    • Referral System
  • GOVERNANCE
    • 3A DAO
    • Voting
    • Forum Discussions
  • COMMUNICATION
    • Contact Us
    • Team Contacts
  • USER GUIDE
    • Frequently Asked Questions
    • DeFi Glossary
  • BRAND ASSETS
    • Logo Package
    • Color Palette
Powered by GitBook
On this page
  • Scope
  • Rewards
  1. TECHNICAL DOCUMENTATION

Bug Bounties

Incentives for community members to review the protocol and submit issues

PreviousHypernativeNextOverview

Last updated 1 year ago

Scope

The bounty program covers exclusively the smart-contract portion of the protocol. The issues should be submitted as tickets on ​

Rewards

The rewards are different for each severity level of the bug:

  • minor: 5,000 A3A - 3 or 4 points

  • medium: 15,000 A3A - 5 or 6 points

  • major: 500,000 A3A - 7 or 8 points

  • critical: 5,000,000 A3A - 9 or 10 points

The severity is determined by two factors:

  1. Likelihood - the certainty with which an issue will arise

  2. Impact - should the issue arise, how devastating it would be

Likelihood

The more likely an issue is to occur, the more points it is given. From a maximum of 5 points for a dead certain occurrence to 1 for an issue that only arises in edge cases.

  1. Very unlikely, edge cases only. Probably never occurs.

  2. Low probability, edge cases that have a good chance of occurring.

  3. Potential for a security incident in the long run. We have time, but it needs fixing.

  4. High probability of a security incident. Needs to be fixed right away.

  5. Dead certain and it could happen tomorrow. The protocol needs to be paused.

Impact

In the same spirit, the higher the impact, the more points an issue gets. From 5 points for a catastrophic issue to 1 point for an annoying bug.

  1. Is annoying but has an easy workaround

  2. May cause loss of functionality but not of funds

  3. May cause loss of funds in some cases

  4. Allows an attacker to gain access to a large portion of the value locked

  5. Allows an attacker to gain access to all of the value locked unless the protocol is paused

Discord