Skip to content

Not using flashblock payload #149

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 10 commits into
base: flashblocks
Choose a base branch
from

Conversation

cody-wang-cb
Copy link

@cody-wang-cb cody-wang-cb commented Mar 27, 2025

When websocket is on for rollup-boost, there seems to be an issue with using the flashblock payload rather than calling get_payload whenever rollup-boost is restarted, it causes sequencing to stop for some reason. Root cause is still unknown but commenting it out for now.

* deps: alloy 0.12.6

* bump jsonrpsee
Copy link

vercel bot commented Mar 27, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
rollup-boost ⬜️ Ignored (Inspect) Visit Preview Apr 16, 2025 9:00pm

@ferranbt
Copy link
Collaborator

Trying to solve this as part of #157

@cody-wang-cb cody-wang-cb force-pushed the cody/not-using-flashblock-payload branch from 1c63316 to b8c3e49 Compare April 3, 2025 19:14
@cody-wang-cb cody-wang-cb force-pushed the cody/not-using-flashblock-payload branch from b8c3e49 to e92ac27 Compare April 3, 2025 19:36
jowparks and others added 7 commits April 8, 2025 13:18
- Added methods to OpExecutionPayloadEnvelope for retrieving transactions and gas used.
- Improved error handling in RollupBoostServer when syncing with builder and L2 clients, including metrics for invalid payloads and request limits.
- Updated RpcClientError to be public for broader access.
…ogging in RollupBoostServer for payload_id and payload_trace_context (#3)
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.

4 participants