Mark Stacey 55bff07bbf Use chainId for incoming transactions controller (#9583) ... The incoming transactions controller now uses the `chainId` for the current network instead of the `networkId`. This ensures that custom RPC endpoints for the built-in supported networks do correctly receive incoming transactions. As part of this change, the incoming transactions controller will also cease keeping track of the "last block fetched" for networks that are not supported. This piece of state never really represented the last block fetched, as _no_ blocks were fetched for any such networks. It been removed.		2020-10-30 22:28:12 -02:30
..
controllers	Use chainId for incoming transactions controller (#9583)	2020-10-30 22:28:12 -02:30
account-import-strategies.spec.js	Update ESLint shared config to v3 (#9274)	2020-08-19 13:57:05 -02:30
buy-eth-url.spec.js	Update Wyre purchase URL (#9414)	2020-09-15 17:56:51 -02:30
cleanErrorStack.spec.js
ComposableObservableStore.js	Fix import/order issues (#9239)	2020-08-18 16:48:25 -02:30
fetch-with-timeout.test.js
message-manager-test.js	Fix no-empty-function issues (#9216)	2020-08-14 09:17:02 -02:30
nodeify-test.js	Update ESLint shared config to v3 (#9274)	2020-08-19 13:57:05 -02:30
personal-message-manager-test.js	Fix no-empty-function issues (#9216)	2020-08-14 09:17:02 -02:30
seed-phrase-verifier-test.js
typed-message-manager.spec.js	Fix signTypedData_v4 chainId param validation (#9552)	2020-10-12 12:10:19 -07:00
util-test.js	Merge pull request from GHSA-c2xw-px2x-pr65	2020-10-06 15:27:02 -02:30