Basilisk
Basilisk is a liquidity protocol built for the Kusama ecosystem. Its mission is to enable permissionless liquidity that caters to the evolving needs of crypto assets - both fungible, and non-fungible (NFTs).
PoC required
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All High and Critical blockchain/DLT bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
Critical blockchain/DLT vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 20 000.
High blockchain/DLT vulnerabilities are scaled based on an internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in-place. However, there is a minimum reward of USD 5 000, rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program.
Critical web/app vulnerabilities are scaled based on an internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in-place. However, there is a minimum reward of USD 5 000, rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program.
Only code involving runtime pallets of Basilisk and pallets developed by Galactic Council are considered as in-scope of the bug bounty program. Pallets that are not in runtime, are not live or are under development are considered as out-of-scope of the bug bounty program.
Payouts are handled by the Basilisk team directly and are denominated in USD. However, payouts are done in BSX.
Program Overview
Basilisk is a liquidity protocol built for the Kusama ecosystem. Its mission is to enable permissionless liquidity that caters to the evolving needs of crypto assets - both fungible, and non-fungible (NFTs).
The modular design of Basilisk enables fungible assets to bootstrap liquidity by choosing the Automated Market Maker (AMM) model which they find the most convenient. The first version comes with an implementation of Snek Swap (XYK) pools which allow users to buy and sell tokens, or to become a liquidity provider and earn rewards generated from trades.
Further iterations for fungibles will deliver a liquidity mining pallet allowing the protocol to incentivize liquidity provisioning to selected pools. Moreover, the Basilisk implementation of Liquidity Bootstrapping Pools (LBP) enables young crypto projects to bootstrap initial liquidity and achieve a fair token distribution across their communities.
For the non-fungibles (NFTs), Basilisk features a Marketplace which supports functions such as putting NFTs up for sale, setting royalty fees, and the ability to make an offer for unlisted NFTs. Future iterations will bring an auction functionality allowing users to bid on NFTs (with 3 auction types - English, Top Up and Candle).
For more information about Basilisk, please visit https://bsx.fi/.
KYC not required
No KYC information is required 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.