feat(tempo): add remote fee payer transport - #5046
brendanjryan wants to merge 1 commit into
Conversation
|
@brendanjryan is attempting to deploy a commit to the Wevm Team on Vercel. A member of the Team first needs to authorize it. |
🦋 Changeset detectedLatest commit: 036452b The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 036452b76e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| walletNamespaceCompat, | ||
| withFeePayer, | ||
| withRelay, | ||
| withRemoteFeePayer, |
There was a problem hiding this comment.
Update the Tempo entrypoint export snapshot
Adding this named export changes Object.keys(tempo), but the inline snapshot in src/tempo/index.test.ts still ends with withRelay and therefore fails on every test run. Add withRemoteFeePayer to that snapshot so the entrypoint test reflects the new public API.
Useful? React with 👍 / 👎.
commit: |
Motivation
Remote fee-payer services may fill sponsored transactions without providing relay signing or broadcast methods. The existing remote wrapper requires relay capabilities despite its fee-payer naming.
Summary
withRemoteFeePayerfor fill-only remote sponsorship.Key design considerations
eth_fillTransactionrequests withfeePayer: trueto the remote service.withRelaybehavior and the deprecatedwithFeePayeralias unchanged.