Wildcat Protocol Documentation
  • The Wildcat Protocol
  • Overview
    • The Elevator Pitch
    • Whitepaper
    • FAQs
  • Using Wildcat
    • Terminology
    • Onboarding
    • Day-To-Day Usage
      • Borrowers
      • Lenders
      • Market Access Via Policies/Hooks
      • The Sentinel
    • Protocol Usage Fees
    • Delinquency
  • Technical Overview
    • Security/Developer Dives
      • The Scale Factor
      • Core Behaviour
      • V1 -> V2 Changelog
      • Known Issues
      • Hooks
        • How Hooks Work
        • Access Control Hooks
        • Fixed Term Loan Hooks
    • Function/Event Signatures
      • /access
        • AccessControlHooks.sol
        • IRoleProvider.sol
        • MarketConstraintHooks.sol
      • /interfaces
        • IHooks.sol
        • IMarketEventsAndErrors.sol
        • IWildcatArchController.sol
        • IWildcatSanctionsEscrow.sol
        • IWildcatSanctionsSentinel.sol
      • /market
        • WildcatMarketConfig.sol
        • WildcatMarketToken.sol
        • WildcatMarketWithdrawals.sol
        • WildcatMarketBase.sol
      • /spherex
        • ISphereXEngine.sol
        • ISphereXProtectedRegisteredBase.sol
        • SphereXConfig.sol
      • HooksFactory.sol
      • IHooksFactory.sol
      • WildcatArchController.sol
      • WildcatSanctionsEscrow.sol
      • WildcatSanctionsSentinel.sol
    • Protocol Structs
    • Contract Deployments
  • Security Measures
    • Code Security Reviews
    • SphereX Protection
    • Bug Bounty Program
  • Legal
    • Wildcat Terms Of Use
    • Risk Disclosure Statement
    • Template MLA
    • Privacy Policy
Powered by GitBook
On this page
  • Borrowers
  • Lenders
  1. Using Wildcat

Onboarding

How to make use of the Wildcat protocol.

PreviousTerminologyNextDay-To-Day Usage

Last updated 2 months ago

Wildcat is a permissioned protocol where both borrowers and lenders must meet specific criteria to participate. The onboarding process and permissions differ for each role, as outlined below.

Borrowers

Borrowers interested in using Wildcat are encouraged to contact the Wildcat Foundation through the or by emailing .

Eligibility:

Currently, only registered legal entities are accepted as borrowers. In the future, individual retail borrowers may be allowed.

Verification Process:

The Wildcat Foundation performs a KYB/C verification similar to centralised exchanges. This includes verifying certificates of incumbency, proofs of address, and the identities of directors and individuals with significant control. After verification, borrowers provide an Ethereum address that is registered on-chain via the , enabling them to deploy hooks instances and create markets.

Permissions:

Borrowers have the authority to determine which categories of lenders can interact with their markets.

Lenders

Wildcat does not directly onboard lenders; instead, each borrower sets their own criteria for lender participation.

Onboarding Process:

The process to obtain lending credentials varies depending on the borrower’s . Examples include:

  • Confirming the lender is not subject to sanctions.

  • Requiring explicit whitelist approval from the borrower.

  • Verifying jurisdiction and accreditation through a third-party KYC/B check.

  • Accepting credentials like or (with future hook integrations planned).

Access and Credentials:

  • Lenders obtain deposit credentials through market hook instances, which act as gatekeepers.

  • Credentials are typically issued without needing direct contact with the borrower, though that option remains available.

  • Credentials may expire and need periodic renewal.

  • Addresses that have previously deposited assets or received market tokens with a valid deposit credential can still make withdrawal requests even if the credential has expired.

  • For security, lenders should use a hardware wallet or multisig when interacting with Wildcat.

Compliance and Restrictions

Wildcat does not dictate borrower requirements for lender onboarding. Each borrower is responsible for compliance based on their location, risk tolerance, and objectives.

Borrower profile pages on the protocol UI provide contact information (email, Telegram, Twitter), and each market displays its credential requirements.

Addresses flagged as sanctioned by the are automatically blocked from interacting with the protocol.

Chainalysis oracle contract
landing page
contact@thewildcat.foundation
Coinbase Verification
Binance Account Bound Tokens
archcontroller
policies