Multichain: Stop Using Partial State for getCurrentChainId Params in metamask-controller

What is this about?

As part of the work to get Default RPCs work out, we used some partial states in metamask-controller.js for usages of getCurrentChainId parameters for controllers, including:

• TokenListController
• AssetsContractController
• TokensController
• NftController
• NftDetectionController
• MetaMetricsController
• GasFeeController
• PPOMController
• TransactionController
• getAddTransactionRequest
• getProviderConfig

When the concept of the global chain ID goes away, we need these to be contextual. This pattern can be easily identified by:

fn({ metamask: this.networkController.state })

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

• Engineering (needed in most cases)
• Design
• Product
• QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• Security
• Legal
• Marketing
• Management (please specify)
• Other (please specify)

References

No response

Start in metamask-controller.js and search for the listed getCurrentChainId usages matching fn({ metamask: this.networkController.state }). Review how each named controller receives chain context. Done means those usages no longer rely on partial state and all listed integrations work with contextual chain IDs.