Shell Protocol

Submit a Bug
11 March 2021
Live since
No
KYC required
$100,000
Maximum bounty

Program Overview

The objective of the Shell Protocol is to create an internet monetary system using stablecoins as building blocks. The first release is a liquidity pool optimized for stablecoin-to-stablecoin trades. It has weights, deep liquidity, protections against a broken peg and dynamic fees.

The bug bounty program is focused around its smart contracts and the prevention of loss of user funds.

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All web and app bug reports must come with a PoC. Bug reports that do not include a PoC are rejected with instructions to provide PoC.

Payouts are handled by the Shell Protocol team directly and are denominated in USD. Payouts are done in USDC.

There is an additional TOKEN bonus once token is live for smart contract vulnerabilities over $50,000.

Smart Contract

Critical
Level
up to 10% of funds at risk or USD $100,000, whichever is lower
Payout
High
Level
up to USD $20,000
Payout
Medium
Level
up to USD $5,000
Payout
Low
Level
up to USD $1,000
Payout

Websites and Applications

Critical
Level
USD $20,000
Payout
PoC Required
High
Level
USD $7,500
Payout
PoC Required
Medium
Level
USD $3,250
Payout
PoC Required
Low
Level
USD $500
Payout
PoC Required

Assets in scope

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

  • Critical Smart Contract Impact
    Critical
    Impact
  • High Smart Contract Impact
    High
    Impact
  • Medium Smart Contract Impact
    Medium
    Impact
  • Low Smart Contract Impact
    Low
    Impact

Websites and Applications

  • Critical Websites and Applications Impact
    Critical
    Impact
  • High Websites and Applications Impact
    High
    Impact
  • Medium Websites and Applications Impact
    Medium
    Impact
  • Low Websites and Applications Impact
    Low
    Impact

Out of Scope & Rules

The following vulnerabilities are excluded from the rewards for this bug bounty program:

All Programs

  • Attacks that the reporter has already exploited himself, leading to damage
  • Attacks that rely on social engineering
  • Attacks requiring access to leaked keys/credentials

Smart Contracts/Blockchain

  • Smart Contracts/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

Websites and Apps

  • 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
  • URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)

The following activities are prohibited by 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