Skip to content

Conversation

@avalonche
Copy link
Collaborator

@avalonche avalonche commented Dec 31, 2025

📝 Summary

  • Add --flashblocks.build-at-interval-end flag to wait for interval before building first flashblock instead of building immediately
  • Add --flashblocks.send-offset-ms to adjust flashblock send timing (positive = send later, negative = send earlier)
  • Refactor payload loop to wait for signal before building flashblocks
  • Fix log message in tx_manager (funding -> registering)

💡 Motivation and Context

Make flashblocks timing closer to every 200 ms


Sampling local timing

Screenshot 2026-01-01 at 11 44 04 am

✅ I have completed the following steps:

  • Run make lint
  • Run make test
  • Added tests (if applicable)

- Add --flashblocks.build-at-interval-end flag to wait for interval before
  building first flashblock instead of building immediately
- Add --flashblocks.send-offset-ms to adjust flashblock send timing
  (positive = send later, negative = send earlier)
- Refactor payload loop to wait for signal before building flashblocks
- Fix log message in tx_manager (funding -> registering)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@avalonche avalonche force-pushed the flashblock-timing-config branch from d2ed7f7 to e5f651b Compare January 1, 2026 00:45
@SozinM
Copy link
Collaborator

SozinM commented Jan 5, 2026

Why is index 5 flashblock in the middle?

@akundaz
Copy link
Contributor

akundaz commented Jan 5, 2026

Why is index 5 flashblock in the middle?

This is because the leeway time is applied to the last flashblock. Here it's set to 100ms so fb 5 comes 100ms earlier

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.

3 participants