feat: align with updated 7715 standard - #39176
Merged
Merged
Conversation
Contributor
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
4 tasks done
Contributor
✨ Files requiring CODEOWNER review ✨✅ @MetaMask/confirmations (1 files, +4 -16)
👨🔧 @MetaMask/core-extension-ux (8 files, +220 -296)
📜 @MetaMask/policy-reviewers (12 files, +36 -228)
Tip Follow the policy review process outlined in the LavaMoat Policy Review Process doc before expecting an approval from Policy Reviewers. 👨🔧 @MetaMask/wallet-integrations (1 files, +4 -0)
|
Contributor
Builds ready [e24c689]
UI Startup Metrics (1272 ± 107 ms)
📊 Page Load Benchmark ResultsCurrent Commit: 📄 Localhost MetaMask Test DappSamples: 100 Summary
📈 Detailed Results
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
9 of 11 tasks
github-merge-queue Bot
pushed a commit
to MetaMask/core
that referenced
this pull request
Jan 14, 2026
## Explanation
### What is the current state of things and why does it need to change?
The `@metamask/eth-json-rpc-middleware` package currently supports two
EIP-7715 methods:
- `wallet_requestExecutionPermissions` — for requesting new execution
permissions
- `wallet_revokeExecutionPermission` — for revoking existing execution
permissions
However, the EIP-7715 specification also defines two additional
"discoverability" methods that allow dApps to query the wallet about its
execution permission capabilities. Without these methods, dApps have no
way to:
1. Discover which permission types the wallet supports and on which
chains
2. Retrieve the list of currently granted (non-revoked) permissions for
the user
### What is the solution your changes offer and how does it work?
This PR adds support for the two missing EIP-7715 discoverability
methods:
- **`wallet_getSupportedExecutionPermissions`** — Returns an object
keyed by permission type (e.g., `native-token-allowance`,
`erc20-token-allowance`) with their supported chain IDs and rule types.
This allows dApps to understand what the wallet can handle before making
permission requests.
- **`wallet_getGrantedExecutionPermissions`** — Returns an array of all
currently active (non-revoked) execution permissions. Each permission
includes chain ID, addresses, permission details, context, dependencies,
and delegation manager information.
The implementation follows the established patterns in this package:
- Each method has a dedicated handler file with a factory function
(`createWallet*Handler`)
- Hook-based architecture allows consumers to provide their own
processing logic
- Superstruct schemas are defined for result types, enabling runtime
validation
- Types and structs are exported from the package index for consumer use
#### EIP-7715 spec alignment for `wallet_requestExecutionPermissions`
The request/response schema has been updated to align with the latest
EIP-7715 specification:
- **Simplified address fields**: Replaced the nested `address` +
`signer: { type, data: { address } }` structure with flat `from`
(optional) and `to` (required) fields
- **Removed `isAdjustmentAllowed` from rules**: This property is only
relevant at the permission level, not individual rules
- **Extended result type**: Added `dependencies` (array of `{ factory,
factoryData }`) and `delegationManager` to the response
- **New export**: Added `PermissionDependency` type export for consumers
- **Consistent address validation**: Updated
`GrantedExecutionPermissionStruct` to use `HexChecksumAddressStruct` for
address fields
### Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
The handlers don't perform parameter validation since these methods
don't accept parameters (they're pure query methods). This is
intentional and differs from `wallet_requestExecutionPermissions` and
`wallet_revokeExecutionPermission` which validate their params using
Superstruct schemas.
## 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
-->
- Needed for: MetaMask/metamask-extension#39176
- Related to: MetaMask/snap-7715-permissions#249
## Checklist
- [x] I've updated the test suite for new or updated code as appropriate
- [x] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [x] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs)
- [x] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> Implements EIP-7715 discoverability methods and integrates them into
the wallet middleware.
>
> - New handlers: `createWalletGetSupportedExecutionPermissionsHandler`
and `createWalletGetGrantedExecutionPermissionsHandler` using hook-based
processing and `NoParamsStruct` validation
> - Exports new types and structs from `index.ts`
(`SupportedExecutionPermissionConfig*`, `GrantedExecutionPermission*`,
results)
> - Adds `EmptyArrayStruct`/`NoParamsStruct` in `utils/structs` for "no
params" validation
> - Wires methods into `createWalletMiddleware` via optional
`processGet*` hooks
> - Unit tests for both methods: hook invocation, result passthrough,
missing-hook error, and params validation
> - Changelog updated to note new RPC support
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
8e94f86. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
…into feat--support-7715-discoverability-methods
MoMannn
changed the title
Contributor
Builds ready [164f5be]
UI Startup Metrics (1286 ± 110 ms)
📊 Page Load Benchmark ResultsCurrent Commit: 📄 Localhost MetaMask Test DappSamples: 100 Summary
📈 Detailed Results
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
github-merge-queue Bot
pushed a commit
to MetaMask/core
that referenced
this pull request
Jan 15, 2026
## Explanation Releases: - `@metamask/gator-permissions-controller@1.0.0` - `@metamask/eth-json-rpc-middleware@23.0.0` - `@metamask/signature-controller@38.1.0` Both `gator-permissions-controller` and `eth-json-rpc-middleware` produce breaking changes to align with latest eip 7715 specs. ## 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 --> Required by: MetaMask/metamask-extension#39176 ## 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](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Releases coordinated majors with EIP‑7715 updates and dependency alignments. > > - **BREAKING:** `@metamask/eth-json-rpc-middleware@23.0.0` updates `wallet_requestExecutionPermissions` to 7715 spec; adds `wallet_getSupportedExecutionPermissions` and `wallet_getGrantedExecutionPermissions` > - **BREAKING:** `@metamask/gator-permissions-controller@1.0.0` updates core types to 7715 revisions > - **BREAKING:** `@metamask/shield-controller@5.0.0` now depends on `@metamask/signature-controller@39.0.0`; `decodedPermission` shape in signature requests changes > - `@metamask/signature-controller@39.0.0` bumps to use `gator-permissions-controller@1.0.0` > - `@metamask/network-controller` bumps dependency to `eth-json-rpc-middleware@^23.0.0` and updates changelog (notes new `ConnectivityController:getState` requirement) > - Bumps monorepo `version` to `751.0.0` and updates lockfile > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit e0a1409. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: Idris Bowman <34751375+V00D00-child@users.noreply.github.com>
…into feat--support-7715-discoverability-methods
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
Contributor
Builds ready [509370a]
UI Startup Metrics (1332 ± 107 ms)
📊 Page Load Benchmark ResultsCurrent Commit: 📄 Localhost MetaMask Test DappSamples: 100 Summary
📈 Detailed Results
Bundle size diffs [🚀 Bundle size reduced!]
|
Collaborator
|
Policies updated. 🧠 Learn how: https://lavamoat.github.io/guides/policy-diff/#what-to-look-for-when-reviewing-a-policy-diff |
metamaskbot
temporarily deployed
to
pr-comment
January 21, 2026 14:48 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
MoMannn
enabled auto-merge
January 21, 2026 14:59
MajorLift
previously approved these changes
Jan 21, 2026
ameliejyc
previously approved these changes
Jan 21, 2026
metamaskbot
temporarily deployed
to
pr-comment
January 21, 2026 15:17 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
Contributor
Builds ready [fb72537]
UI Startup Metrics (1343 ± 114 ms)
📊 Page Load Benchmark ResultsCurrent Commit: 📄 Localhost MetaMask Test DappSamples: 100 Summary
📈 Detailed Results
Bundle size diffs [🚀 Bundle size reduced!]
|
…into feat--support-7715-discoverability-methods
…github.com/MetaMask/metamask-extension into feat--support-7715-discoverability-methods
Member
Author
|
@metamaskbot update-policies |
jeffsmale90
approved these changes
Jan 21, 2026
Collaborator
|
No policy changes |
MajorLift
approved these changes
Jan 21, 2026
Contributor
Builds ready [a522169]
UI Startup Metrics (1318 ± 94 ms)
📊 Page Load Benchmark ResultsCurrent Commit: 📄 Localhost MetaMask Test DappSamples: 100 Summary
📈 Detailed Results
Bundle size diffs [🚀 Bundle size reduced!]
|
ameliejyc
approved these changes
Jan 21, 2026
dan437
approved these changes
Jan 21, 2026
jiexi
approved these changes
Jan 21, 2026
github-project-automation
Bot
moved this from Has approvals, needs CODEOWNER
to Review finalised - Ready to be merged
in PR review queue
This branch was previously deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
7 participants
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.
Description
This PR updates the codebase to align with API changes in the
@metamask/gator-permissions-controllerpackage.Reason for the change:
The upstream
@metamask/gator-permissions-controllerpackage has updated its type definitions and data structures. This PR ensures compatibility with those changes.Changes included:
Type simplification: Removed the
Signergeneric parameter fromStoredGatorPermissionSanitized<Signer, PermissionTypesWithCustom>→StoredGatorPermissionSanitized<PermissionTypesWithCustom>across all files (selectors, hooks, components, and tests).Data structure updates:
permissionResponse.address→permissionResponse.from(delegator address)decodedPermission.signer.data.address→decodedPermission.to(delegate/recipient address)permissionResponse.signerMeta.delegationManager→permissionResponse.delegationManager(flattened structure)permission.rules→permissionResponse.rules(rules array location change)New RPC methods: Added support for two new unrestricted methods:
wallet_getSupportedExecutionPermissions- Returns supported permission types (filtered by enabled advanced permissions)wallet_getGrantedExecutionPermissions- Returns granted execution permissionsChangelog
CHANGELOG entry: Added support for
wallet_getSupportedExecutionPermissionsandwallet_getGrantedExecutionPermissionsRPC methods.CHANGELOG entry: Updated to latest 7715 standart.
Related issues
Depends on: MetaMask/core#7603
Relates to: MetaMask/snap-7715-permissions#249
Requires: MetaMask/core#7634
Requires: MetaMask/snap-7715-permissions#254
Manual testing steps
For manual testing check: MetaMask/snap-7715-permissions#249
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Updates codebase to the 7715/gator-permissions v1 API and introduces execution-permissions query RPCs.
@metamask/gator-permissions-controller@^1.0.0: removeSignergeneric, movepermission.rulestopermissionResponse.rules, renamepermissionResponse.address→from,signerMeta.delegationManager→delegationManager, and decoded permissionsigner...address→to; applies across hooks, selectors, components, and testswallet_getSupportedExecutionPermissions(filters by enabled advanced types) andwallet_getGrantedExecutionPermissions; wires throughcreateMetamaskMiddlewareand forwards to the permissions kernel snapeth-json-rpc-middleware@^23,permissions-kernel-snap@^1.0.0,signature-controller@^39,shield-controller@^5, etc.) and adjusts LavaMoat policies to use the updated middleware pathingWritten by Cursor Bugbot for commit a522169. This will update automatically on new commits. Configure here.