feat(account-tree-controller): use multichain-account-service to build multichain account wallet/group nodes
#6646
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
|
@metamaskbot publish-preview |
|
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions. |
…for bip-44 accounts
ccharly
force-pushed
the
feat/account-tree-controller-use-service
branch
from
4390b9d to
c5de1f5
Compare
|
@metamaskbot publish-preview |
|
@metamaskbot publish-preview |
|
@metamaskbot publish-preview |
|
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions. |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The
multichain-account-serviceis responsible of holding/grouping all BIP-44 accounts together (in wallets and groups).The
account-tree-controllerwas re-using a similar matching logic to build it's tree and match those wallets and groups. But... In reality, this is the responsibility of the service and thus, the controller should "consume" the wallets/groups from the service directly.Architecture wise, this is more correct, and other kind of wallets could follow the same pattern (having 1 wallet for each keyring types and 1 wallet for each other kind of account management Snaps).
This also fixes an issue with backup & sync which was listening to
:accountAddedeven for BIP-44 accounts. The problem was because theEvmAccountProvideris sometimes temporarily creating an account in order to get its associated address (during discovery) and then remove it afterward. Since backup & sync does not handle account deletion, this temporary account was triggering an account group creation on backup & sync, thus, "persisting" this account on the user remote profile.References
N/A
Checklist