Skip to content

fix(skill): handle Binance candle boundaries and USD volume - #63

Merged
dxiongya merged 1 commit into
mainfrom
fix/binance-candle-pagination
Oct 29, 2026
Merged

dxiongya merged 1 commit into
mainfrom
fix/binance-candle-pagination

Conversation

@AmazingAng

Copy link
Copy Markdown
Contributor

Agents following the Binance guide could repeat a candle during backfill because the guide promises exclusive time bounds while live responses include the boundary. Teach millisecond pagination with after=min(timestampMs)-1, strict timestamp filtering, a composite candle key, cursor-progress termination, and replacement of mutable open candles on refresh.

Confirm the official USD volume mapping, describe shared request queues/cache/coalescing and 429 handling, and distinguish the still-missing serving price-info body from the already-correct xhub source contract. Keep price-info disabled until its live schema exposes the required array; a repository merge is not publication.

Rechecked BSC USDT, 1h, limit 3: equal after repeats one candle, minus 1ms does not; before also includes the boundary. Official schema defines prices and candle volume in USD:
https://web3.binance.com/en/dev-docs/catalog/web3-wallet/api/rest-api/1.0.0/schema.json

Validation:

  • bun install --frozen-lockfile passed
  • bun run typecheck passed
  • bun run build passed
  • bun run test: 1457 passed, 0 failed
  • npm pack --dry-run --ignore-scripts passed
  • New guide regression test failed before the guide correction, then passed.

No version, release, or live provider configuration changes.

@dxiongya
dxiongya merged commit 889c15e into main Oct 29, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants