iQuant Liquidation DeskRestricted execution console

Operator authentication

This console exposes live execution state, wallet performance and risk controls. Authenticate with your assigned operator key.

iQuant Liquidation Desk Execution · surveillance · risk
Stream—
Processed—
Confirmed—
Detector—
Last match—
Uptime—
Dropped—
Memory—
Capital state INITIALISING Waiting for execution preflight
Realized P&L — Execution wallet
Hit rate — Confirmed / submitted
Failed-race spend — Fees and reverted tips
Market capture — Share of priced field P&L

Company projections capture scenarios · before infrastructure

Field captureDailyWeeklyMonthly (30d)Operating interpretation

Opportunity quality priced event window ±1 slot

Execution latency oracle event → confirmed landing

Largest realized opportunities net value to fee payer

ProtocolSignerPositionSlotNet USDJito tip / CUContestSignature

Live execution authority, venue readiness, candidate flow and rejection diagnostics. Runtime gate changes affect real capital on the next eligible candidate.

Risk parameters effective immediately · runtime only · restart restores policy

Capital controls are loading.

Candidate conversion funnel process lifetime · final guaranteed economics

VenueEnqueuedProfit-approvedPacket-readySimulatedSubmittedConfirmedSubmit → confirm

Auction bid calibration selected tape window · landed Jito winners

VenueSamplesTypical requested CUTip/CU p50Tip/CU p90Typical-CU tip p50Typical-CU tip p90Evidence gate

Persistent packet readiness selected window · top 50 by estimated reward

VenuePositionEstimated rewardWire bytesHeadroomStatic accountsResultSignature

Execution latency selected audit window · milliseconds · p50 / p90

VenueAttemptsBlockhashBuild + signSimulationSubmit ackConfirmationDecision → settled

Execution readiness fail closed

Solend shadow detector oracle-priced + simulated

MarginFi shadow detector program-exact health + flashloan bracket

Kamino shadow detector Scope/Pyth-priced + flash-refresh-liquidate

Market microstructure: liquidation flow, competitor concentration, auction spend, failure modes and protocol-level opportunity distribution.

Attempts over time per minute

Winner concentration is it 3 wallets or 300?

Per protocol attempts, landed vs reverted

Why attempts revert decoded from the raw error bytes — the tape keeps the hex

Cause Class Txs Share of reverts Fees burnt Raw Example

Wallets

# Wallet Attempts Landed Reverted Win rate Share of wins Fees SOL Tips SOL Mean CU price Own program Protocols Slot span Last slot
“Own program” is the share of a wallet’s attempts where the liquidation was CPI’d from its own program rather than called directly — a purpose-built bot, not somebody using a lending UI.

Instruction coverage every instruction this build matches on, fired or not

Protocol Instruction Selector Txs Landed Reverted Lines CPI'd Args Accounts Notes
A row with no transactions is the one to look at: a quiet market and a mistyped discriminator produce exactly the same empty row, and only one of them is fine.

Transaction ledger. Every observed liquidation attempt, immutable tape fields, execution cost, compute consumption and signer-level balance movement.

Tape feed

Time Slot Outcome Signer Protocol Instruction Via Fee ⌁ CU price CU used Tip ⌁ Amount Signer deltas Signature
Click a row for the whole record. The feed trails the chain by the block-time hold (store.block_time_wait_ms): a line is only shown once it is committed to the tape, so the page cannot claim a record the file does not have.

Operational assurance: valuation completeness, surveillance coverage, stream health, decoder integrity, retained evidence and active configuration.

What it was worth net, not gross

Protocol Landed No delta Priced Net p50 p90 Max leg

Coverage downtime or quiet?

Largest gaps Length Cause

Capture health is this a measurement?

Tapes on disk

File Size Modified

Measurement config credentials redacted


Tape line