All code of Wildcat Protocol can be found at [https://github.com/wildcat-finance/wildcat-protocol.](https://github.com/wildcat-finance/wildcat-protocol) Documentation for the assets provided in the table can be found at [https://wildcat-protocol.gitbook.io/wildcat/.](https://wildcat-protocol.gitbook.io/wildcat/)  

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.

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Contract fails to deliver promised returns, but doesn't lose value

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

__Restrictions on Security Researcher Eligibility__

Security researchers who fall under any of the following are ineligible for a reward
- OFAC Sanctioned Countries

__Previous Audits__

Wildcat Protocol has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
- [https://hackmd.io/@geistermeister/r15gj_y1p ](https://hackmd.io/@geistermeister/r15gj_y1p)
- [https://code4rena.com/contests/2023-10-the-wildcat-protocol](https://code4rena.com/contests/2023-10-the-wildcat-protocol)

__Feasibility Limitations__

At Immunefi, we sometimes receive 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. If it’s obviously feasible, then it seems there are no questions about severity or payout amount. But if the bug report is less feasible, or not really feasible at all, suddenly questions arise.

Therefore, Immunefi has developed a set of [feasibility limitation standards ](https://immunefisupport.zendesk.com/hc/en-us/articles/16913132495377-Feasibility-Limitation-Standards)which by default states what a Projects should or should not cite when downgrading a bug report’s impact, severity, and/or payout amount. These standards are continuously being developed and updated  with help of the community and encompasses fair guidelines where the project clearly commits, and the security researcher can be assured that the project cannot arbitrarily downgrade the program based on theoretical counter measures, such as a [chain rollback. ](https://immunefisupport.zendesk.com/hc/en-us/articles/16913153448721-Chain-Rollbacks)

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:
- Smart Contract, Critical
- Smart Contract, High
- Smart Contract, Medium
- Smart Contract, Low

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules) Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Reward Payment Terms__

Payouts are handled by the Wildcat Protocol team directly and are denominated in USD. However, payments are done in USDC. 

Wildcat Protocol

Resources & Documentation