Skip to content

Upgrade to reth 1.4.7 and main rollup-boost branch #112

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

Merged
merged 1 commit into from
Jun 4, 2025
Merged

Conversation

avalonche
Copy link
Contributor

@avalonche avalonche commented Jun 4, 2025

πŸ“ Summary

upgrade reth to 1.4.7.

πŸ’‘ Motivation and Context

bug fixes and compatibility with the latest rollup-boost


βœ… I have completed the following steps:

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

@avalonche avalonche merged commit 19bd39c into main Jun 4, 2025
2 checks passed
@@ -664,7 +664,7 @@ where
block_hash,
transactions: new_transactions_encoded,
withdrawals: ctx.withdrawals().cloned().unwrap_or_default().to_vec(),
withdrawals_root,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think there is correct default for this
Probably better to just expect, because it would mean that we don't support pre-isthmus chains

@@ -2,6 +2,7 @@ use super::DEFAULT_JWT_TOKEN;
use alloy_eips::{eip7685::Requests, BlockNumberOrTag};
use alloy_primitives::B256;
use alloy_rpc_types_engine::{ForkchoiceUpdated, PayloadStatus};
use http::Uri;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have they break compatibility with uri::Uri?
Can you do .to_string for uri::Uri?

@SozinM SozinM mentioned this pull request Jun 4, 2025
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