Event Contract Position Limit Check

Checks a book of event-contract positions, stated as quantities and prices only, against caller-declared position accountability levels and position limits: maximum loss per position recomputed from the side (yes loses its full cost; no loses payout minus price), aggregated per contract, per event or per series as the caller declares, with market-maker treatment applied as data. Every limit figure is caller-supplied - this tool hard-codes no venue figure - and the node reports arithmetic against declared levels; it never states that a participant violated a rule.

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data - use synthetic or anonymised inputs only.
Scope note: how position limits aggregate across similar contracts is venue-specific and CFTC staff guidance on that question (a staff advisory and an advance notice of proposed rulemaking, 2026) sets no numeric levels, so every level and limit here is caller-supplied. Accountability levels and position limits are regulatory figures a designated contract market adopts per contract (17 CFR 38.300, 38.301); the pinned Kalshi rulebook profile states the market-maker treatment shape (accountability levels 10x for market makers with quoting obligations, and no position limits on program contracts), never a figure. Fee and pricing arithmetic for event contracts lives in separate tools (art-211 and art-212); this node does no fee arithmetic. This is arithmetic evidence, not a legal opinion, and no venue or participant is named as compliant or in violation.
Book input (quantities and prices only)
What this node checks
CheckArithmeticOutcome
Max lossyes: quantity × price; no: quantity × (payout − price); rounded UP to the next minor unit when computed from micro-denominated prices (the one rounding rule; conservative toward finding). A caller-declared max_loss_minor is used as givenreport
Accountabilitygroup max loss vs the declared accountability level, x10 under the pinned profile for a market maker with quoting obligations (Rule 4.5); only where a level is declaredbreach
Position limitgroup max loss (basis max_loss) or quantity (basis contracts) vs the declared limit; not applied to a limit-exempt market maker; only where a limit is declaredbreach
Nettinggross counts yes and no on the same contract separately; per_contract_net nets quantities per contract before the max-loss computation. The declared rule and the profile default are both stated in the outputreport
Aggregationper contract, per event or per series, declared by the caller; a group's level or limit is applied only when every position in the group declares the same figure - mixed or missing figures surface as a manual-review flag, never a silent defaultreport
VerdictLIMIT_BREACH over ACCOUNTABILITY_REVIEW over WITHIN, from the breaches foundverdict
Identifier-like labelsany contract, event or series label shaped like an account id, member id, address, email or hash is refused with a structured non-verdict; the value is never echoedrefusal
Refused inputsunknown profile, malformed as_of, out-of-window as_of, out-of-enum aggregation, netting, participant class, side or limit basis: structured refusal, no default appliedrefusal

Fee and pricing arithmetic for event contracts is separate tooling (art-211 and art-212). This node never hard-codes a venue limit figure, never names a participant as having violated a rule, and gives no legal opinion; CFTC questions on how limits aggregate across similar contracts (staff advisory and advance notice, 2026) set no numeric levels.

Manifest