All blockchain/DLT of Basilisk can be found at [https://github.com/galacticcouncil](https://github.com/galacticcouncil). However, only those in the “Assets in Scope” table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by Basilisk that isn’t on this table but for which the impact is in the “Impacts in Scope” section below, you are encouraged to submit it for the consideration by the project. This applies to only Critical impacts.

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

Governance compromise

Identity theft that compromises user’s assets (fungible, non-fungibles)

Unauthorized token minting

Unauthorized NFT minting (for reserved classes)

XYK pool account theft

XYK pool manipulation resulting in loss/theft of liquidity

Double spending

Direct loss of funds

Transaction/consensus manipulation

Direct theft of user’s assets (fungibles, non-fungibles)

Performing state modifying action without user’s consent such as making trades, transfers, withdrawals etc.

Subdomain takeover only on app.basilisk.cloud

Blocking or modifying governance processes

Generating not handled on chain error which leads to blocking users from accessing their assets

Theft of unclaimed yield

Stalling the chain

Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc

Putting on-chain data into an unexpected state without interrupting the system or users from performing their tasks

Open redirect

Taking down the application

Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data

DoS of greater than 10% but less than 30% of validator or miner nodes without shutting down the network

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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__.

Basilisk

Resources & Documentation