Wildcat Protocol
Bounty Range
$2,000 - $10,000
external program
Wildcat Protocol
The Wildcat Protocol is a hands-off credit facilitation protocol that enables the deployment of markets by pre-authorised (KYC'd through protocol) borrowers. Market parameters are arbitrarily parameterisable subject to these parameters falling within the bounds of controllers registered with the protocol registry. Borrowers must - at present - select their own lender lists explicitly. Participants in markets can optionally choose to sign a master loan agreement that dictates their behaviour. Wildcat markets make use of novel implementations of withdrawals, collateralisation and penalties for failure to maintain adequate reserves. Rebasing 'market tokens' are issued in exchange for deposits, inflating according to the active interest rate to ensure 1:1 parity for claiming underlying assets.
For more information about Wildcat Protocol, please visit https://www.wildcat.finance/
Wildcat Protocol provides rewards in USDC on Ethereum, denominated in USD.
Smart Contract
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $10,000.
Minimum reward to discourage security researchers from withholding a bug report: $7,500
Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table.
Payouts are handled by the Wildcat Protocol team directly and are denominated in USD. However, payments are done in USDC.
Wildcat Protocol has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
A PoC is required for the following severity levels:
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.
The provision of KYC is required to receive a reward for this bug bounty program where the following information will be required to be provided:
KYC information is only required on confirmation of the validity of a bug report.
The submission of KYC information is a requirement for payout processing.
If needed by the security researcher, Wildcat Protocol is able to provide the necessary information for the proper issuance of an invoice. This includes:
Wildcat Protocol adheres to the Primacy of Impact for the following severity levels:
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.
Category 2: Notice Required
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, including: