Sherlock V2
  • 👋Intro to Sherlock
  • 🙋FAQ
  • 📚Glossary
  • ‼️Disclaimers
  • Audits
    • 🧑‍💻Protocol Teams
      • How it Works for Protocols
      • Audit Timeline
      • Scheduling Process
      • Audit Preparation
      • Protocol Involvement During the Audit Process
      • Protocol Involvement Post-Audit
      • Rescheduling and Cancellations
      • Interim Updates and Upgrades
    • 🕵️Watsons
      • Lead Senior Watson Selection Process
      • Fix Review Process
      • Contest Points
      • How to Score Issue Points in a Contest
      • Meeting the Payout Criteria
      • First Blood Pot
      • Leaderboard Points Example
      • FAQ
    • 🧑‍⚖️Judging
      • Judging Conduct Guidelines
      • Criteria for Issue Validity
        • Criteria Changelog
      • Lead Judge
      • 🧑‍⚖️Community Judging
      • Dedicated Judge
      • Discussion
      • Sherlock's Exclusive Judging Apprentice Program
    • 🤝Referral Program
  • Bug Bounties
    • 🌱Pre-Launch Bounty
    • 🚀Post-Launch Bounty
      • 📜Platform Rules
      • ⚖️Dispute Resolution
  • Coverage
    • 🛡️Sherlock Shield
    • 💰Stakers
      • Overview
      • Lockup Period
      • Payout Flow
      • Staking APY
    • 🧑‍💻Protocol Teams
      • Getting Started
      • Coverage Premiums
      • Pricing
      • Composability and Coverage
      • Payout Flow
      • FAQ
    • 📝Claims
      • Claims Process
  • Tokens
    • SHER
    • Receipt NFTs
  • Governance
    • Roles
  • Developer
    • Overview
    • Stake Position Lifecycle
    • Claim Lifecycle
    • Protocol Lifecycle
    • SHER Distribution
    • Deployed Contracts
    • Contract Reference
    • Audits
Powered by GitBook
On this page
  • Sherlock Terminology
  • Bug Bounty
  • Claim
  • Coverage
  • Exploit
  • Premium
  • SHER
  • Staking
  • Unstaking
  • Watsons

Glossary

PreviousFAQNextDisclaimers

Last updated 1 year ago

Sherlock Terminology

Bug Bounty

  • A bug bounty is essentially a reward offered to an honest participant who finds a way to exploit a protocol. Black hat hackers are "bad guys" who exploit a protocol directly, leading to losses for all users. White hat hackers are "good guys" who report a potential exploit vector to the protocol team in return for a bug bounty reward (usually USDC).

Claim

  • A claim occurs when a protocol covered by Sherlock receives a bug bounty submission or believes it has been hacked and believes Sherlock has a responsibility to repay the bug bounty or hack. See the for details.

Coverage

  • If Sherlock takes on a protocol as a customer, the "coverage" is the amount of tokens (USDC) that Sherlock will reimburse when a bug bounty submission or exploit (that falls under the coverage agreement) occurs.

Exploit

  • For Sherlock's purposes, an exploit is the act of maliciously removing tokens (usually tokens deposited by others) from a protocol in an unintended way. Sherlock covers most (but not all) exploits that a protocol could experience. For a detailed breakdown of which exploits are generally covered, take a look at our current coverage agreements .

Premium

  • The amount of USDC a protocol pays Sherlock over a specified time interval. In return, Sherlock reimburses covered bug bounty submissions and exploits experienced by the protocol over that same time interval.

SHER

Staking

  • The act of depositing USDC into a Sherlock staking pool for a fixed period (6 months, 12 months, etc.). Once USDC has been deposited, USDC and SHER tokens accrue to the depositor in the form of APY. A portion of the staked tokens (up to 50% for an individual exploit) in the staking pool is at risk of being liquidated due to a bug bounty payout or exploit at one of the protocols covered by Sherlock.

Unstaking

  • The act of removing staked USDC from the Sherlock staking pool. This action can only be taken once the staking period (6 months, 12 months, etc.) for that USDC has ended.

Watsons

  • "You know my methods, Watson. There was not one of them which I did not apply to the inquiry." - The Memoirs of Sherlock Holmes (1893)

  • Watsons are the individuals without which Sherlock would be nothing. These are the security experts who do the deep fundamental research (audits) that allows Sherlock to confidently provide coverage for a given protocol's smart contracts.

Sherlock's governance token. See the for more info.

📚
claims section
here
SHER section