Skip to content

Conversation

@rekmarks
Copy link
Member

@rekmarks rekmarks commented Oct 29, 2025

Explanation

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
  • I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

@rekmarks rekmarks changed the title refactor!: Support JsonRpcEngineV2 refactor(eth-json-rpc-provider): Support JsonRpcEngineV2 Oct 30, 2025
@rekmarks rekmarks force-pushed the rekm/ejrpcp-v2 branch 2 times, most recently from 6cb53fa to 88118a9 Compare October 31, 2025 17:29
Base automatically changed from rekm/internal-provider to main October 31, 2025 19:09
…hten v2 types

- InternalProvider
  - replace rpcHandler with server
  - wrap legacy engine via asV2Middleware + JsonRpcServer
  - update tests
- asV2Middleware: fix middleware signature
- providerFromMiddleware
  - Use providerFromMiddlewareV2 and asV2Middleware to wrap legacy
    middleware
- json-rpc-engine:
  - add MiddlewareConstraint
  - update JsonRpcServer/asV2Middleware generics
@rekmarks rekmarks changed the title refactor(eth-json-rpc-provider): Support JsonRpcEngineV2 refactor!(eth-json-rpc-provider): Support JsonRpcEngineV2 Nov 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants