-
-
Notifications
You must be signed in to change notification settings - Fork 201
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
feat: Add Multichain API to @metamask/multichain
#4813
base: main
Are you sure you want to change the base?
Conversation
## Explanation This PR fixes a lot of the linting and typescript errors. still some left but this covers a lot of it. <!-- Thanks for your contribution! Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes: * What is the current state of things and why does it need to change? * What is the solution your changes offer and how does it work? * Are there any changes whose purpose might not obvious to those unfamiliar with the domain? * If your primary goal was to update one package but you found you had to update another one along the way, why did you do so? * If you had to upgrade a dependency, why did you do so? --> ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/package-a` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ### `@metamask/package-b` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ## 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 highlighted breaking changes using the "BREAKING" category above as appropriate - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes --------- Co-authored-by: Jiexi Luan <[email protected]>
## Explanation <!-- Thanks for your contribution! Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes: * What is the current state of things and why does it need to change? * What is the solution your changes offer and how does it work? * Are there any changes whose purpose might not obvious to those unfamiliar with the domain? * If your primary goal was to update one package but you found you had to update another one along the way, why did you do so? * If you had to upgrade a dependency, why did you do so? --> Added ESM exports for multichain package ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/package-a` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ### `@metamask/package-b` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ## 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 highlighted breaking changes using the "BREAKING" category above as appropriate - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes
@SocketSecurity ignore npm/[email protected] new author seems to be bot that is on numerous other popular npm packages |
@SocketSecurity ignore npm/@npmcli/[email protected] new author seems to be bot that is on numerous other popular npm packages |
@SocketSecurity ignore npm/[email protected] new author seems to be bot that is on numerous other popular npm packages |
@SocketSecurity ignore npm/[email protected] author contributes to other repos with several thousand stars |
@SocketSecurity ignore npm/[email protected] new author seems to be involved in node and typescript development. His two changes to this package are a removal of a file and bumping the node engine version |
@SocketSecurity ignore npm/[email protected] New authors changes seem just to be fixes. Author is also part of the Netflix open source org |
@SocketSecurity ignore npm/[email protected] makes sense for this package to have network access |
packages/multichain/src/middlewares/MultichainMiddlewareManager.test.ts
Outdated
Show resolved
Hide resolved
packages/multichain/src/middlewares/MultichainMiddlewareManager.test.ts
Outdated
Show resolved
Hide resolved
packages/multichain/src/middlewares/MultichainMiddlewareManager.test.ts
Outdated
Show resolved
Hide resolved
expect(endSpy).not.toHaveBeenCalled(); | ||
}); | ||
|
||
it('should remove middleware by scope and origin', () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do these tests verify that the middleware has been deleted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
they can't directly verify that the middleware is gone from state because those are stored in a private property on the class, so instead it tests the side effect, that being that next is called. I'll change these to call eth_subscribe though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…r.test.ts Co-authored-by: Frederik Bolding <[email protected]>
…r.test.ts Co-authored-by: Frederik Bolding <[email protected]>
…r.test.ts Co-authored-by: Frederik Bolding <[email protected]>
); | ||
expect(middlewareSpy).not.toHaveBeenCalled(); | ||
expect(nextSpy).not.toHaveBeenCalled(); | ||
expect(endSpy).toHaveBeenCalled(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't follow the test change here, shouldn't next be called and not end?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's because eth_subscribe is the method being called in this example (which results in end() being called since this triggers the case where eth_subscribe is called but no middleware is registered to handle it since we remove it as part of this scenario). I can either overload this to test both eth_subscribe and other, or split it into two methods
EDIT: I realized that the "eth_subscribe" request scenario already exists but was named poorly. I've changed this scenario back to calling something other than "eth_subscribe" and this test now expects nextSpy
to be called again
Explanation
This PR updates
@metamask/multichain
to add method handlers and middleware specific to the new Multichain API and which can be shared across the extension & mobile clients. The package includes implementations for managing multichain sessions, handling multichain RPC methods, and integrating multichain functionalities into the MetaMask extension. Key features of this package include:wallet_createSession
,wallet_invokeMethod
,wallet_revokeSession
, andwallet_getSession
.NormalizedScopesObject
andInternalScopesObject
These tools and utilities will be used in both clients (mobile + extension)'s multichain API implementations.
File Overview
packages/multichain/src/adapters/caip-permission-adapter-middleware.ts
: Middleware for the EIP-1193 API that enforces a CAIP-25 permission for each request if that CAIP-25 permission was granted viawallet_createSession
packages/multichain/src/handlers/wallet-getSession.ts
: Handlers for CAIP Multichain lifecycle methods except forwallet_createSession
which seemed a little too platform specific to belong in a shared package currentlypackages/multichain/src/middlewares/
: Middleware for the Multichain API that helps facilitate concurrent eth subscriptions and for using@metamask/api-specs
for method param validation for new CAIP Multichain methodspackages/multichain/src/scope/authorization.ts
: Adds helpers that sort scopes based on if they are currently supported by the wallet (i.e. a network already exists the eip155 scope), if they could be supported by the wallet (i.e. the network does not already exist for the eip155 scope, but the dapp has provided EIP-3085 details for adding the network in thescopedProperties
property of thewallet_createSession
request), or if they cannot be served.packages/multichain/src/scope/filter.ts
: provides helpers used for the bucketing above inauthorization.ts
types/@metamask/eth-json-rpc-filters.d.ts
: Typedef for missing types in@metamask/eth-json-rpc-filters/subscriptionManager
References
Upstream: #4784
Downstream: None. This is the end.
Key Multichain API Standards implemented here:
wallet_creatSession
wallet_invokeMethod
wallet_revokeSession
wallet_sessionChanged
wallet_getSession
Open PR that uses this new package for exposing the multichain API in the extension: MetaMask/metamask-extension#27782
Changelog
@metamask/multichain
getInternalScopesObject
andgetSessionScopes
helpers for transforming betweenNormalizedScopesObject
andInternalScopesObject
.caipPermissionAdapterMiddleware
for enforcing CAIP-25 permission on the EIP-1193 API.walletGetSession
,walletInvokeMethod
, andwalletRevokeSession
handlers.multichainMethodCallValidatorMiddleware
for validating Multichain API method params as defined in@metamask/api-specs
.MultichainMiddlewareManager
to multiplex a request to other middleware based on requested scope.MultichainSubscriptionManager
to handle concurrent subscriptions across multiple scopes.bucketScopes
which groups the scopes in aNormalizedScopesObject
based on if the scopes are already supported, could be supported, or are not supportable.getSupportedScopeObjects
helper for getting only the supported methods and notifications from eachNormalizedScopeObject
in aNormalizedScopesObject
.Checklist