Check slashing window feasibility API

Compare caller-supplied slashing stages with an available window. Each duration is an integer in seconds, or in epochs when its unit is epochs. Epoch length is seconds. Stages run in detection, evidence, submission, veto, execution, and finality order. Consecutive stages listed in parallel start together and the timeline uses the longest. A missing stage is incomplete and is not treated as zero. feasibility_status is feasible, margin_exceeded, infeasible, incomplete, or invalid. A fit is arithmetic only. No protocol parameters are fetched.

The Check slashing window feasibility operation is part of the Cross Network Slashing Exposure API on BRAINIAC.software. Compare caller-supplied slashing stages with an available window. Each duration is an integer in seconds, or in epochs when its unit is epochs. Epoch length is seconds. Stages run in detection, evidence, submission, veto, execution, and finality order. Consecutive stages listed in parallel start together and the timeline uses the longest. A missing stage is incomplete and is not treated as zero. feasibility_status is feasible, margin_exceeded, infeasible, incomplete, or invalid. A fit is arithmetic only. No protocol parameters are fetched. It is exposed as POST /api/v1/restaking-risk/slashing-window-feasibility and priced at $0.05 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied vault, collateral, and slashing records processed locally Caller-supplied slashing window durations processed locally Limitations: Amounts are integers in the caller-supplied unit. No balance is fetched. The same underlying collateral is counted once. Gross exposure counts each allocation. A reuse group is shared backing only when the request says those allocations list the same units. Simultaneous losses are capped at 100% of a shared slice. Sequential losses use the balance left by earlier events. Prices and conversion rates are used only when supplied. No price is invented. A modeled loss is not proof that a slash occurred. A slashing window fit is arithmetic on the supplied durations. It does not show that a network will finish the process in time. slashing-correlation caps each operator at 100 percent of its own stake. The correlation score is the share of stake listed on more than one network. exit-window uses the soonest supplied slash horizon. A negative buffer scores zero feasibility. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Calculate cross-network slashing exposure, Score cross-network slashing correlation, Score exit timing before a slash. Open the group documentation for the full request schema, field notes, and response examples before integrating.