Desi McAdam
Desi McAdam
Please don't spend more than 2 to 3 days on this spike. Outcome of the spike should be a POC that lets us define an actual issue to be worked...
Order of operation: - Complete Controller Message ADR work - Build minimal POC - Then write the tech proposal. Desi add blockers for the two dependencies to this issue.
Chunk files make creating patches difficult and for that reason we'd like to move to using `ts-bridge` where possible.
### What is this about? Update the `@metamask/base-controller` package and replace all `RestrictedMessenger` instances with a delegated messenger. This issue represents the work needed to resolve breaking changes made as...
When there is a new npm published for core it would be nice if that could trigger a slack notification to the metamask dev channel for all EM's to check...
## Problem To make the Wallet Framework a success, we want developers to use the messenger within the UI and other places. However, currently, it is very difficult for them...
Once all the Keyring updates have been completed and we are ready to release the controller, we should create a DRAFT PR to pull those changes into Mobile
Once all the Keyring updates have been completed and we are ready to release the controller, we should create a DRAFT PR to pull those changes into Extension
auto create issues: when a release in core trigger issues in the other controller repos - accounts - ppomvalidator - smart transactions - swaps - snaps
For the services piece of this we should do this after the RPC service work. The messenger system should come after the ADR for messenger delegation related - https://github.com/MetaMask/core/issues/4986 -...