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.

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

Transition to OpChainSpec for Optimism node #11238

Closed
Tracked by #8904
mattsse opened this issue Sep 26, 2024 · 0 comments · Fixed by #11304
Closed
Tracked by #8904

Transition to OpChainSpec for Optimism node #11238

mattsse opened this issue Sep 26, 2024 · 0 comments · Fixed by #11304
Labels
A-sdk Related to reth's use as a library

Comments

@mattsse
Copy link
Collaborator

mattsse commented Sep 26, 2024

we're currently still using the unified chainspec type:

/// Optimism chain specification parser.
#[derive(Debug, Clone, Default)]
pub struct OpChainSpecParser;
impl ChainSpecParser for OpChainSpecParser {
type ChainSpec = ChainSpec;

this should be OpChainSpec instead, this also means we need to get rid of all remaining

ChainSpecParser<ChainSpec = ChainSpec>

and

ChainSpecProvider<ChainSpec = ChainSpec>

in favor of trait restrictions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-sdk Related to reth's use as a library
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant