Skip to content
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.

Sign up for GitHub

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

Sidecar disambiguation #37

Merged
merged 1 commit into from
Nov 20, 2024
Merged

Sidecar disambiguation #37

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,8 +50,8 @@ cargo run --jwt-token your_jwt_token --l2-url http://localhost:8545 --builder-ur
- `rollup-boost` validates the block with `proposer-op-geth` using `engine_newPayload`.
- This validation ensures the block will be valid for `proposer-op-geth`, preventing network stalls due to invalid blocks.
- If the external block is valid, it is returned to the `proposer-op-node`.
5. As per its normal workflow, the `proposer-op-node` sends another `newPayload` request to the sidecar and another FCU(without) to update the state of its op-geth node.
- In this case, the sidecar just relays the data and does not introspect anything.
5. As per its normal workflow, the `proposer-op-node` sends another `newPayload` request to the `rollup-boost` and another FCU(without) to update the state of its op-geth node.
- In this case, the `rollup-boost` just relays the data and does not introspect anything.
- Note that since we already tested `newPayload` on the proposer-op-geth in the previous step, this process should be cached.

![Workflow Diagram](/assets/workflow.svg)
Expand Down
Loading