refactor: use provider methods with request headers - #187
Merged
Merged
Conversation
decofe
force-pushed
the
onbjerg/raw-provider-calls
branch
2 times, most recently
from
August 28, 2026 08:52
fa3e7a8 to
62a1619
Compare
onbjerg
force-pushed
the
onbjerg/raw-provider-calls
branch
from
September 10, 2026 13:31
62a1619 to
222dd54
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
onbjerg
force-pushed
the
onbjerg/raw-provider-calls
branch
2 times, most recently
from
September 10, 2026 13:34
e2a8619 to
f43bbac
Compare
onbjerg
force-pushed
the
onbjerg/raw-provider-calls
branch
from
September 10, 2026 13:37
f43bbac to
4fe14ba
Compare
onbjerg
marked this pull request as ready for review
September 10, 2026 13:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use Alloy’s typed provider methods for transaction lookup and receipt polling while preserving request-scoped headers with
ProviderCall::with_headers. Require Alloy provider 2.4.2 and update the lockfile to published crates.Raw transaction submission uses the same request path with or without headers. Receipt-details decoding keeps the raw response to preserve optional fee-field presence.
Validation: full workspace tests, compilation checks, Clippy, formatting, and Ethereum/Tempo transaction decoding pass in CI.