feat: move Notifications networks config to backend [GE-23] #7840
Conversation
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
Contributor
There was a problem hiding this comment.
TYSM!!
Great that we can clean this up!
Contributor
There was a problem hiding this comment.
Note - this whole file can be thrown away once we start the push notification cleanup ticket
(push notifications are all derived from the server now, so we do not need any client side implementation to generate push messages).
Contributor
Author
There was a problem hiding this comment.
Done in 6e7ebdb. I thought it made sense to add it in this PR
Prithpal-Sooriya
previously approved these changes
Feb 4, 2026
...ation-services-controller/src/NotificationServicesController/mocks/mock-raw-notifications.ts
Show resolved
Hide resolved
7 tasks
baptiste-marchand
changed the title
packages/notification-services-controller/notification-services/ui/package.json
Outdated
Show resolved
Hide resolved
...tion-services-controller/src/NotificationServicesController/constants/notification-schema.ts
Show resolved
Hide resolved
| - Note, however, that the versions specified in the client's `package.json` always "win", and you are expected to keep them up to date so as not to break controller and service intercommunication. | ||
| - Modified background push utilities to handle more edgecases and not throw errors ([#7275](https://github.com/MetaMask/core/pull/7275)) | ||
| - Bump `@metamask/controller-utils` from `^11.16.0` to `^11.18.0` ([#7534](https://github.com/MetaMask/core/pull/7534), [#7583](https://github.com/MetaMask/core/pull/7583)) | ||
| - Move Notifications networks metadata to backend ([#7840](https://github.com/MetaMask/core/pull/7840)) |
Contributor
There was a problem hiding this comment.
Since we are removing some exports, lets add this in the ### Removed section, and mark as breaking (will require a major version bump)
Prithpal-Sooriya
approved these changes
Feb 10, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Explanation
This PR removes notification networks config to replace it by backend data.
Backend PR: https://github.com/consensys-vertical-apps/va-mmcx-notify-notification-services/pull/265
References
Fixes: GE-23
Checklist
Note
Medium Risk
Introduces a breaking export removal and changes how push notification text derives chain symbols, so clients must adapt and backend payloads must reliably include
payload.network.Overview
Moves notification network metadata from client-side constants to backend-provided payload fields. The
./notification-services/uisubpath export (and its bundled network constants/types likeNOTIFICATION_CHAINS_ID, currency symbols, and block explorer mappings) is removed, and the rootNotificationServicesControllerno longer re-exportsUI.Notification API types are updated so on-chain payloads include
networkmetadata (native_symbol,block_explorer, etc.), mocks are updated to include this newpayload.networkobject, and push-notification message generation now reads the symbol fromnotification.payload.network.native_symbolinstead of local chain-id mappings.Written by Cursor Bugbot for commit d01b2f9. This will update automatically on new commits. Configure here.