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

meta(anvil): make anvil a reth extension / sparse client #9970

Open
sambacha opened this issue Feb 27, 2025 · 2 comments
Open

meta(anvil): make anvil a reth extension / sparse client #9970

sambacha opened this issue Feb 27, 2025 · 2 comments
Labels
A-reth-anvil Area: reth-anvil T-meta Type: meta

Comments

@sambacha
Copy link
Contributor

sambacha commented Feb 27, 2025

Component

Anvil

Describe the feature you would like

anvil and reth should be best friends.

It makes sense to do this. It would make anvil more accurately produce EL client behavior because it is an EL client.

'sparse' client

A 'sparse' client would be like a reduced functionality client with certain checks disabled (like connecting to a beacon client, etc.). I would think this may be useful for reth testing in CI as well, maybe.

The reth_anvil client should support extensions. This does make sense w.r.t. custom RPC methods, as it would make extending custom methods much easier. Hot loading such modules would be very intriguing.

Additional context

Inshallah, we get this sooner than we got v1.0.0 foundry

@sambacha sambacha added T-feature Type: feature T-needs-triage Type: this issue needs to be labelled labels Feb 27, 2025
@github-project-automation github-project-automation bot moved this to Todo in Foundry Feb 27, 2025
@sambacha sambacha changed the title feat(anvil): make anvil a reth extension feat(anvil): make anvil a reth extension or sparse client Feb 27, 2025
@sambacha sambacha changed the title feat(anvil): make anvil a reth extension or sparse client feat(anvil): make anvil a reth extension / sparse client Feb 27, 2025
@zerosnacks zerosnacks added the A-reth-anvil Area: reth-anvil label Feb 27, 2025
@zerosnacks
Copy link
Member

zerosnacks commented Feb 27, 2025

You are reading our mind 😉! reth-anvil is in the beginning stages but what you stated is effectively what we would like to do. It will build on top of Reth's SDK.

We are planning to maintain anvil until reth-anvil has most of the important features anvil has and users can start switching over. It will be so good - I can't wait for us to work on it and ship it.

Check out the https://github.com/foundry-rs/foundry/issues?q=state%3Aopen%20label%3A%22A-reth-anvil%22 label, if you have any concrete ideas for things you want to be in reth-anvil feel free to open specific tickets.

I'll turn this ticket into a meta-ticket for reth-anvil as it captures the idea well

@zerosnacks zerosnacks added the T-meta Type: meta label Feb 27, 2025
@zerosnacks zerosnacks changed the title feat(anvil): make anvil a reth extension / sparse client meta(anvil): make anvil a reth extension / sparse client Feb 27, 2025
@zerosnacks zerosnacks removed T-feature Type: feature T-needs-triage Type: this issue needs to be labelled labels Feb 27, 2025
@sambacha
Copy link
Contributor Author

You are reading our mind 😉! reth-anvil is in the beginning stages but what you stated is effectively what we would like to do. It will build on top of Reth's SDK.

We are planning to maintain anvil until reth-anvil has most of the important anvil has and users can start switching over. It will be so good - I can't wait for us to work on it and ship it.

Check out the foundry-rs/foundry/issues (state:open label:"A-reth-anvil") label, if you have any concrete ideas for things you want to be in reth-anvil feel free to open specific tickets.

I'll turn this ticket into a meta-ticket for reth-anvil as it captures the idea well

Thank you for responding, I had not seen the label for this, very exciting indeed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-reth-anvil Area: reth-anvil T-meta Type: meta
Projects
Status: Todo
Development

No branches or pull requests

2 participants