Sommelier
Sommelier is built on the Cosmos SDK to maximize interoperability with other blockchains, and the platform is a reimagined gateway into interchain DeFi. With a bridge in place connecting the Cosmos-based platform to Ethereum, Sommelier will be able to execute strategies across multiple blockchains, opening a wide horizon of possibilities.
PoC required
KYC required
Rewards by Threat Level
Please review how rewards are distributed based on the Immunefi Vulnerability Severity Classification System V2.3. This is a simplified 5-level scale system with separate scales for Blockchain/DLTs, Smart Contracts and Websites/Apps.
Payouts and Payout Requirements
Payouts are handled by the Sommelier team directly and are denominated in USD. However, payouts are done in USDC. Sommelier commits to honoring payouts according to the terms set out in this program at the time of report submission, and to treat this program as the agreement and source of truth concerning bug reports and responsible disclosures.
For the purposes of determining report validity, this is a Primacy of Impact program.
Learn more about report validity best practices here: Best Practice - Primacy of Impact vs Primacy of Rules.
Sommelier does have a Know Your Customer (KYC) requirement for bug bounty payouts.
Sommelier will send a link to complete KYC through Rise pay. KYC will be anonymous to Sommelier.
KYC information is only required on confirmation of the validity of a bug report.
Audit Discoveries and Known Issues
Bug reports covering previously-discovered bugs are not eligible for any reward through the bug bounty program. If a bug report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the bug report via Immunefi.
Previous audits and known issues can be found at:
- Mitigations against malicious strategists are still a work in progress and not eligible for a bug bounty at this time
- Volumetric denial of service attacks against the gravity bridge via on chain txs are not fully mitigated against and not eligible for a bug bounty
- Audits for smart contracts are in of the github repos: https://github.com/PeggyJV/cellar-contracts/tree/main/audits
Program Overview
Sommelier is built on the Cosmos SDK to maximize interoperability with other blockchains, and the platform is a reimagined gateway into interchain DeFi. With a bridge in place connecting the Cosmos-based platform to Ethereum, Sommelier will be able to execute strategies across multiple blockchains, opening a wide horizon of possibilities.
For more information about Sommelier, please visit https://www.sommelier.finance/.
For Whitehats: It is highly recommended that you review the details of this program in full. Although many Bug Bounty programs have standard terms and conditions, each also has their own unique details that are critical to your success.
Prior to submitting a report please review the Immunefi Bug Report Template and Best Practices.
KYC required
The submission of KYC information is a requirement for payout processing.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.