Shell Protocol

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 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

Websites and Applications

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