Sei Bug Bounty Program

Sei is the fastest Layer 1 blockchain, designed to scale with the industry. Pushing the boundaries of blockchain technology through open source development, Sei stands to unlock a brand new design space for consumer facing applications.

For more information about Sei Foundation, please visit https://www.sei.io/

Rewards

Sei provides rewards in SEI on Sei, denominated in USD.

Rewards by Threat Level

Blockchain/DLT

• Critical: Max: $500,000 | Min: $50,000
• High: Flat: $25,000
• Medium: Flat: $5,000
• Low: Flat: $1,000

Reward Calculation for Critical Level Reports

For Critical Blockchain/DLT vulnerabilities, rewards are determined based on the ratio between the total funds at risk—including all affected projects built on the Sei blockchain—and the Sei market capitalization, calculated as the average market cap reported by CoinMarketCap and CoinGecko at the time the report is submitted.

A minimum reward of USD $50,000 is guaranteed for all valid Critical reports in order to incentivize timely and responsible disclosure.

This ratio is referred to as the risk ratio, defined as:

Risk Ratio = Funds at Risk / Sei Market Capitalization

Rewards scale linearly from a 0:1 to a 1:1 risk ratio, where a 1:1 ratio corresponds to a maximum reward of USD $500,000.

If the funds at risk exceed the market capitalization, the reward remains capped at USD $500,000.

Reward Payment Terms

Rewards are denominated in USD and paid by the Sei Foundation team.

Payouts are made in SEI or USDT/C, at the Foundation's discretion.

Public Disclosure of Known Issues

Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program.

• Project operation risk in tokenfactory module

Previous Audits

Sei Foundation has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.

• https://github.com/oak-security/audit-reports/blob/master/Sei/2023-05-15%20Audit%20Report%20-%20Sei%20Cosmos%20v1.0.pdf
• https://github.com/oak-security/audit-reports/blob/master/Sei/2023-05-15%20Audit%20Report%20-%20Sei%20Tendermint%20v1.0.pdf
• https://github.com/oak-security/audit-reports/blob/master/Sei/2023-05-19%20Audit%20Report%20-%20Sei%20Chain%20and%20CosmWasm%20v1.0.pdf

Proof of Concept (PoC) Requirements

A PoC is required for the following severity levels:

• Blockchain/DLT: Critical
• Blockchain/DLT: High
• Blockchain/DLT: Medium
• Blockchain/DLT: Low

All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

For Medium, High and Critical reports, whitehats should provide a PoC using a local 4-node cluster. You can follow these steps to provide this PoC:

• Spin up the local testnet with make docker-cluster-start
• Connect to node0 with docker exec -it sei-node-0 /bin/bash
• Carry out attack

Note that any PoC submitted against testnet must not:

• Set any GIGA_* flag to true
• Explicitly enable any configuration under sections prefixed with giga

PoCs that rely on enabling Giga-related functionality will be considered out of scope and will not be eligible for a bounty.

Malicious Proposer Rule

If an attack requires the attacker to be a block proposer (or equivalent privileged validator role), its severity is reduced by one level (e.g. Critical → High, Low → Informational/Out of Scope).

Note: direct loss of funds remains Critical regardless of attacker role.

KYC Requirements

Sei Foundation has a Know Your Customer (KYC) requirement for bug bounty payouts.

KYC requirements include:

• Full Name
• Date of birth
• Proof of address (either a redacted bank statement with address or a recent utility bill)
• Copy of passport or other government issued ID

Primacy of Impact vs Primacy of Rules

If an impact is covered within the Primacy of Impact, it means that even if the impacted asset is not in-scope but is owned by the project, then it would be considered as in-scope of the bug bounty program. When submitting a report, just select the Primacy of Impact asset placeholder. If the team behind this project has multiple projects, those other projects are not covered under the Primacy of Impact of this program. Instead, check if those other projects have a bug bounty program on Immunefi.

Testnet and mock files are not covered under the Primacy of Impact.

All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms of the bug bounty program.

Sei Foundation adheres to the Primacy of Impact for the following severity levels:

• Blockchain/DLT: Critical
• Blockchain/DLT: High

If a category's severity level is covered within the Primacy of Impact, it means that even if the impacted asset is not in-scope but is owned by the project, then it would be considered as in-scope of the bug bounty program as long as it involves an impact under that respective severity level. When submitting a report, just select the Primacy of Impact asset placeholder. If the team behind this project has multiple projects, those other projects are not covered under the Primacy of Impact of this program. Instead, check if those other projects have a bug bounty program on Immunefi.

Testnet and mock files are not covered under the Primacy of Impact.

All other severity levels not listed here are considered under the Primacy of Rules, which means that they are bound by the terms of the bug bounty program.

Known Issue Assurance

Sei Foundation commits to providing Known Issue Assurance to bug submissions through their program. This means that Sei Foundation will either disclose known issues publicly or at the very least privately via a self-reported bug submission in order to allow for a more objective and streamlined mediation process to prove that an issue is known. Otherwise, assuming the bug report itself is valid, it would result in the bug report being considered in-scope and due 100% of the reward with respect to the bug bounty program terms.

Immunefi Standard Badge

Sei Foundation has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to best practices.

Responsible Publication

Category 3: Approval Required

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

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:

• Chain Rollbacks
• Pre-Impact Bug Monitoring
• Attack Investment Amount
• Attacks With A Financial Risk To The Attacker
• When Is An Impactful Attack Downgraded To Griefing?