Skip to content

refactor(network-controller)!: remove legacy per-endpoint failoverUrls - #11266

Merged
cryptodev-2s merged 5 commits into
mainfrom
worktree-zazzy-hatching-clover
Nov 5, 2026
Merged

cryptodev-2s merged 5 commits into
mainfrom
worktree-zazzy-hatching-clover

Conversation

@cryptodev-2s

@cryptodev-2s cryptodev-2s commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Explanation

NetworkController has two places to define RPC failover URLs: the failoverUrls constructor option (keyed by chain ID) and a legacy failoverUrls property on each RPC endpoint in state. The state property was only a fallback for chains missing from the constructor option, and both clients now pass that option.

This PR removes the legacy property:

  • failoverUrls is gone from InfuraRpcEndpoint and CustomRpcEndpoint, so addNetwork and updateNetwork no longer accept it.
  • Network clients use failoverUrls?.[chainId] ?? [], so configuration.failoverRpcUrls keeps its shape.

References

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
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

High Risk
Breaking API and behavior change to RPC failover sourcing in core network infrastructure; clients relying on per-endpoint persisted failover URLs will lose failover unless they migrate to the constructor option.

Overview
Breaking change: failoverUrls is removed from InfuraRpcEndpoint and CustomRpcEndpoint, so persisted RPC endpoints and addNetwork / updateNetwork payloads must no longer include it. Default and custom network templates in NetworkController stop emitting empty failoverUrls arrays on each endpoint.

RPC failover is now only supplied via the NetworkController constructor option failoverUrls (keyed by chain ID). When building network clients, failoverRpcUrls is set to failoverUrls?.[chainId] ?? [] with no fallback to values that used to live on individual endpoints—chains without a constructor entry get no failover URLs.

Tests and fixtures across network-controller, assets-controller, assets-controllers, multichain-network-controller, and selected-network-controller are updated accordingly (provider failover tests now pass chain-level failoverUrls). The changelog documents client migration (stop writing endpoint failoverUrls, optionally strip them from persisted state).

Reviewed by Cursor Bugbot for commit 76a9a4b. Bugbot is set up for automated code reviews on this repo. Configure here.

@cryptodev-2s
cryptodev-2s requested review from a team as code owners November 3, 2026 13:55
@cryptodev-2s
cryptodev-2s marked this pull request as draft November 3, 2026 14:01
…s from RPC endpoints

Failover URLs are now sourced only from the failoverUrls constructor option, keyed by chain ID. The failoverUrls property on RpcEndpoint (and on endpoints accepted by addNetwork/updateNetwork) is removed.
@cryptodev-2s
cryptodev-2s force-pushed the worktree-zazzy-hatching-clover branch from 1c0fd72 to 3a0f39d Compare November 3, 2026 14:08
@cryptodev-2s

Copy link
Copy Markdown
Contributor Author

@metamaskbot publish-preview

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Preview builds have been published. Learn how to use preview builds in other projects.

Expand for full list of packages and versions.
@metamask-previews/account-tree-controller@11.2.0-preview-3a0f39d23
@metamask-previews/accounts-controller@40.1.0-preview-3a0f39d23
@metamask-previews/address-book-controller@8.0.0-preview-3a0f39d23
@metamask-previews/advanced-chart-core@1.0.0-preview-3a0f39d23
@metamask-previews/ai-controllers@2.0.0-preview-3a0f39d23
@metamask-previews/analytics-controller@4.1.0-preview-3a0f39d23
@metamask-previews/analytics-data-regulation-controller@0.0.0-preview-3a0f39d23
@metamask-previews/announcement-controller@9.0.0-preview-3a0f39d23
@metamask-previews/app-metadata-controller@3.0.0-preview-3a0f39d23
@metamask-previews/approval-controller@10.0.0-preview-3a0f39d23
@metamask-previews/assets-controller@20.2.0-preview-3a0f39d23
@metamask-previews/assets-controllers@113.1.0-preview-3a0f39d23
@metamask-previews/authenticated-user-storage@4.1.0-preview-3a0f39d23
@metamask-previews/base-controller@10.1.0-preview-3a0f39d23
@metamask-previews/base-data-service@2.1.0-preview-3a0f39d23
@metamask-previews/bitcoin-regtest-up@2.0.0-preview-3a0f39d23
@metamask-previews/bridge-controller@83.1.3-preview-3a0f39d23
@metamask-previews/bridge-status-controller@78.0.1-preview-3a0f39d23
@metamask-previews/build-utils@4.0.0-preview-3a0f39d23
@metamask-previews/byte-utils@0.1.0-preview-3a0f39d23
@metamask-previews/chain-agnostic-permission@2.1.0-preview-3a0f39d23
@metamask-previews/chomp-api-service@7.0.0-preview-3a0f39d23
@metamask-previews/claims-controller@1.1.0-preview-3a0f39d23
@metamask-previews/client-controller@2.0.0-preview-3a0f39d23
@metamask-previews/client-utils@3.1.0-preview-3a0f39d23
@metamask-previews/compliance-controller@3.0.0-preview-3a0f39d23
@metamask-previews/composable-controller@13.0.0-preview-3a0f39d23
@metamask-previews/config-registry-controller@5.0.0-preview-3a0f39d23
@metamask-previews/connectivity-controller@1.0.0-preview-3a0f39d23
@metamask-previews/controller-utils@13.0.0-preview-3a0f39d23
@metamask-previews/core-backend@13.0.0-preview-3a0f39d23
@metamask-previews/cryptography@1.1.2-preview-3a0f39d23
@metamask-previews/delegation-controller@4.0.0-preview-3a0f39d23
@metamask-previews/earn-controller@13.0.2-preview-3a0f39d23
@metamask-previews/eip-5792-middleware@4.1.0-preview-3a0f39d23
@metamask-previews/eip-7702-internal-rpc-middleware@1.0.0-preview-3a0f39d23
@metamask-previews/eip1193-permission-middleware@3.0.0-preview-3a0f39d23
@metamask-previews/error-utils@0.1.0-preview-3a0f39d23
@metamask-previews/eth-block-tracker@16.0.0-preview-3a0f39d23
@metamask-previews/eth-json-rpc-middleware@26.0.0-preview-3a0f39d23
@metamask-previews/eth-json-rpc-provider@7.0.0-preview-3a0f39d23
@metamask-previews/foundryup@2.0.0-preview-3a0f39d23
@metamask-previews/gas-fee-controller@27.0.0-preview-3a0f39d23
@metamask-previews/gator-permissions-controller@6.1.0-preview-3a0f39d23
@metamask-previews/geolocation-controller@2.0.0-preview-3a0f39d23
@metamask-previews/java-tron-up@2.0.0-preview-3a0f39d23
@metamask-previews/json-rpc-engine@11.0.0-preview-3a0f39d23
@metamask-previews/json-rpc-middleware-stream@9.0.0-preview-3a0f39d23
@metamask-previews/keyring-controller@28.2.0-preview-3a0f39d23
@metamask-previews/kyc-controller@0.14.0-preview-3a0f39d23
@metamask-previews/local-node-utils@2.0.0-preview-3a0f39d23
@metamask-previews/logging-controller@10.0.0-preview-3a0f39d23
@metamask-previews/marketing-consent-controller@1.1.0-preview-3a0f39d23
@metamask-previews/message-manager@15.0.0-preview-3a0f39d23
@metamask-previews/messenger@3.0.0-preview-3a0f39d23
@metamask-previews/messenger-cli@1.0.0-preview-3a0f39d23
@metamask-previews/mfa-recovery-controller@0.0.0-preview-3a0f39d23
@metamask-previews/money-account-api-data-service@2.3.1-preview-3a0f39d23
@metamask-previews/money-account-balance-service@3.1.2-preview-3a0f39d23
@metamask-previews/money-account-controller@3.0.0-preview-3a0f39d23
@metamask-previews/money-account-lifecycle-controller@0.0.0-preview-3a0f39d23
@metamask-previews/money-account-mfa-whitelist@0.1.0-preview-3a0f39d23
@metamask-previews/money-account-upgrade-controller@6.0.0-preview-3a0f39d23
@metamask-previews/money-account-utils@2.2.0-preview-3a0f39d23
@metamask-previews/multichain-account-service@14.1.0-preview-3a0f39d23
@metamask-previews/multichain-api-middleware@5.0.0-preview-3a0f39d23
@metamask-previews/multichain-network-controller@4.0.0-preview-3a0f39d23
@metamask-previews/multichain-transactions-controller@8.0.0-preview-3a0f39d23
@metamask-previews/name-controller@10.0.0-preview-3a0f39d23
@metamask-previews/network-connection-banner-controller@1.0.0-preview-3a0f39d23
@metamask-previews/network-controller@37.1.1-preview-3a0f39d23
@metamask-previews/network-enablement-controller@7.1.0-preview-3a0f39d23
@metamask-previews/node-utils@0.1.0-preview-3a0f39d23
@metamask-previews/notification-services-controller@30.1.0-preview-3a0f39d23
@metamask-previews/passkey-controller@4.1.0-preview-3a0f39d23
@metamask-previews/permission-controller@14.1.0-preview-3a0f39d23
@metamask-previews/permission-log-controller@6.0.0-preview-3a0f39d23
@metamask-previews/perps-controller@22.1.0-preview-3a0f39d23
@metamask-previews/phishing-controller@18.3.0-preview-3a0f39d23
@metamask-previews/platform-api-docs@0.2.1-preview-3a0f39d23
@metamask-previews/polling-controller@17.0.0-preview-3a0f39d23
@metamask-previews/preferences-controller@24.0.0-preview-3a0f39d23
@metamask-previews/profile-controller@1.2.1-preview-3a0f39d23
@metamask-previews/profile-metrics-controller@5.2.1-preview-3a0f39d23
@metamask-previews/profile-sync-controller@36.0.0-preview-3a0f39d23
@metamask-previews/ramps-controller@29.0.0-preview-3a0f39d23
@metamask-previews/rate-limit-controller@8.0.0-preview-3a0f39d23
@metamask-previews/react-data-query@2.0.0-preview-3a0f39d23
@metamask-previews/remote-feature-flag-controller@7.0.0-preview-3a0f39d23
@metamask-previews/sample-controllers@6.0.0-preview-3a0f39d23
@metamask-previews/seedless-onboarding-controller@12.0.0-preview-3a0f39d23
@metamask-previews/selected-network-controller@27.0.0-preview-3a0f39d23
@metamask-previews/sentinel-api-service@2.1.0-preview-3a0f39d23
@metamask-previews/shield-controller@7.1.1-preview-3a0f39d23
@metamask-previews/signature-controller@40.0.0-preview-3a0f39d23
@metamask-previews/smart-transactions-controller@27.2.1-preview-3a0f39d23
@metamask-previews/snap-account-service@4.0.0-preview-3a0f39d23
@metamask-previews/social-controllers@3.15.0-preview-3a0f39d23
@metamask-previews/solana-test-validator-up@2.0.0-preview-3a0f39d23
@metamask-previews/stellar-quickstart-up@0.0.0-preview-3a0f39d23
@metamask-previews/storage-service@2.0.0-preview-3a0f39d23
@metamask-previews/subscription-controller@15.1.2-preview-3a0f39d23
@metamask-previews/transaction-controller@73.0.0-preview-3a0f39d23
@metamask-previews/transaction-pay-controller@30.3.3-preview-3a0f39d23
@metamask-previews/transaction-pay-middleware@2.0.1-preview-3a0f39d23
@metamask-previews/type-utils@0.1.0-preview-3a0f39d23
@metamask-previews/user-operation-controller@42.1.0-preview-3a0f39d23
@metamask-previews/utils@12.0.1-preview-3a0f39d23
@metamask-previews/wallet@21.0.0-preview-3a0f39d23
@metamask-previews/watch-only-account-service@0.1.0-preview-3a0f39d23

@cryptodev-2s
cryptodev-2s added this pull request to the merge queue Nov 5, 2026
Merged via the queue into main with commit 82c01b9 Nov 5, 2026
84 checks passed
@cryptodev-2s
cryptodev-2s deleted the worktree-zazzy-hatching-clover branch November 5, 2026 09:52
Naz-Ovh pushed a commit to 0x-fork/metamask-core that referenced this pull request Nov 7, 2026
## Explanation

Release 1397.0.0. It bumps two packages:

| Package | From | To | Why |
| --- | --- | --- | --- |
| `@metamask/assets-controller` | 20.2.2 | **20.2.3** (patch) |
Unreleased only has a `Changed` entry: asset state now included in state
logs ([MetaMask#11319](MetaMask#11319)) |
| `@metamask/assets-controllers` | 113.1.1 | **113.2.0** (minor) |
`Added`: `serviceProfile` option on `searchTokens`
([MetaMask#11274](MetaMask#11274)), plus a `uuid`
bump |

Nothing breaking has landed in either package since its last release.
The `refactor(network-controller)!` commit (MetaMask#11266) only touched test
fixtures in these packages.

Generated with `yarn create-release-branch`. I didn't edit any changelog
by hand. Uncategorized entries are left for the changelog bot.

### Other changes the tool made
- Bumped dependents' ranges: `bridge-controller` (`assets-controller`
^20.2.3, `assets-controllers` ^113.2.0), `transaction-pay-controller`
(`assets-controller` ^20.2.3), `assets-controller` (`assets-controllers`
^113.2.0), and `yarn.lock`.
- Root version 1396.0.0 → 1397.0.0.

### Packages marked `intentionally-skip`
The tool requires these because they are dependencies of the released
packages. Neither release relies on any unreleased change in them:
account-tree-controller, accounts-controller, approval-controller,
base-controller, client-controller, config-registry-controller,
controller-utils, core-backend, keyring-controller, messenger,
multichain-account-service, multichain-transactions-controller,
network-controller, network-enablement-controller,
permission-controller, phishing-controller, polling-controller,
preferences-controller, profile-sync-controller,
remote-feature-flag-controller, storage-service, transaction-controller,
utils.

## Checks run locally
- `yarn constraints`: passes
- Tests for `@metamask/assets-controller` (1384 passed) and
`@metamask/assets-controllers` (1863 passed): pass
- `yarn changelog:validate`: passes (after the internal-only
`Uncategorized` entries were removed)

## Adversarial review (adverse)
Round 1 verdict: **SHIP-WITH-CAVEATS (3/3 ship, 0/3 block)**. Findings:
0 critical, 2 warnings, 2 info.
- Warning: the `Uncategorized` block is left in both changelogs.
**Fixed.** I removed both blocks. They held only MetaMask#11324 (dev tooling)
and MetaMask#11266 (test fixtures only in these packages), so nothing changes
for consumers.
- Warning: patch bump despite a `Changed` entry. **Declined.** The
change only adds state-log metadata, with no API change and no new
behavior for consumers, so patch is right.
- Info: the `refactor(network-controller)!` entry appears in packages
that weren't really affected. **Fixed** by the same removal.

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
dmytrozahumennov-wb pushed a commit to dmytrozahumennov-wb/metamask-extension that referenced this pull request Nov 10, 2026
)

## **Description**

MetaMask/core#11266 removes the per-endpoint `failoverUrls` property
from `NetworkController`. Failover URLs now come only from the
`failoverUrls` constructor option (chain ID to URLs), and only apply to
`*.infura.io` endpoints.

This PR adopts that change:

- Drops `failoverUrls` from the built-in and featured RPC endpoints, the
network form state, and the `wallet_addEthereumChain` confirmation.
- Adds `getFailoverUrlsForEndpoint` so the "Failover" tag in the network
form and RPC list reads from the constructor map for Infura endpoints.
- Adds migration 235 to strip `failoverUrls` from persisted
`rpcEndpoints`. Migrations 182 and 184 no longer write the field (needed
to type-check).

The v38 bump also changes failover behavior beyond the `failoverUrls`
removal:

- RPC failover mode now defaults to `enabled`. Before, a missing or
malformed `corePlatformRpcFailoverMode` flag was read as `disabled`. Now
it is skipped, so the default applies. A valid flag value (`disabled`,
`enabled`, `forced`) is still honored, so the e2e specs that set
`disabled` keep working.
- The Failover tag in the network form and RPC list now follows
`corePlatformRpcFailoverMode` (on unless `disabled`), matching the
controller. The retired `walletFrameworkRpcFailoverEnabled` flag is no
longer referenced, including in the feature flag registry.
- Anyone with a custom `failoverUrls` value on an endpoint outside the
chain ID map loses it. This is expected.

## **Changelog**

CHANGELOG entry: null

## **Related issues**

Related: MetaMask/core#11266

## **Manual testing steps**

1. In `.metamaskrc`, set `QUICKNODE_MAINNET_URL` to any URL, then run
`yarn start` and load the extension. RPC failover mode defaults to
`enabled`, so no flag override is needed.
2. Open Settings > Networks and edit Ethereum Mainnet.
3. Verify the "Failover" tag shows on the Infura RPC endpoint and the
failover URL field shows the QuickNode URL.
4. Add a custom (non-Infura) RPC to the same network and verify it shows
no failover tag.
5. On a build from main, create a wallet, then switch to this branch's
build. Verify the wallet loads, networks still work, and a downloaded
state log has no `failoverUrls` on any RPC endpoint.

<!--
## **Screenshots/Recordings**

### **Before**

### **After**
-->

## **Pre-merge author checklist**

- [ ] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Touches persisted network configuration via a migration and changes
default RPC failover gating when remote flags are missing; custom
per-endpoint failover values in old state are dropped.
> 
> **Overview**
> Adopts `@metamask/network-controller` **v38** by removing the legacy
**`failoverUrls` field on individual RPC endpoints** from persisted
state, built-in/featured network definitions, network form state, and
`wallet_addEthereumChain` approvals. **Migration 235** strips any
leftover per-endpoint `failoverUrls` from `NetworkController` state;
migrations **182** and **184** no longer write that field.
> 
> Failover display and behavior now follow the controller model:
**`getFailoverUrlsForEndpoint`** looks up chain-keyed QuickNode URLs
only for `*.infura.io` endpoints, and the network form / RPC list use
that instead of persisted endpoint data. RPC failover UI gating switches
from **`walletFrameworkRpcFailoverEnabled`** to
**`corePlatformRpcFailoverMode`** (on unless explicitly `disabled`,
matching the controller default). E2E fixtures and validation are
updated to state version **235** without endpoint `failoverUrls`.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
781592d. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
darkwing pushed a commit to darkwing/metamask-mobile that referenced this pull request Nov 12, 2026
## **Description**

MetaMask/core#11266 removes the per endpoint `failoverUrls` property
from `@metamask/network-controller` (v38). Failover URLs now come only
from the controller's `failoverUrls` constructor option (chain ID to
URLs), and core applies them only to `*.infura.io` endpoints.

This PR adapts mobile to that:

* Builds the constructor option from one chain keyed map in
`customNetworks.tsx`, and stops writing `failoverUrls` on endpoints
(popular networks, config registry, swap deeplink, card and bridge
hooks).
* Adds migration 162 to strip `failoverUrls` from persisted
`NetworkController` state. Migrations 72 and 83 no longer write the
field (needed to type check).
* Network details UI reads failover from the chain map and shows the
Failover tag only for Infura hosted endpoints, matching what core does.
* Adds Robinhood (`0x1237`) to the map. Its only failover source used to
be the endpoint state value.

The v38 bump also changes failover behavior beyond the `failoverUrls`
removal:

* RPC failover mode now defaults to `enabled`. Before, a missing or
malformed `corePlatformRpcFailoverMode` flag was read as `disabled`. Now
it is skipped, so the default applies. A valid value (`disabled`,
`enabled`, `forced`) is still honored.
* The Failover tag follows `corePlatformRpcFailoverMode` (on unless
`disabled`), matching the controller. The retired
`walletFrameworkRpcFailoverEnabled` flag is no longer referenced, and
the feature flag registry is updated.

## **Changelog**

CHANGELOG entry: null

## **Related issues**

Refs: MetaMask/core#11266

## **Manual testing steps**

Before testing, set a failover URL for Ethereum Mainnet in `.js.env`.
Without it the chain has no failover configured and the tag never shows:

```
export QUICKNODE_MAINNET_URL="https://example.quiknode.pro/test"
```

Then restart Metro with `yarn watch:clean` (the value is baked into the
bundle, so a plain reload is not enough) and reload the app. Any URL
works for checking the display.

```gherkin
Feature: RPC failover display

  Scenario: Infura endpoint shows failover
    Given Ethereum Mainnet with its Infura RPC selected and QUICKNODE_MAINNET_URL set

    When user opens the network details
    Then the Failover tag and read only failover URL are shown

  Scenario: custom endpoint does not show failover
    Given the same chain with a custom RPC that is not Infura selected

    When user opens the network details
    Then no Failover tag or failover URL is shown

  Scenario: upgrading from a build of main
    Given a wallet created on a build of main

    When user installs this branch on top and opens the app
    Then the wallet loads, networks still work, and persisted NetworkController state has no `failoverUrls` on any RPC endpoint
```

## **Screenshots/Recordings**


https://github.com/user-attachments/assets/64f199c7-df4d-4179-839e-4b534d372966

## **Pre-merge author checklist**

- [ ] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [ ] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Touches core RPC configuration, a persistence migration, and a major
`network-controller` bump; failover gating and defaults change when
remote flags are missing, but scope is largely aligned with upstream
core behavior.
> 
> **Overview**
> Upgrades **`@metamask/network-controller` to v38** and removes the
legacy **`failoverUrls` field on RPC endpoints** everywhere the app adds
or edits networks (PopularList, bridge/card hooks, swap deeplinks,
config registry, network form state).
> 
> **Failover is now chain-level only:** `customNetworks.tsx` exposes
`getFailoverUrlsByChainId()` (including Robinhood chain `0x1237`),
passed into `NetworkController` via wallet init options. The network
details UI and RPC list use `getFailoverUrlsForEndpoint(chainId,
rpcUrl)` so the **Failover** tag and read-only URL appear only for
**`*.infura.io`** endpoints when failover is enabled—matching core
behavior.
> 
> **Migration 162** strips persisted per-endpoint `failoverUrls` from
`networkConfigurationsByChainId`. Older migrations and fixtures stop
writing the field.
> 
> **Feature flags:** `selectIsRpcFailoverEnabled` now keys off
`corePlatformRpcFailoverMode` (off only when `disabled`; absent flag
defaults to on), replacing `walletFrameworkRpcFailoverEnabled`.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
25c1ebe. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants