Wildcat Labs ripcord · Wildcat V2 withdrawal monitor & arming
Read-only data, as is. Market figures are read through a Wildcat Labs read-only feed, without warranty; verify independently before any time-critical action. This tool also builds and submits transactions, but that submission goes from your browser to third-party infrastructure Wildcat Labs does not operate, submit through, or accept liability for.

Configuration

Market data is read through a Wildcat Labs read-only feed. Arming and submission (below) run in your browser against third-party infrastructure you choose; Wildcat Labs does not submit or broadcast, and is not liable for it.
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 publicly and is for testnet or rehearsal only.

A · Private bundle (pre-signed)

The forward leg must be signed by the receiving account, offline. You never enter a key here.

Submission never touches Wildcat Labs infrastructure. Most bundle relays require a signed identity header and block browser CORS; if this fails, submit from local operator tooling.

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.