description
Private credit, on your terms.

The Wildcat Protocol

{% hint style="info" %} This Gitbook recently underwent substantial changes to incorporate Wildcat V2 details.

Something you don't understand? Something missing?

Fire a message to @functi0nZer0 on Twitter/X and watch him do Things That Don't Scale! {% endhint %}

Hi there.

Welcome to the Wildcat protocol documentation.

We recognise that a protocol Gitbook is - as a rule - read by three distinct categories of people:

• Potential users and researchers working out if something is actually useful,
• Security auditors working out if something is actually broken, and
• Lawyers and regulators working out if something is actually legal.

With that in mind, we'll keep this high-level page brief.

---

Users/Researchers

You might as well start at the beginning.

{% content-ref url="overview/introduction.md" %} introduction.md {% endcontent-ref %}

---

Auditors/Developers

Contract deployments, gas profiles etc can be found under the following section:

{% content-ref url="broken-reference" %} Broken link {% endcontent-ref %}

More specifically, if you're taking part in an audit or validating a potential bug, please refer to:

{% content-ref url="technical-overview/security-developer-dives/" %} security-developer-dives {% endcontent-ref %}

If you're interested in reading about our on-chain protection or previous security reviews:

{% content-ref url="broken-reference" %} Broken link {% endcontent-ref %}

---

Lawyers/Regulators:

{% content-ref url="broken-reference" %} Broken link {% endcontent-ref %}

Beyond that, the documentation is yours to enjoy (or not) at your leisure. \

Hic sunt dragones.