Skip to content

fix(spammer): timestamp catch-up blocks when fetched - #146

Open
westkite1201 wants to merge 1 commit into
circlefin:mainfrom
westkite1201:fix/spammer-catch-up-timestamps-128
Open

westkite1201 wants to merge 1 commit into
circlefin:mainfrom
westkite1201:fix/spammer-catch-up-timestamps-128

Conversation

@westkite1201

Copy link
Copy Markdown

Summary

  • Timestamp each catch-up block after it is fetched instead of reusing the first post-gap notification timestamp.
  • Update the block event timestamp docs to cover both live notifications and catch-up scans.
  • Add a WebSocket-backed regression test for catch_up_scan timestamping.

Fixes #128

Testing

  • RED: cargo test -p spammer catch_up_scan_timestamps_each_fetched_block_individually -- --nocapture failed before the fix on stale timestamp reuse
  • cargo fmt --all -- --check
  • cargo test -p spammer
  • cargo clippy -p spammer --all-targets --all-features -- -D warnings
  • git diff --check

@ZhiyuCircle ZhiyuCircle added bug Something isn't working tooling Component: tooling labels Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working tooling Component: tooling

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore(refactor): catch-up scan uses stale received_at timestamp

2 participants