feat: pm-resolution-delay multi-venue (Polymarket + Kalshi) - #1689
Merged
Conversation
- Add venue label to resolutionDelay/resolutionsTotal/disputesTotal metrics - Update chain.go call sites to prefix 'polymarket' as venue label - New kalshi_resolution.go: polls public Kalshi API every 5min, emits resolution delay from close_time to observed finalization - Wire runKalshiResolutionLoop goroutine in main.go - Replace polymarket-resolution-delay.yml with pm-resolution-delay.yml (multi-venue, venue= filters on all queries) - Update pm-venue-context.ts benchSlug to pm-resolution-delay - Add polymarket-us + manifold to PM_VENUE_META
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
venuelabel topmres_resolution_delay_seconds,pmres_resolutions_total,pmres_disputes_totalkalshi_resolution.go: polls public Kalshi REST API (/trade-api/v2/markets?status=settled) every 5 min; delay =settlement_ts - close_time(exact, no poll-interval error)benchmarks/polymarket-resolution-delay.yml→benchmarks/pm-resolution-delay.ymlwith{venue="polymarket"}filters on all existing queries + new Kalshi provider rowspm-venue-context.ts: bench slugpolymarket-resolution-delay→pm-resolution-delay; addspolymarket-us+manifoldtoPM_VENUE_METAVPS deploy
Already deployed:
ocb-pm-resolution-delayrebuilt and restarted onocb-par-main. Kalshi data is flowing ([kalshi-res] resolved ...logs confirmed).Test plan
/bench/pm-resolution-delayloads with multi-venue providers once merged + Vercel deploy/bench/polymarket-resolution-delayredirects or 404s gracefully