When a lender's wallet is compromised, Ripcord has a go at rescuing a queued withdrawal, on a best-effort basis. It
executes the withdrawal and gets the released funds into a safe wallet in one private, atomic bundle, aiming to have them
out before a sweeper watching the public mempool can grab them. Whether it lands comes down to a builder winning the block, so
there are no guarantees and no promises. This page reads the market's live state and helps you put that bundle together and
fire it; it holds no key and never moves funds on its own.
Precondition: this only works if there is already a withdrawal request queued from the compromised wallet. Ripcord
executes an existing queued withdrawal for that account. If the tokens were moved off to a hostile address before that
request went in, there is nothing this tool, or anyone, can do to get them back.
How this handles data and funds. Market figures come from a Wildcat Labs read-only feed, provided
as is and without warranty, so check them against something you trust before you act on timing. This page
never moves funds itself. When you arm, the transactions you have signed go from your browser to a fan-out
relayer run by a Wildcat Labs team member on their own private infrastructure, separate from Wildcat Labs'
systems (you can point it at any endpoint instead). Wildcat Labs the company does not run that relayer, submit
through it, or take on any liability for it.
Configuration
Market data comes through a Wildcat Labs read-only feed. Arming and submission (below) run in your
browser, against whatever relay endpoints you list; Wildcat Labs the company does not submit or broadcast,
and takes on no liability for it. The notice above says who runs the default relayer.
idle
Live state
enter a market and account, then refresh.
Arm (client-side)
Keys stay in your wallet, or arrive already signed. This page holds neither. The front-run-safe path is a
private bundle of pre-signed transactions; the wallet path below broadcasts in the open and is for testnet
or a rehearsal only.
A · Private bundle (pre-signed)
The forward leg has to be signed by the receiving
account, offline. You never enter a key here.
Defaults to a fan-out relayer that fires at Flashbots, Titan and beaverbuild at once, with a direct Titan line as a browser fallback. Bundles stay private and atomic, and only land when a builder wins the block. Edit the list (one per line) to use your own. Wildcat Labs the company is not in the submit path.
B · Wallet (public, rehearsal)
Connects an injected wallet to broadcast the
legs as ordinary transactions. Visible in the public mempool, so not front-run-safe. Use for
testnet or dry rehearsal.
Never paste a raw private key into this or any hosted page. Wildcat Labs will never ask you to.
