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 Bond Protocol 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 only applies to Critical impacts.

Bond Protocol is a permissionless marketplace for Olympus-style bonds.  Our mission is to bring capital raises on-chain and support protocols to acquire strategic assets including their own liquidity.

Direct theft of user funds

Permanent freezing of funds

Protocol insolvency

Bond Protocol Smart Contracts

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 bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required..

Known Issues highlighted in their previous audit reports are considered out of scope:

- [https://github.com/Bond-Protocol/bond-contracts/tree/master/audits](https://github.com/Bond-Protocol/bond-contracts/tree/master/audits)

Bond Protocol requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is name and address.  If a hunter prefers to stay anonymous, one would need to sign an NDA provided by Bond Protocol’s legal counsel. 

Payouts are handled by the __Bond Protocol__ team directly and are denominated in USD. However, payouts are done in __USDC__.

Bond Protocol

Codebase