onbjerg

This can be solved in the linked crate by them providing a `Provider` extension trait, like the one we provide in `alloy-ens`: https://github.com/alloy-rs/alloy/blob/165f5a60abf7c6653eb7fa5a0416fc7935ef10fa/crates/ens/src/lib.rs#L145-L197

bump @knelsondev :saluting_face:

Hi @knelsondev, since this PR is inactive, I'm going to close it. I appreciate the time you put into this, and I do appreciate that this going stale is on...

Hi @zugdev @zarkk01, I'm closing this PR as there has been no activity for a while. Please feel free to open up the PR again against `master` if any of...

Idea for an interactive debugger: some `Debugger` struct that handles state/displays UI. Messages are passed between the `Debugger` and the debug inspector. Contracts are identified on the fly when the...

Please do not merge this upon approval, I'd like to merge the devnet 4 PRs in one go when necessary.

What is the motivation/use case for this issue?

It makes sense to have other types of nonce management strategies. You can already do this using a custom filler, but this simplifies implementing a new nonce strategy somewhat, so...

Please do not merge this upon approval, I'd like to merge the devnet 4 PRs in one go when necessary.

After some thinking we likely do not gain much by retaining the type here instead of using blobs, since validation is mostly a CL responsibility now, and system contracts adhering...