feat(data): upgrade Binance USD-M reference to V3 - #774
Conversation
|
Warning Review limit reached
Next review available in: 39 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2acc62503a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Change contract
Capture USD-M tick size, step size, and minimum notional in reference V3 while preserving immutable V2 triplets as strictly validated read-only evidence.
Issue relationship
Refs #773
Out of scope
Existing-host cutover, PIT materialization, authenticated fee snapshots, execution latency telemetry, and Live trading.
Dependencies and merge order
First rollout unit for #773. The separately scoped existing-host cutover depends on this schema PR and must merge before any V3 production switch.
Focused validation
Rollout and rollback
No production rollout from this PR alone. Keep the current V2 collector and uploader unchanged until the follow-up existing-host cutover is reviewed, merged, released, shadow-gated, and explicitly controlled.
Scope exception
None.