FAQs
Worry not, help has arrived.
Last updated
Worry not, help has arrived.
Last updated
This is very likely because your TAP (Transaction Authorization Policy) is set up to block interactions with DeFi protocols: the default mode is locked down quite heavily.
Add a new Contract Call TAP rule (you can find them in your Settings) with the Wildcat market you are attempting to interact with as the Destination which Allows the interaction, and move it up to the top of your rule-set, above any generic blocking rules. For an example of how to set up a rule: (account required).
This is because when you placed your withdrawal request, you either started a new withdrawal cycle or joined an existing one. That withdrawal cycle needs to conclude before any assets set aside within it can be claimed - the length of which is dependent on the market itself.
Check the Lender Withdrawal Requests tables within the market that you placed the withdrawal request from: you'll be able to see when the cycle ends and you can claim funds that have been made available for you from your request.
For those parties using a Safe, we ask that you go to the Safe website and connect to the Wildcat frontend via a . The URL for this is https://app.wildcat.finance (or https://testnet.wildcat.finance if you're looking around on Sepolia).
We're in the process of talking to Safe about getting approved as an app on their site.
If you're encountering any difficulties, get in touch! Three questions in the FAQ doesn't seem like much, but the point of an FAQ is to answer the questions we hear a lot!